MATLAB Answers

Can you program a figure to execute the same callback after each child's callback?

2 views (last 30 days)
Dominik Mattioli
Dominik Mattioli on 11 Jul 2019
Commented: Walter Roberson on 11 Jul 2019
Essentially, I'd like a callback that is for the figure and all of it's children, but is executed last. Of course, you could manually enter this code for every single callback, but perhaps there is a more elegant way?
fh = figure()
button1 = uicontrol('Parent', fh, 'Callback', button1_Callback)
button1 = uicontrol('Parent', fh, 'Callback', button2_Callback)
%...
buttonN = uicontrol('Parent', fh, 'Callback', buttonN_Callback)
function button1_callback(hObject, eventD, fh)
% Do stuff specific to this object.
% Perform this action (***I don't want to type this for every single callback***)
fh_callback(fh, eventD, fh); % Example.
end
function button2_Callback(hObject, eventD, fh)
% Do stuff specific to this object.
% Perform this action (***I don't want to type this for every single callback***)
fh_callback(fh, eventD, fh); % Example.
end
%...
function buttonN_Callback(hObject, eventD, fh)
% Do stuff specific to this object.
% Perform this action (***I don't want to type this for every single callback***)
fh_callback(fh, eventD, fh); % Example.
end

  6 Comments

Show 3 older comments
Walter Roberson
Walter Roberson on 11 Jul 2019
set(ancestor(hObject, 'figure'), 'currentobject', ancestor(hObject, 'figure'))
But I would just add a function call at the end of each of the callbacks to do this work.
Another approach is
hObject.Enable='disable'
hObject.Enable='on'
That is, disable an object removes its focus.
You could also add a figure window button down callback: that should fire after the individual callback.
Dominik Mattioli
Dominik Mattioli on 11 Jul 2019
Are you sure that a WindowButtonDownFcn callback will fire after each uibutton's callback? My test right now only fires when the mouse clicks on panels, axes.

Sign in to comment.

Answers (1)

Steven Lord
Steven Lord on 11 Jul 2019
Are you setting the figure object's CurrentObject property back to the figure object itself because your callbacks query the CurrentObject to determine what component to query or modify? That could be dangerous -- all it would take would be the user clicking in the wrong place at the wrong time to potentially break your UI by making the CurrentObject not what your callbacks expect it to be.
Instead, I would store the handles of the components in your UI and share the stored handles among the callbacks. That way you don't need to care what the current CurrentObject is, you can refer to either the object whose callback is currently executing (the first input to the callback function) or to a specific object whose handle is in the shared data.

  1 Comment

Dominik Mattioli
Dominik Mattioli on 11 Jul 2019
I was asking the question in the abstract because I think it could be helpful to others also, but to be more specific, I am setting the CurrentObject property back to the figure object itself so that clicking on uibuttons (and running their respective callbacks) does not disable quick keys that I've programmed for the UI.
Unless there is a property of uicontrols that prevents the current object from remaining on that button itself (absent a user-intervening mouse click on say, any other non-button object of the UI), this seems like it is necessary.

Sign in to comment.

Products


Release

R2018a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!