[Octave-bug-tracker] [bug #52361] Ctrl-C/Ctrl-V only works reliably if executed as very first action

[Philip Nienhuis]

Follow-up Comment #5, bug #52361 (project octave):

Thank you for enlightening me, Torsten.

All shortcuts looked to be the proper (default) ones before I touched anything
in the Shortcuts pref pane.
It must be one of clicking the "Default" button, or "Export" to some file (I
couldn't find afterwards, but that's another story).

It makes me think of Jordi's "nasal daemons". But also of some
(un)initialization issue.

That preferences are version-independent does not quite match my experience.
If I run an older version of Octave, say 4.03 or 4.2.0, the next time I start
4.3.0+ the GUI pane settings & positions are royally screwed up. 
The other way round works fine, that is, older versions work well with
qt-settings files from newer versions. And IMO, when you think about it, that
makes perfect sense with what I see.
You write: /"The qt-settings file should not be version dependent. If there is
a new preference in a new version, a default value is used if the preference
is not found in the existing settings file."/
Those older Octave versions overwrite the qt-settings files upon exit (don't
they?), so a newer Octave version started afterwards has to make do with an
existing qt-settings made by an older version. So indeed, it then fills in
default values for non-default settings it had stored before the older version
removed them. Does that scenario make sense to you?

For me this is really an issue. I was even thinking of amending the octave.vbs
files or m/startup/__finish__.m to copy qt-settings files around.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52361>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/