Register really broken

[Neulinger, Nathan]

Does not fix the crash when closing a register window that was popped up
from reconcile.=20

It's actually worse now, I now also get a crash when closing a register
window that wasn't opened from reconcile.=20

Doesn't fix the goofy tab/cant-add-a-split behavior either.=20

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:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Josh Sled [mailto:jsled@asynchronous.org]=20
> Sent: Thursday, November 14, 2002 2:40 AM
> To: Chris Lyttle; Gnucash
> Subject: Re: Register really broken
>=20
>=20
> On Wed, Nov 13, 2002 at 09:39:27PM -0800, Josh Sled wrote:
>=20
> | At least one crash involving the register which backtraces=20
> into the GUI
> | code is a memory-handling problem which I'm working to=20
> solve presently. I'd
> | be willing to be these are, as well.
>=20
> I've just committed a couple of small but important changes=20
> which I believe
> solve all the register-related crashes which have been seen recently.
>=20
> | | 2) If you dont have SX's, and try to enter a transaction=20
> with more than
> | | one split you will find you can't. If you close and=20
> reopen the register
> | | the transaction will show up correctly and allow you to=20
> enter the new
> | | split. Basically from what I'm seeing I think the register isn't
> | | updating the screen properly.
> |=20
> | That I have specifically tried and have seen work...
>=20
> 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.
>=20
> | | There could be more problems that I haven't discovered=20
> yet. However, I
> | | think we need to resolve the issues above and then go=20
> through and test
>=20
> That is true ... though my hope is that this set of changes=20
> will prevent
> the release from being delayed much longer.  While there are=20
> still known
> issues [a lot of GTK-{Critical,Warning}s], I can vouch for=20
> each of them:
> they won't seriously impact functionality and will be easily=20
> resolvable.
> The majority of the remaining register-related issues should=20
> be resolved
> this weekend, and ready for the next beta.
>=20
> Testing from the recently-vocal parties [Nathan, Laurent] would be
> appreciated; if you can still reproduce the issue, please=20
> file a bug at
> bugzilla.gnome.org, assigned to me -- jsled-gnomebugs (at)=20
> asynchronous
> (dot) org.
>=20
> ...jsled
>=20
> --=20
> http://www.asynchronous.org - `a=3Djsled; b=3Dasynchronous.org;=20
> echo ${a}@${b}`
> jabber:jsled@jabber.asynchronous.org, ICQ:4983267, {AIM,YIM}:joshsled
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel@lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>=20