seems, because you typically want to communicate with multiple peers at
the same time.
Minor updates, and moved files to more meaningful locations,
which required updating links.
Christian and moralistic.
Explanation of "Proof of share" added to crypto_currency.md
where no one is likely to find it. Need to create document
on consensus.
which is an irrelevant digression, since it already
reports errors on calls
Maybe I will get reports if I fail to finalize a compiled
sql statement before shutting down a database connection,
but the most likely circumstance for this to happen is
on program close, when I am unlikely to be able to see
the log.
Sqlite3 crash due to premature call to shutdown.
calls to layout very rarely have any obvious effect,
but sometimes under odd and idiosyncratic circumstances
they do.
Called shutdown after the destroy was executed, but destroy does
not immediately destroy the windows, thus does not immediately
finalize all compiled sql statements and close all database
connections. You have to wait for all the windows to be destroyed.
Again, a rare crash except under certain special circumstances.
add name so it does not flash so horribly
Massively violating dry - I need to extract the repeated
code into a struct that does the cleanup when it is
destroyed
from display_wallet.h and display_wallet.cpp
They are now all wrapped in the long promised
and long forgotten wrapper class.
Long, long ago, I intended to implement the Pimpl idiom,
but these days std::unique takes care of all that work for
you. You just wrap your low level pimple class in a high
level wrapper whose base class is an std_unique_ptr to
to an instance of your low level class.
but the overhead and screen flash
of destroying and recreating every
little window is annoying.
I should use something like:
SELECT COUNT(*) FROM UserZookoIDs
WHERE LOWER("name")<LOWER(?1) AND "name"<?1);
and insert a new item at that position
the sqlite view capability VIEW UserZookoIDs
Made add_name responsive, but add_name still
does not use the VIEW triggers.
Got distracted by sizing issues. There is some issues
with resizing architecture - I know they put an ad hoc
workaround in on dialogs, need to read up on what they
did and why.
start problem.
modified: docs/manifesto/social_networking.md
Discussion of gpg has been obsoleted by
by git adding its own trust mechanism
to deal with the trust problems of gpg.
modified: docs/rootDocs/README.md
modified: docs/setup/contributor_code_of_conduct.md
for the case where we have many windows and
you want to change the menu on change of focus
Which is a classic example of writing code before
it is needed.
to the new cool style imitating other successful open
software movements.
But all my navbars are the same navbar. The point of the new
style is to make information readily available.
We will want multiple button bars in the navbar, and possibly a
related materials sidebar. Or perhaps simply link pages.
We also need to change the introductory paragraph in every page
to the abstract style.
length bitfields to that they will sort correctly in a Merkle Patricia
tree.
Have written no end of rubbish on this with needs to be deleted or
modified
fixed it by looking for funny things that deviated from
the sameples, and doing various recommended safe things,
and found a few sql errors, and one by one the crashes
went away.
The new wxWidgets just seems less tolerant of little careless
stuff that is not right.
a distributed hash table byzantine fault tolerant
Slight clarification on scalability
Figured out how to make variable length integers that
will be represented in correct order in a patricia
merkle tree.
Halting work on main program to re-integrate libraries.
Crash on file dialog. Does not happen in
wxWidgets sample code
Failure to record last used. Does not happen in
wxWidgets sample code
Failure to throw hash re-use exception
(the library always returns zero on hashing data into an
unfinalized, or finalizing an already finalized hash)
Need to use std::variant, with the variants being
monotype for the default init of hash and blob of unsigned
char for the init with an hsh argument, with a member
function blob that does get_if<1> and casts it to byte,
(and throws if it returns null) and for hsh, the variants
being monotype, the libsodium data structure,
and another monotype after the hash is finalized.
For every cross type constructor, you need a corresponding
static cast in the source type, so that copy construction works.
I don't know why << fails with a left hand type.
looks like wxWidgets bugs
going back to sample code
either sample code breaks, and I make a bug report
to wxWidgets, or I converge the sample code to my
code, and see when it breaks
But did not apply the concept to the parameter pack,
event though I applied no end of cleverness to generate
a variant concept, because
visual studio gives meaningless error messages when applying
a variant concept to a parameter pack.
This will probably improve in later or different compilers,
but right now, this feature does not work
