Thread Subject: ButtonPressFcn behaves strangely

Hi,

I am running a GUI with an axes in it. When I start the GUI
the axes are empty. During this time I am able to click on
the figure and return a (diagnostic) message. I did the same
for the GUI itself, and both work.

% --- Executes on mouse press over axes background.
function axes1_ButtonDownFcn(hObject, eventdata, handles)
disp('mouse button pressed on axes1');


% --- Executes on mouse press over figure background.
function figure1_ButtonDownFcn(hObject, eventdata, handles)
disp('mouse button pressed on figure1');

But once I use image(frame) to display a frame in the axes,
axes1_ButtonDownFcn can not be called anymore by mouse
clicks on the axes, although figure1_ButtonDownFcn still can
get called by mouse clicks on the figure background. This
puzzles me quite a bit. Any ideas how I could fix this so
that ButtonDownFcn continues to work after image(frame)?

Thanks,
J

"jay vaughan" <jvaughan5.nospam@gmail.com> wrote in message
<g0ch73$79t$1@fred.mathworks.com>...
> Hi,
>
> I am running a GUI with an axes in it. When I start the GUI
> the axes are empty. During this time I am able to click on
> the figure and return a (diagnostic) message. I did the same
> for the GUI itself, and both work.
>
> % --- Executes on mouse press over axes background.
> function axes1_ButtonDownFcn(hObject, eventdata, handles)
> disp('mouse button pressed on axes1');
>
>
> % --- Executes on mouse press over figure background.
> function figure1_ButtonDownFcn(hObject, eventdata, handles)
> disp('mouse button pressed on figure1');
>
> But once I use image(frame) to display a frame in the axes,
> axes1_ButtonDownFcn can not be called anymore by mouse
> clicks on the axes, although figure1_ButtonDownFcn still can
> get called by mouse clicks on the figure background. This
> puzzles me quite a bit. Any ideas how I could fix this so
> that ButtonDownFcn continues to work after image(frame)?
>
> Thanks,
> J


"jay vaughan" <jvaughan5.nospam@gmail.com> wrote in message
<g0ch73$79t$1@fred.mathworks.com>...
> Hi,
>
> I am running a GUI with an axes in it. When I start the GUI
> the axes are empty. During this time I am able to click on
> the figure and return a (diagnostic) message. I did the same
> for the GUI itself, and both work.
>
> % --- Executes on mouse press over axes background.
> function axes1_ButtonDownFcn(hObject, eventdata, handles)
> disp('mouse button pressed on axes1');
>
>
> % --- Executes on mouse press over figure background.
> function figure1_ButtonDownFcn(hObject, eventdata, handles)
> disp('mouse button pressed on figure1');
>
> But once I use image(frame) to display a frame in the axes,
> axes1_ButtonDownFcn can not be called anymore by mouse
> clicks on the axes, although figure1_ButtonDownFcn still can
> get called by mouse clicks on the figure background. This
> puzzles me quite a bit. Any ideas how I could fix this so
> that ButtonDownFcn continues to work after image(frame)?
>
> Thanks,
> J

Sorry for the quick reply...I wanted to add that mouse
clicks at the very edge of the axes do call
axes1_ButtonDownFcn, but not mouse clicks in the interior.
If it is helpful, I am also using a function to return mouse
position, although disabling this function (i.e. removing
the WindowButtonMotionFcn callback) did not restore the
mouse clicks in the interior of the axes after image(frame).

J

The image is in front of the axes so you are clicking the
image, not the axes. Turn the hittest property of the image
off and you'll be fine.

"matt dash" <n.a@mail.com> wrote in message
<g0cjg8$qke$1@fred.mathworks.com>...
> The image is in front of the axes so you are clicking the
> image, not the axes. Turn the hittest property of the image
> off and you'll be fine.
>
>

Matt,

that worked perfectly. Thanks!


J