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 344494 - Gnucash thinks the file has changed after cancelling out of the Since Last Run dialog and making no changes
Gnucash thinks the file has changed after cancelling out of the Since Last Ru...
Status: VERIFIED OBSOLETE
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
git-master
Other Linux
: Normal normal
: ---
Assigned To: Josh Sled
Josh Sled
Depends on:
Blocks:
 
 
Reported: 2006-06-10 17:02 UTC by Tim Wunder
Modified: 2018-06-29 21:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim Wunder 2006-06-10 17:02:23 UTC 
(May be related to bug #34493)
Gnucash thinks the file was changed (and needs to be saved) after starting then cancelling out of the Since Last Run dialog (just start it, then click Cancel and Yes when asked if you're sure you want to cancel). Not sure if that's a related bug or not.
Behavior first notived in r14347 and still exists in r14352.

Steps to duplicate:
Open gnucash datafile with SX's.
DO NOT CHANGE ANYTHING
Start the Since Last Run Dialog
Click Cancel
Click Yes
Click File-Quit

Expected results:
GnuCash closes without asking whether the user wants to save the file because of changes made.

Actual results:
GnuCash present the user with the dialog that asks the user to save the file because changes were made.
Comment 1 Tim Wunder 2006-06-12 14:45:57 UTC 
er, I meant: may be related to bug #344493
Comment 2 Chris Shoemaker 2006-06-17 01:13:56 UTC 
Did you leave out the steps where you advanced to the last page, the register, of the SLR druid?
Comment 3 Chris Shoemaker 2006-06-17 01:23:10 UTC 
Assuming answer to comment #2 is 'yes', this is because of the way that SX are created.  They really do modify the book.

Josh, I see two options:
1) make the SLR druid modal.  Then we can save book dirty state at the beginning of the druid and restore it upon cancel.

or...

2) just put this off as a post-2.0 sx rework thing.

What do you think?
Comment 4 Tim Wunder 2006-06-18 03:37:15 UTC 
Answer to comment #2 is no. I just started the SLR, and then cancelled. But I am unable to duplicate this behavior since moving to FC5, using r14369.
Comment 5 Josh Sled 2006-06-18 17:01:58 UTC 
(In reply to comment #3)
> 2) just put this off as a post-2.0 sx rework thing.
> 
> What do you think?

I don't think spurious book modification is important, but this is definietly a post-2.0 thing, anyways.
Comment 6 Josh Sled 2007-01-20 23:01:53 UTC 
Obsolete on trunk, post-15399 (sx-cleanup branch merge).  Transactions will only be created if there were auto-create transactions.  There's no longer a druid with "Apply" semantics to be incorrect.
Comment 7 John Ralls 2018-06-29 21:07:50 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=344494. Please update any external references or bookmarks.