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 770136 - "Reverse Order" in "View"->"Sort by" is not saved
"Reverse Order" in "View"->"Sort by" is not saved
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: User Interface General
2.6.4
Other All
: Normal normal
: ---
Assigned To: gnucash-ui-maint
gnucash-ui-maint
Depends on:
Blocks:
 
 
Reported: 2016-08-19 10:46 UTC by Dominik
Modified: 2018-06-29 23:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dominik 2016-08-19 10:46:44 UTC
Hi,

it seems, that the checkbox for "Reverse Order" is not saved, even though "Save Sort Order" is checked. Every setting in this dialogue is saved and correctly restored, when reopening an account, but not the "Reverse Order".

I can confirm this problem in 2.6.4, 2.6.13 and 2.6.12 under Linux and 2.6.13 under macOS.

This problem could probably relate to https://bugzilla.gnome.org/show_bug.cgi?id=710905 but I am not sure.

Thanks for checking
Comment 1 Mike Evans 2016-08-19 14:30:41 UTC
See bug 683881 which probably covers this and partly explains why I never implemented it.

See also any bugs relating to register2 which was intended to completely replace the existing register display and so making any work I did pointless in the long run. Although I didn't realise that the reg2 code would be delayed this long.
Comment 2 Dominik 2016-08-19 19:29:33 UTC
Thanks for checking into this. So, this means, for foreseeable future the saving of "Reverse Order" will not be realized? Or is there a known timeframe for register2? 


(In reply to Mike Evans from comment #1)
> See bug 683881 which probably covers this and partly explains why I never
> implemented it.
> 
> See also any bugs relating to register2 which was intended to completely
> replace the existing register display and so making any work I did pointless
> in the long run. Although I didn't realise that the reg2 code would be
> delayed this long.
Comment 3 Mike Evans 2016-08-19 19:58:44 UTC
Well. It means "I'm" not doing it. Someone else can obviously. Patches are always welcome.
Comment 4 Dominik 2016-08-20 06:01:04 UTC
Ok, understood :) Do you probably know the time-schedule for the register2?

(In reply to Mike Evans from comment #3)
> Well. It means "I'm" not doing it. Someone else can obviously. Patches are
> always welcome.
Comment 5 Geert Janssens 2016-08-24 10:01:28 UTC
Ok, I decided to fix this as there's no clear roadmap for the new register code.

This fix will go into the next gnucash release (2.6.14).

Note that older versions of gnucash will obviously completely ignore the saved state, yet it will be kept in the data. So the next time you open your data file with gnucash 2.6.14 or more recent the saved state will be honoured again.
Comment 6 Dominik 2016-08-24 13:26:20 UTC
Also here, thank you very much :) I am looking forward for the release 2.6.14


(In reply to Geert Janssens from comment #5)
> Ok, I decided to fix this as there's no clear roadmap for the new register
> code.
> 
> This fix will go into the next gnucash release (2.6.14).
> 
> Note that older versions of gnucash will obviously completely ignore the
> saved state, yet it will be kept in the data. So the next time you open your
> data file with gnucash 2.6.14 or more recent the saved state will be
> honoured again.
Comment 7 John Ralls 2018-06-29 23:50:40 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=770136. Please update any external references or bookmarks.