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 721290 - SX Editor: Pressing "Enter" too soon hides transaction
SX Editor: Pressing "Enter" too soon hides transaction
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
2.6.0
Other Windows
: Normal normal
: ---
Assigned To: gnucash-core-maint
gnucash-core-maint
: 721979 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-12-31 21:02 UTC by John Ralls
Modified: 2018-06-29 23:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Ralls 2013-12-31 21:02:19 UTC
On Dec 31, 2013, at 11:06 AM, PK <fourteenone@gmail.com> wrote to gnucash-users:

Follow-up to #3
I reinstalled 2.6 and I do not see the issue when using the General Ledger. I do still see the issue when creating SX.

Open Scheduled Transaction Editor. Click New. Enter name "Test SX 001", leave default options on Overview and Frequency. On Template Transaction tab, there are two green rows (with Date, Num, Description, Tot Funds In, Tot Funds Out {no fields are editable}) and the cursor is in the yellow rows just below (with Scheduled, Num, Description, Tot Funds In, Tot Funds Out, and Notes). I can enter values into the Num, Description, and Notes fields. I click into the blank TX split row below and the top green rows change (to Action, Memo, Account, R, Debit Formula, Credit Formula) and I can enter values into the (now yellow, single row I clicked in). I enter values for Memo, Account, Debit and hit enter and the values are cleared blank again (on the whole panel).
If after entering the data in the TX split row, instead of hitting enter, I click back to the top TX description row, the values stay and I get a new TX split row below and can enter values (after which, hitting enter works fine). However, at this point, if I try to hit 'OK' to save and close it, I get "The Scheduled Transaction Editor cannot automatically balance this transaction. Should it still be entered?"
If I create the SX without hitting enter (click above the row, then enter the 2nd half of the entry (one row for credit, one row for debit) it'll save and run it, but when looking at the general ledger at that point, it just shows a long hex value in the account field for both rows and the funds in/out and both blank.

It seems that hitting enter in the SX edit form saves the row, but hides it (creating the imbalance if the second row wasn't entered with the matching credit/debit).
Comment 1 John Ralls 2013-12-31 21:04:15 UTC
Subsequent investigation on my part shows that if the transaction isn’t complete, pressing Enter hides the whole transaction and presents a new, blank transaction, which is why it seems to disappear. I’ve managed to make an SX with three transactions, two of which are single-split and one of which is a proper two-split transaction. Even when I close and reopen the editor the single-split transactions don’t appear, but when the SX runs it creates all three transactions in the normal registers. Everything in those transactions looks normal, including in the GL. This on Win7-64.
Comment 2 Mike Alexander 2014-01-11 07:01:45 UTC
Do the single split transactions disappear because of the change in r23585?
Comment 3 John Ralls 2014-01-11 20:22:24 UTC
Yup. Good call.
Comment 4 John Ralls 2014-01-12 14:58:39 UTC
*** Bug 721979 has been marked as a duplicate of this bug. ***
Comment 5 John Ralls 2014-01-13 02:13:45 UTC
r23692.

The problem was that r23585 was a bit too broad in what it excluded, so
narrow it down to require exactly one split and that that split's
account is NULL.

Note that this will still cause the split to disappear from the SX
editor if one creates a transaction with no splits or with one that has
no account: A split will be created in the appropriate Orphan account.
It will be visible there and in the General Ledger so that it can be
easily deleted.

Please test tonight's nightly.
Comment 6 John Ralls 2018-06-29 23:23:10 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=721290. Please update any external references or bookmarks.