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

[Markus Mützel]

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
parents).

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:
https://octave.discourse.group/

Closing as invalid.



    _______________________________________________________

Reply to this item at:

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

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