Donald Allen <[email protected]> writes:
>> Agreed, it should be more vocal about failures! In particular it should
>> at LEAST output something to gnucash.trace!
>
> It already announces the assertion failure in gnucash.trace. That's
> great for debugging, pretty useless for an ordinary user. The user
> needs to be told about this via the UI.
Yeah, that's true too. Certain errors need to get propagated up to the
user.
>> Can you try to run a Check & Repair to see if it fixes the issue?
>
> I did and it did (with gnucash 2.2.9). It didn't take very long,
> either, and my xml file is over 20 Mb uncompressed. Perhaps you should
> consider automatically running Check & Repair after N restarts of
> gnucash, just as fsck is run after N clean reboots that mount an
> ext2/ext3 filesystem.
Not a bad idea. Or perhaps it should get run prior to a Save-As?
> /Don
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[email protected] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
