[Top][All Lists]

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

[Octave-bug-tracker] [bug #62748] Inconsistent behavior for gca / gco /

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #62748] Inconsistent behavior for gca / gco / gcf / gcbo / gcbf
Date: Mon, 11 Jul 2022 15:13:54 -0400 (EDT)

Update of bug #62748 (project octave):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 


Follow-up Comment #1:

`gca` and `gcf` need to create objects for compatibility (both with existing
code and with Matlab). `gco` could point to a range of different objects. It
wouldn't make sense to create a "random" one. (And compatibility again.)
`gcbo` and `gcbf` are specific to callbacks (which must have existing

If you'd like get the handle to the current figure without creating a new one
if none exists, use this:

get (0, 'CurrentFigure')

If you'd like to get the handle to the current axes of a figure without
creating new axes if none exists, use this:

hf = figure ();  % or some other source for a figure handle, e.g.,  `gcf`
get (hf, 'CurrentAxes')

In general, if you have questions about the usage of Octave, the discourse
forum might be a better platform than the bug tracker:

Closing as invalid.


Reply to this item at:


Message sent via Savannah

reply via email to

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