After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347474 - (tabbing) Register: Tab goes to wrong split
(tabbing)
Register: Tab goes to wrong split
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: Register
2.0.x
Other Linux
: Normal minor
: ---
Assigned To: Andreas Köhler
Chris Shoemaker
: 360557 375035 380386 388931 469041 507142 (view as bug list)
Depends on:
Blocks: backport
 
 
Reported: 2006-07-14 02:56 UTC by Mark Johnson
Modified: 2018-06-29 21:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
First try (764 bytes, patch)
2008-03-28 23:29 UTC, Andreas Köhler
committed Details | Review

Description Mark Johnson 2006-07-14 02:56:01 UTC
While entering a transaction with multiple splits, I tab through the fields.  After the second split, tabbing brings me back to the first split and not to the third.

I have gnucash 2.0.0 on Slackware 10.0, linux version 2.6.15.

The register is set to "Auto-split" in preferences.

Steps:
1. Open an account register.
2. Enter a description
3. Tab through the fields to the amount.  Enter it.
4. Tab until you reach the account field of the second split.  Choose an account.  Tab to the amount.  Enter one.
5. Hit tab twice more.
6. Observe that you are now editting the first split again rather than the third one as expected.
Comment 1 Julian Gilbey 2006-08-28 20:07:48 UTC
Happens to me too.  I haven't yet checked whether or not this only occurs when all of the entries balance so far, so that there is no residual amount to account for.  The behaviour in 1.8.x was not like this.
Comment 2 Julian Gilbey 2006-08-29 13:09:59 UTC
Correction to previous comment: this occurs whether or not the entries balance so far, as long as it is a new entry in the General Ledger (haven't checked other entry methods).
Comment 3 Mark Johnson 2006-08-31 01:30:32 UTC
I have not been using the General Ledger.  I open the register for the asset/liability account from which payment is to be made.

I have upgraded to 2.0.1 and still observe this behaviour.

I have noticed that whenever there is another split below the current one, it will correctly tab to that split.  For example, when a blank split is below the current one, you can tab to it.  However, when you are on the very last split, tabbing to the "next" split arrives at the first split rather than creating a new one.  I have been pressing the up arrow to go up one split (this creates a new one at the bottom with the remaining imbalance) and then down arrow twice to get to the new split.

Comment 4 Chris Shoemaker 2006-10-16 03:28:25 UTC
*** Bug 360557 has been marked as a duplicate of this bug. ***
Comment 5 Josh Sled 2006-11-15 14:31:14 UTC
*** Bug 375035 has been marked as a duplicate of this bug. ***
Comment 6 Christian Stimming 2006-11-29 09:45:47 UTC
*** Bug 380386 has been marked as a duplicate of this bug. ***
Comment 7 Mark Johnson 2006-12-07 03:00:32 UTC
I have built trunk svn 15187 and it still occurs with this version.  This one is on a system using gtk+ 2.8.20.

It also occurs on a system with gtk+ 2.10.6 and gnucash 2.0.1.
I had thought that trying it with a newer gtk might have an effect, but it didn't.  Gnucash 2.0.1 was rebuilt after the upgrade.
Comment 8 Iustin Pop 2006-12-24 13:17:22 UTC
It happens to me too. I can add that this new behaviour was introduced late in the 1.9.something or 2.0 rc series, it was not present from the beginning of the gtk 2 implementation.
Comment 9 Jonathan Kamens 2007-01-08 03:07:42 UTC
When I'm entering a split transaction in an account window (not general ledger) with gnucash 2.0.2, and I hit tab on the last split, I move back to the date field of the transaction instead of moving to the next split line.  This is exceedingly annoying.  This bug is almost six months old, sort of amazing that no developer has done anything with it in six months.
Comment 10 Mark Johnson 2007-01-08 04:04:53 UTC
I have upgraded to gnucash 2.0.4.  It still has this bug.


Comment 11 Josh Sled 2007-01-17 04:13:29 UTC
*** Bug 388931 has been marked as a duplicate of this bug. ***
Comment 12 Josh Sled 2007-08-27 18:57:02 UTC
*** Bug 469041 has been marked as a duplicate of this bug. ***
Comment 13 Josh Sled 2008-01-07 16:29:33 UTC
*** Bug 507142 has been marked as a duplicate of this bug. ***
Comment 14 Andreas Köhler 2008-03-28 23:29:03 UTC
Please check out the attached patch and test it thoroughly.
The register can a beast, so really stress test it :-)
Comment 15 Andreas Köhler 2008-03-28 23:29:42 UTC
Created attachment 108196 [details] [review]
First try
Comment 16 Andreas Köhler 2008-04-12 19:19:45 UTC
Applied as r17078 and marked for backport to branches/2.2.  This is still open
for comments and needs regression tests :-)
Comment 17 David Reiser 2008-04-13 03:52:15 UTC
I haven't tested thoroughly, but it looks good initially. I'm really happy that this one might be fixed! Thanks. I'll report again after I've used current trunk for several days.
Comment 18 Andreas Köhler 2008-04-26 17:05:17 UTC
26-13 == 13 > 7, cool :-)

Applied to branches/2.2 as r17137 for GnuCash 2.2.5.
Thanks for the patience.
Comment 19 John Ralls 2018-06-29 21:09:36 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=347474. Please update any external references or bookmarks.