[Octave-bug-tracker] [bug #53207] crash when Octave starts on Windows after removing external 4K display

[Philip Nienhuis]

Follow-up Comment #4, bug #53207 (project octave):

This simply sounds related to stored qt-settings that assume upon the next
start of octave screen dimensions that are no more valid.

@OP: Octave saves all its GUI settings, incl. window positions, into the file
%USERPROFILE%\.config\octave\qt-settngs
If you remove that file Octave should start w/o problems but with default
layout.

I have a somewhat related issue: my work PC has a two-monitor setup where I
have the undocked GUI editor on the right monitor, But often I log in remotely
to that PC from a single-screen PC and then I can't access the editor anymore.
My workarounds are:
- keeping a tiny strip of the editorś pane's left border on the left monitor
so that I can always grab at least part of the editor pane so I can resize it
and then drag it on the left monitor;
- have two separate qt-settings files, one for double-and one for single
monitors, that I copy into place when needed.

Perhaps Octave needs to check saved window positions with current screen
limits and adapt the former if the new screen is much smaller than the
previous one.
Or Octave might have a start-up option (command line option) to select a
specific qt-settings file. On Windows systems that could be organized using
separate .bat or .vbs files for each HW setup.


    _______________________________________________________

Reply to this item at:

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

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