WindowButtonDownFcn vs zoom or pan

In my figure I have some little images; I've implemented WindowButtonDownFcn so when I click on an image, I do something different according to the image selected

The cursor position is checked with WindowButtonMotionFcn

Practically, every little image simulates a button with its callback function. I do this because the graphical aspect of my figure is better, and I can have a 'button' of different shape instead of the square or rectangular button shape. Moreover, I don't have the button outline.

Im my figure I have also an axis, used to plot data.

When I activate the zoom or the panning, the WindowButtonDownFcn function doesn't work, my 'buttons' don't work anymore until I deactivate the zoom or the pan.

This behaviour there is also if I set the zoom (or panning) on programmatically.

Is there a way to avoid this behaviour? I need the WindowButtonDownFcn ALWAYS working.

Thank you

[Ted Londner]

I'm encountering an issue similar to this one. I'd be interested to hear if Giuela's question was ever answered.

Answer 1

[Samay Sagar]

Hi @Giuela and @Ted Londner,

I have also faced a similar issue in the past.

When you assign a “WindowButtonDownFcn” callback to a “uifigure “in App Designer, it overrides the default mouse button behaviour for the entire app window. This can interfere with built-in interactive features such as zooming and panning.

Since MATLAB’s interactions depend on these callbacks, attempting to mix the two can result in unsupported and unpredictable behaviour.

You can consider using the “ImageClicked” callback function to execute your intended logic.

[Ted Londner]

Thanks, @Samay Sagar.