Unexpected Revert Behavior

[David T.]

Cheryl,

I’d have to say, probably “Yes.”

As in, I believe that the Revert feature closes a file and then initiates the Open command (which is intended design), but that the program assumes a single opened file, and thus that Revert can therefore assume that GnuCash’s default Open command (which automatically opens the last file accessed) will result in the correct file being reopened. SInce you had most recently opened file B, the Revert function on file A would invoke the Open on the last opened file (file B). I imagine that if you were to open file A, and then file B, and then revert file B, it would do what you expect.

It might be nice to have the Revert command re-programmed to track which file is being reverted and then reopen that file, but realistically, it’s a pretty rare circumstance, and probably wouldn’t garner a lot of developer interest, unless it were a trivial change to code.

Not speaking as a programmer or accountant, or anything else, of course. YMMV, etc. and so on.

David

> On Mar 7, 2016, at 3:32 PM, Cheryl Wheeler <c_wheeler_2002 at yahoo.ca> wrote:
> 
> I have two Gnucash files/books. Yesterday, I opened File A and then File B in two separate instances of Gnucash. After working on File A for a bit, I decided that I wanted to revert those changes, so I selected File > Revert. Gnucash closed File A without saving (so, that's good), but then it opened File B, giving me two instances with File B. I expected it to reopen File A after the changes were discarded.
> 
> Is this a bug or design intent?
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.