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

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

[Octave-bug-tracker] [bug #64985] Figure windows ignoring 'windowstate'


From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #64985] Figure windows ignoring 'windowstate' property
Date: Tue, 5 Dec 2023 10:27:08 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?64985>

                 Summary: Figure windows ignoring 'windowstate' property
                   Group: GNU Octave
               Submitter: nrjank
               Submitted: Tue 05 Dec 2023 10:27:06 AM EST
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 9.0.90
         Discussion Lock: Any
        Operating System: Any
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Tue 05 Dec 2023 10:27:06 AM EST By: Nicholas Jankowski <nrjank>
[https://octave.discourse.group/t/figure-cannot-be-maximized/5066 As reported
over on discourse], attempting to use the 'WindowState' property for figures
seems to have no effect, whether during creation or later using the set
command. 

Tested on Windows with Octave 8.4.0 and 9.0.1 (hg id: 14cb31ec0251), as well
as on Ubuntu with 9.0.0 (hg id: 4f09c1b4148).

the following commands all produce a normally sized figure window:


figure (1, "windowstate", "maximized") %new named fig
figure ("windowstate", "maximized") %new fig unnamed
figure (1, "windowstate", "maximized") %new fig into existing fig


similarly:

a = figure;
set (a, "windowstate", "maximized")


fails to change the state of the window.  same behavior for "minimized", and
"fullscreen".  Tested on single and multiple monitor setups in case the latter
was causing the problem.

can anyone verify if this behavior is a regression or was it always
nonfunctional parameter?







    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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