From: Corey Kelly on
Walter Roberson <roberson(a)hushmail.com> wrote in message <lLGKn.29596$rE4.22700(a)newsfe15.iad>...
> Corey Kelly wrote:
>
> > In terms of flexibility, and simplicity, does it make more sense for me
> > to be doing this in terms of a ginput() call, or a buttondown callback
> > for my axis? I can't seem to get either method to produce any results.
>
> I believe ginput() requires that the program pause and wait for the
> click, which would imply the frames would stop playing (unless possibly
> they were updated in a timer callback, but even then I'm not sure:
> ginput flushes the queue but once it thinks it has flushed the queue I
> am not sure that interrupts would be processed.)

I was leaning towards the buttondown callback anyway. Any ideas why my callback isn't producing any results? I'm testing it without the image stack playing for the time being, and still can't get any response, even though I've set all the hittest properties.
From: Walter Roberson on
Corey Kelly wrote:

> I was leaning towards the buttondown callback anyway. Any ideas why my
> callback isn't producing any results? I'm testing it without the image
> stack playing for the time being, and still can't get any response, even
> though I've set all the hittest properties.

Sorry, no idea at the moment. If it were a hittest problem, then
clicking outside of the images should get you the axis callback.

I do not recall at the moment whether you indicated which Matlab version
you are using?
From: Corey Kelly on
Walter Roberson <roberson(a)hushmail.com> wrote in message <TFIKn.37401$304.13037(a)newsfe12.iad>...
> Corey Kelly wrote:
>
> > I was leaning towards the buttondown callback anyway. Any ideas why my
> > callback isn't producing any results? I'm testing it without the image
> > stack playing for the time being, and still can't get any response, even
> > though I've set all the hittest properties.
>
> Sorry, no idea at the moment. If it were a hittest problem, then
> clicking outside of the images should get you the axis callback.
>
> I do not recall at the moment whether you indicated which Matlab version
> you are using?

I don't seem to get the callback by clicking outside of the image either. I'm using 2010a.
From: Corey Kelly on
"Corey Kelly" <ckelly01(a)uoguelph.ca> wrote in message <htflih$t3e$1(a)fred.mathworks.com>...
> Walter Roberson <roberson(a)hushmail.com> wrote in message <TFIKn.37401$304.13037(a)newsfe12.iad>...
> > Corey Kelly wrote:
> >
> > > I was leaning towards the buttondown callback anyway. Any ideas why my
> > > callback isn't producing any results? I'm testing it without the image
> > > stack playing for the time being, and still can't get any response, even
> > > though I've set all the hittest properties.
> >
> > Sorry, no idea at the moment. If it were a hittest problem, then
> > clicking outside of the images should get you the axis callback.
> >
> > I do not recall at the moment whether you indicated which Matlab version
> > you are using?
>
> I don't seem to get the callback by clicking outside of the image either. I'm using 2010a.

So this is an interesting development, hopefully it will help.
I was debugging this problem and discovered the following. I've got 'visible' set to 'off' for my axis so that there's nothing in the GUI until the image is loaded. I tried setting it to 'on', and in that case, if I click on the axis before loading an image, I get the buttondown callback. I still don't get the callback after loading the image, though.
Any ideas what this means? Seems like there's still something fishy going on with my hittest properties.
From: Steven Lord on

"Corey Kelly" <ckelly01(a)uoguelph.ca> wrote in message
news:hth88t$8hv$1(a)fred.mathworks.com...
> "Corey Kelly" <ckelly01(a)uoguelph.ca> wrote in message
> <htflih$t3e$1(a)fred.mathworks.com>...
>> Walter Roberson <roberson(a)hushmail.com> wrote in message
>> <TFIKn.37401$304.13037(a)newsfe12.iad>...
>> > Corey Kelly wrote:
>> >
>> > > I was leaning towards the buttondown callback anyway. Any ideas why
>> > > my callback isn't producing any results? I'm testing it without the
>> > > image stack playing for the time being, and still can't get any
>> > > response, even though I've set all the hittest properties.
>> >
>> > Sorry, no idea at the moment. If it were a hittest problem, then
>> > clicking outside of the images should get you the axis callback.
>> >
>> > I do not recall at the moment whether you indicated which Matlab
>> > version you are using?
>>
>> I don't seem to get the callback by clicking outside of the image either.
>> I'm using 2010a.
>
> So this is an interesting development, hopefully it will help.
> I was debugging this problem and discovered the following. I've got
> 'visible' set to 'off' for my axis so that there's nothing in the GUI
> until the image is loaded. I tried setting it to 'on', and in that case,
> if I click on the axis before loading an image, I get the buttondown
> callback. I still don't get the callback after loading the image, though.
> Any ideas what this means? Seems like there's still something fishy going
> on with my hittest properties.

Are you taking this into account?

http://www.mathworks.com/support/solutions/en/data/1-3K8R2L/?solution=1-3K8R2L

IMAGE is a high-level plotting function and by default it does restore many
of the axes properties (including ButtonDownFcn) to their default values
when called.

--
Steve Lord
slord(a)mathworks.com
comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
To contact Technical Support use the Contact Us link on
http://www.mathworks.com


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11
Prev: mbuild -setup doesn't see my compiler
Next: Using imcontrast