David,
I think your workaround (changing the default view session-by-session)
will probably have to do for now -- at least as a temporary solution for
my purposes. I also can agree that asking for a per-account-type View
setting is probably a bit more complicated than necessary. Just being
able to set and save the register views individually
(register-by-register) would be a great improvement. And I think it
would be fairly straightforward to implement that via the gcm files;
since the Column Widths are already being stored there when a Save is
done. Hopefully it wouldn't be much harder to save the View flag there
as well.
I'm a bit torn between whether to call this a bug or an RFE. I kind of
feel like the View setting got left out of the Save function by mistake
(i.e., it's a bug). But after hearing both your feedback and Adrien's,
I guess it's probably more appropriate to consider this a feature
request instead. So unless someone else in Bugzilla already has an open
Bug report, I'll just plan on submitting an RFE. Anyway, thanks for all
your input on this.
Tom
On 12/15/2025 8:28 PM, [email protected] wrote:
Tom,
I don't recall anyone making this request in my time using GnuCash (19
years). But I think your observations and suggestions merit
consideration.
My workaround has been to change the default view on a
session-by-session basis, depending on the general type of accounting
work I have to do, but this is clunky at best.
TBH, it never occurred to me in all my years of use-- but I definitely
could use a per-register or per-account-type view setting. It would be
very helpful!
I imagine a per-register setting could be saved in the same gcm file
that the column widths are stored.
Adding the capability to set register defaults by account type would
get messy rather quickly and could lead to additional confusion for
future users. Where are these settings made? Where are they stored?
What happens when a user has changed individual registers and then
attempts to make an account type default? Who decides what the
'normal' register type is for different account types? And so on.
This is not to say I wouldn't want to have this; just that with
complexity, the likelihood of implementation goes down.
The other comments in the thread about the steps needed to save a
register's column widths (change the settings, exit GnuCash without
closing the register, and then reopen GnuCash) suggest to me that a
more robust and user-friendly method for maintaining a register
customization (e.g., saving whenever a register is closed, in addition
to when GnuCash itself is closed) might also help with those sorts of
issues. But that's a slightly different topic.
David T.
On Dec 16, 2025, at 7:59 AM, Tom Route36 <[email protected]> wrote:
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
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.
