octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53276] GUI: undocked panes cannot be moved, o


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #53276] GUI: undocked panes cannot be moved, or resized along upper border
Date: Mon, 2 Apr 2018 15:27:51 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1

Follow-up Comment #67, bug #53276 (project octave):

Got home early from vacation, so I just tested.

In short: doesn't help much.

Longer:

- The Editor pane (was undocked before I started Octave) cannot be moved by
the title bar. It just has a spot in the lower right corner, in the status
bar, where the pane can be dragged bigger and smaller, that's it.

- The Variable Editor (VarEd) was docked. I can drag it out of Octave's main
window, and i stays there. And it can be dragged by its title bar, and all
around it has spots where the cursor changes in a resize cursor.
*BUT*: 
It is an unstable situation. After a while, or after some fiddling, suddenly
the undocked VarEd pane changes position & size and morphs in a similar
behavior as the Editor pane - no more movable by its title bar, no more
resizing (not even in the lower right corner).

This behavior applies to any pane. Docking and undocking the Editor pane, or
any other pane, works similarly, but after a while the medicine's half-life
seems to have passed :-)

In summary, it seems to help for a while just after a pane was undocked. 
It seems completely unpredictable when the change from moveable to unmoveable
occurs. It looks (flagrant guesswork!) like it has to do with focus and
re-focussing.

@Dan:
- Given the discussion in this bug report and in bug #53409;
- Given the fact that this seems due to a Qt-5.6.1 to 5.7.0 bug;
- Given that -from what I read- few distros use Qt 5.6.1 to 5.7.0;
- Given that I have Q t5.6.2 on my development Linux box but mainly use Octave
on Windows where mxe-octave has a much later Qt;
- just to repeat what I wrote in an earlier bug report discussion:

==> is it really worthwile to you to invest loads of time fixing a workaround
for this upstream bug?
Mind you, I am very grateful to you that you try, I regularly use Octave on
Linux as well but for me this bug is not a showstopper - and after all, I
suppose Mageia will update Qt anyway sometime.
It's up to you. If you still want to go on, I'm prepared to let my Linux boxes
serve as guinea pigs for your patches etc. As long as I get clear instructions
:-)


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]