[Octave-bug-tracker] [bug #65499] Use separate GUI settings for Octave releases

[Torsten Lilge]

Follow-up Comment #2, bug #65499 (group octave):

A downside would be that carefully selected settings, like, e.g., the editor
styles are not available in other octave versions.

I would like to handle user defined settings files (per environment variable
or per command line argument) differently from version aware settings files.
In the latter case, what about still having one file but adding the version
number to the names of potentially critical preferences, i.e. those that are
internally processed by Qt like window or table view states (generally of type
QByteArray)? In the derived settings class, the methods for reading settings
could check for the version-matching preference name and take older or no
versions as fallback.     


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65499>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/