Sorry for the afterthought but even if the user clicks "Close
GNUmed", may there already have been a problem of their data not
having gotten, or getting, properly committed?
I am guessing that even GNUmed *could* (normally) detect and report a
problem with saving data, this could be impeded by an exception.
Do we therefore think it advisable that, after an exception, the user
verified whether their last entry had been properly saved? If not
with every exception, then with the unhandled ones?
If so, then maybe after "don't count on it." add one of
Either way, it is advisable to notice if your next (or last) entry
appears intact.
or
If you keep running, it is advisable to watch if your current entry
appears intact.
... provided the above does not overly lengthen (vertically) the window
On May 11, 2007, at 4:44 AM, Karsten Hilbert wrote:
On Fri, May 11, 2007 at 01:35:30PM +0200, Karsten Hilbert wrote:
Attached find a screenshot of the exception handler in
action with all suggestions included.
Well ...
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
<GNUmed-exception-handler.png>
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
