Geoaxes zoom not working after adding ButtonDownFcn.
32 views (last 30 days)
Show older comments
Peter Valent
on 19 May 2021
Edited: Jan Kappen
on 27 Jan 2025 at 11:23
I have an app built in AppDesigner with a map plotted in geoaxes. I need to zoom in and out but I also need to do some action when I click on the map. The problem is that:
- zoom works perfectly when no buttondownfcn is added
f = uifigure;
gx = geoaxes();
geoscatter(gx,10,10)
- zoom does not work at all when buttondownfcn is added.
f = uifigure;
gx = geoaxes(f);
geoscatter(gx,10,10)
gx.ButtonDownFcn = 'disp(''hello'')';
I need to use both functionalities. What should I do?
0 Comments
Accepted Answer
Adam Danz
on 20 May 2021
Edited: Adam Danz
on 22 Jan 2025 at 20:42
I'm not sure why assigning the button down function affects the zooming but it can be fixed by resetting the default interactivity of the axes. Note: This solution stopped working in R2023a.
gx = geoaxes;
geoscatter(gx,10,10)
enableDefaultInteractivity(gx) % * <-- must be before assigning ButtonDownFcn
gx.ButtonDownFcn = 'disp(''hello'')';
Update
This solution works beyond R2023a. It creates an event listener on the figure that responds any time a mouse button is pressed within the the figure. The listener callback checks whether the mouse button press was within the geoaxes before executing a simple display action.
fig = figure();
gax = geoaxes(fig);
geoscatter(gax,10,10)
event.listener(fig, 'WindowMousePress', @(src,evt)ButtonDownResponseFcn(src,evt,gax));
function ButtonDownResponseFcn(~,evt,gax)
% gax is the geoaxes handle. Check whether the hit object was the geoaxes.
if isequal(evt.HitObject, gax)
disp('Geoaxes hit!')
end
end
10 Comments
Adam Danz
on 22 Jan 2025 at 20:43
@Jan Kappen, check out my updated answer for another workaround. I tested it in R2023a and R2025a.
Jan Kappen
on 27 Jan 2025 at 11:14
Edited: Jan Kappen
on 27 Jan 2025 at 11:23
Dear @Adam Danz beautiful, so the key point is no to use the ButtonDownFcn, or WindowMousePress, which appararently kills all default axis interactions (so why in hell are the callback properties empty then?), but to add an additional listener to the fired event.
Awesome, thanks!
Edit: all those events seem to be hidden and thus not really wanted to be accessed?
events("matlab.ui.Figure")
There are way more including the one you mentioned.
m = ?matlab.ui.Figure; string({m.EventList.Name})'
More Answers (1)
Jan Studnicka
on 21 May 2021
"Sometimes MATLAB® automatically disables the built-in interactions. For example, they might be disabled for charts that have special features, or when you implement certain callbacks such as a WindowScrollWheelFcn."
However, with geoaxes you can easily implement zooming in / out by using WindowScrollWheelFcn callback of the uifigure. This is an example created from the documentation's example on "how to use WindowScrollWheelFcn":
function scroll_wheel
% Shows how to use WindowScrollWheelFcn in combination with geoaxes and
% ButtonDownFcn callback.
f = uifigure('WindowScrollWheelFcn',@figScroll,'Name','Scroll Wheel Demo');
gx = geoaxes(f);
geoscatter(gx,10,10)
gx.ButtonDownFcn = 'disp(''hello'')';
title(gx,'Rotate the scroll wheel')
function figScroll(~,event)
if event.VerticalScrollCount > 0
gx.ZoomLevel = gx.ZoomLevel-0.1;
elseif event.VerticalScrollCount < 0
gx.ZoomLevel = gx.ZoomLevel+0.1;
end
end
end
1 Comment
Adam Danz
on 21 May 2021
Edited: Adam Danz
on 21 May 2021
+1 Good idea, Jan. Note that this zooms into the center of the axes rather than zooming into the location of the cursor within the axes.
It's still not clear to me why a ButtonDownFcn would prevent zoom interaction since that callback function does not respond to the scroll wheel. I also find it odd that adding the ButtonDownFcn disables zoom interaction but calling enableDefaultInteractivity can turn it back on in regular figures - that sounds buggy to me. Lastly, I wonder why applying enableDefaultInteractivity doesn't fix the problem with uifigures.
BTW, I also get the same interative warning when zooming in/out using this method (r2021a)
Warning: A value of class "double" was indexed with no subscripts specified. Currently the result of this operation is the indexed value itself, but in a
future release, it will be an error.
> In matlab.internal.asynchttpsave/AsyncHTTPContentFileWriter/handleThreadIsFinishedEvent
In matlab.internal.asynchttpsave.AsyncHTTPContentFileWriter
In asyncio/Channel/onPropertyChanged (line 471)
In asyncio.Channel>@(source,data)obj.onPropertyChanged(data.Name,data.Value) (line 401)
There's clearly some cleaning up to do by MW.
See Also
Categories
Find more on Introduction to Installation and Licensing in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!