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

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

[Octave-bug-tracker] [bug #55428] gcbf and HandleVisibility property


From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #55428] gcbf and HandleVisibility property
Date: Thu, 10 Jan 2019 16:24:28 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Update of bug #55428 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #3:

The code mentioned in comment #1 was added as part of a fix for bug #52621.
Specifically, the implementation relied on this excerpt of ML doc for
"handlevisibility" figure properties [1]:


When the HandleVisibility property value is restricted using the 'callback' or
'off' settings, the object does not appear in the 
parent object Children property, figures do not appear in the 
root CurrentFigure property, objects do not appear in the root
CallbackObject property or in the figure CurrentObject property,
and axes do not appear in their parent CurrentAxes property.
 

I see now that the documentation for uimenu's "handlevisibility"  [2] does not
state that gcbo/gcbf are affected. So the behavior is different for figures
and other objects?
 
What does the following return?


hf = figure ('handlevisibility', 'off', 'buttondownfcn', 'gcbo')
% Click inside the figure


[1]
https://fr.mathworks.com/help/matlab/ref/matlab.ui.figure-properties.html#buiwuyk-1-HandleVisibility
[2]
https://fr.mathworks.com/help/matlab/ref/matlab.ui.container.menu-properties.html#bub8xy5-1_sep_shared-HandleVisibility

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via Savannah
  https://savannah.gnu.org/




reply via email to

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