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.
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.
