that by default it searches for header files in the source
directory as well as on the include line - which is very
nice but non standard and breaks every other build system,
resulting in incomprehensible and misleading error messages
that send one down a hundred rabbit holes.
Windows and MacOS default fonts to metric compatibility with Times for serif and Helvetica for sans-serif.
while Linux defaults to metric compatibility with DejaVu
DejaVu also has better full unicode support than just about anyone.
DejaVu has more inversal compatibility, everything has DejaVu
So if you want your documents to lay out the same on every system
go with DejaVu.
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