broken register entry

David Reiser dbreiser at earthlink.net
Mon Apr 24 09:16:16 EDT 2006


On Apr 24, 2006, at 1:30 AM, Chris Shoemaker wrote:

> On Mon, Apr 24, 2006 at 12:57:55AM -0400, David Reiser wrote:
>> Something in r13833-13835 seriously broke transaction entry for me.
>
> Almost certainly 13834.  I have no doubt that this change had
> unintended consequences.  Please help me fix it by providing more info
> on how the behavior has changed.
>
>> I
>> couldn't complete a transaction in autosplit mode
>
> "couldn't complete"?  What happened instead?  Is this unique to  
> autosplit?
In autosplit mode, neither carriage return nor clicking the Enter  
toolbar button would calculate the balance and put the cursor in a  
new blank transaction. Tabbing through the last empty split after  
completing another split that balanced the transaction would keep me  
cycling through the fields in the empty split (normal) -- unless I  
hit carriage return or the Enter toolbar button, in which case I was  
pinned in the last field of the empty split (and still no balance  
calculated)

With View set to Basic, 2-line mode, I could tab through a  
transaction and into a new transaction, but the balance of the just  
completed transaction showed 0.00

Somewhere along the line (about 2 out of 15), I got gnucash to fully  
accept a transaction (calculate accurate balance, move to new  
transaction), but I couldn't figure out what I had done.

>
>> unless I clicked on
>> another transaction.
>
> So keynav-ing to another transaction had a different effect than
> clicking on it?  How?
I didn't try arrow key navigating to another transaction, just tab  
and return. I don't think I even tried return in Basic 2-line...

>
>> Most transactions that did get retained
>
> "retained"?  Does this mean some transactions are not retained?  Which
> ones? When?
oops. It was late. All text entered remained in a register, unless I  
quit gnucash and relaunched. Then the transactions showing 0.00  
balance had disappeared.
>
>> showed a
>> Balance of 0.00,
>> when obviously there should have been some other
>> balance.
>
> Hmm, I see that, too.
>
>> If I saved the file, quit GnuCash, and relaunched, any of
>> the transactions with the 0.00 balance had disappeared.
>
> And that, too.
>
> *sigh* I've been waiting all evening for someone to find something
> wrong with that commit and now it's too late to look at tonight.  I'll
> look at this more closely in the morning.
>
> Well, it's comforting to know that somebody notices when I break
> things. :)
Well, I usually wait until things settle for a couple hours before  
trying a major modification. But I was interested in seeing if the  
Orphans went away.

>
> -chris
>
>>
>> reverting to 13832 restored usual behavior.
>> Dave

--
David Reiser
dbreiser at earthlink.net



More information about the gnucash-devel mailing list