Does not fix the crash when closing a register window that was popped up from reconcile.
It's actually worse now, I now also get a crash when closing a register window that wasn't opened from reconcile. Doesn't fix the goofy tab/cant-add-a-split behavior either. Did anyone else have any luck with these latest commits? (0.1099s) [load] -*-helvetica-bold-r-*-*-12-*-*-*-*-*-ISO8859-1 --> 0x83f19f8 (0.1253s) [load] -*-helvetica-bold-r-*-*-15-*-*-*-*-*-ISO8859-1 --> 0x8398ff0 Debug: sxsincelast_populate: No scheduled transactions to populate. Debug: regWindowLedger: (regData)08503f90 (->window)08513d48 (->gsr)0850df68 (->ledger)08429138 Debug: regWindowLedger: (regData)0856a040 (->window)08429468 (->gsr)085791e8 (->ledger)08429138 Debug: gnc_split_reg_ld_destroy: destroying (gsr)085791e8 (->window)08429468 with ledger 08429138 Debug: gsr_foobar: Happiness is being destroyed (widget)08586cd0, (ud)085791e8 -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Josh Sled [mailto:jsled@;asynchronous.org] > Sent: Thursday, November 14, 2002 2:40 AM > To: Chris Lyttle; Gnucash > Subject: Re: Register really broken > > > On Wed, Nov 13, 2002 at 09:39:27PM -0800, Josh Sled wrote: > > | At least one crash involving the register which backtraces > into the GUI > | code is a memory-handling problem which I'm working to > solve presently. I'd > | be willing to be these are, as well. > > I've just committed a couple of small but important changes > which I believe > solve all the register-related crashes which have been seen recently. > > | | 2) If you dont have SX's, and try to enter a transaction > with more than > | | one split you will find you can't. If you close and > reopen the register > | | the transaction will show up correctly and allow you to > enter the new > | | split. Basically from what I'm seeing I think the register isn't > | | updating the screen properly. > | > | That I have specifically tried and have seen work... > > I still cannot reproduce this; if anyone can, specific circumstances > and an as-small-as-possible test case [i.e., from an empty file] would > be appreciated. > > | | There could be more problems that I haven't discovered > yet. However, I > | | think we need to resolve the issues above and then go > through and test > > That is true ... though my hope is that this set of changes > will prevent > the release from being delayed much longer. While there are > still known > issues [a lot of GTK-{Critical,Warning}s], I can vouch for > each of them: > they won't seriously impact functionality and will be easily > resolvable. > The majority of the remaining register-related issues should > be resolved > this weekend, and ready for the next beta. > > Testing from the recently-vocal parties [Nathan, Laurent] would be > appreciated; if you can still reproduce the issue, please > file a bug at > bugzilla.gnome.org, assigned to me -- jsled-gnomebugs (at) > asynchronous > (dot) org. > > ...jsled > > -- > http://www.asynchronous.org - `a=jsled; b=asynchronous.org; > echo ${a}@${b}` > jabber:[EMAIL PROTECTED], ICQ:4983267, {AIM,YIM}:joshsled > _______________________________________________ > gnucash-devel mailing list > [EMAIL PROTECTED] > http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel > _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
