Thread Subject: Instantiation of multiple images in a GUI

I'm trying to instantiate an unique image within each axes object of my GUI. Unfortunately, this becomes problematic after the first image. I am using imread and imshow in the callback of each axes object. Is there any alternative?

Thanks

On Nov 19, 12:43=A0pm, "Thiago Jota" <thi...@mathworks.com> wrote:
> I'm trying to instantiate an unique image within each axes object of my G=
UI. Unfortunately, this becomes problematic after the first image. I am usi=
ng imread and imshow in the callback of each axes object. Is there any alte=
rnative?
>
> Thanks

---------------------------------------------------------------------------=
---------------------------
Thiago Jota:
Don't load images into the axes in the callback of the axes. You can
do it in the callback of your listbox or some other function. You
click on an image filename in your listbox, or set it in your function
somehow. Then in the call back of the listbox, or in that other
function, you can call imread and imshow. Before you call those
however, make sure you call the axes function and pass it the handle
to the axes where you want the image displayed.

Clicking on an axes is problematic because once an image is thrown
into it, I think it essentially lies on top of the axes and you can
never click on the axes again because it's underneath the image -
you're clicking on the image which is a child of the axes and you'd
have to set up a callback for that image which is separate from the
callback of the axes that it lives in. Really quirky, I know.
Regards,
ImageAnalyst

I've found a solution! After creating axes objects in GUIDE, place this code inside each "axes_CreateFcn" callback:

axes(hObject)
imshow('file.extension');
title('')

I am able to instantiate multiple images in the same figure with this technique, which originated from this tutorial by Doug Hull:

http://blogs.mathworks.com/pick/2007/10/16/matlab-basics-setting-a-background-image-for-a-gui/

On Nov 19, 3:54=A0pm, "Thiago " <thi...@mathworks.com> wrote:
> I've found a solution! After creating axes objects in GUIDE, place this c=
ode inside each "axes_CreateFcn" callback:
>
> axes(hObject)
> imshow('file.extension');
> title('')
>
> I am able to instantiate multiple images in the same figure with this tec=
hnique, which originated from this tutorial by Doug Hull:
>
> http://blogs.mathworks.com/pick/2007/10/16/matlab-basics-setting-a-ba...

-------------------------------------------------------------------
Yes, most of the time you need to call the axes command to set the
current graphics object (the "gca") to the one you want to put stuff
into before you put the stuff in. So that's why it worked for you.
It's a bit puzzling though. You'd think that inside the creation
callback for the axes, that the gca would already be that axes, but
maybe not. In other words I'm surprised you had to do that because
you'd think that that would have already been done automatically
without you having to explicitly do it. Maybe that doesn't occur
until the creation callback completely terminates. But if that were
the case, (the axes weren't yet full created) then how could you issue
an axes() command to it?

The tutorial I cited explains why.

ImageAnalyst <imageanalyst@mailinator.com> wrote in message <236663b5-3953-416e-a6d9-256634da7feb@g38g2000yqd.googlegroups.com>...
> On Nov 19, 3:54=A0pm, "Thiago " <thi...@mathworks.com> wrote:
> > I've found a solution! After creating axes objects in GUIDE, place this c=
> ode inside each "axes_CreateFcn" callback:
> >
> > axes(hObject)
> > imshow('file.extension');
> > title('')
> >
> > I am able to instantiate multiple images in the same figure with this tec=
> hnique, which originated from this tutorial by Doug Hull:
> >
> > http://blogs.mathworks.com/pick/2007/10/16/matlab-basics-setting-a-ba...
>
> -------------------------------------------------------------------
> Yes, most of the time you need to call the axes command to set the
> current graphics object (the "gca") to the one you want to put stuff
> into before you put the stuff in. So that's why it worked for you.
> It's a bit puzzling though. You'd think that inside the creation
> callback for the axes, that the gca would already be that axes, but
> maybe not. In other words I'm surprised you had to do that because
> you'd think that that would have already been done automatically
> without you having to explicitly do it. Maybe that doesn't occur
> until the creation callback completely terminates. But if that were
> the case, (the axes weren't yet full created) then how could you issue
> an axes() command to it?