[Octave-bug-tracker] [bug #53275] Variable Editor: Undocking variable window causes it to become nearly full screen

[Dan Sebald]

Follow-up Comment #2, bug #53275 (project octave):

Yes, I put that behavior in on purpose, knowing that it would evolve into
something else.  This was for a couple reasons.  First, I didn't like that
pressing the undock icon/button in the upper right corner would make the
undocked window the exact same size right on top of where it was.  One
couldn't tell that anything happened when in fact it did undock.

So, I thought I could make the undocked pane a certain default size, centered
or something.  What to do?  But then I also thought that something users would
like to do is expand the tiny docked window for a quick look at the table in a
much wider view, and then press a button and put it back to the small size. 
So, this behavior is just meant to illustrate that idea.

We can take this out easy enough:


        // Make initial size expanded very large for "magnified" viewing
        if (m_initial_float)
          {
            // This will be resolved based on user feedback and preference
            // and will eventually work without QGuiApplication.  Perhaps
            // a maximize button added to the label_dock_widget windows
            // along with the dock/undock and close buttons is best.
#if defined (HAVE_QGUIAPPLICATION)
            QScreen *pscreen = QGuiApplication::primaryScreen ();
            QRect rect (0, 0, 0, 0);
            rect = pscreen->availableGeometry ();
            rect = QRect (rect.x () + 5, rect.y () + 5,
                          rect.width () - 10, rect.height () - 10);
            setGeometry (rect);
            m_initial_float = false;
#endif
          }


but the big question is what *should* the behavior be for best general use? 
What would user's prefer?  Perhaps this sort of thing can be discussed at
OctConf.  My thinking is that we'll end up putting some kind of "fullscreen"
or "maximize" button alongside the dock/undock button, but I didn't want to go
down that path without getting user feedback and getting back to a stable
location because cleanup and better structure of the V.E. classes was a part
of this, which JWE is working on.

    _______________________________________________________

Reply to this item at:

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

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