|
This problem can also be caused by trying to debug a program which uses the WindowButtonMotionFcn feature of figures. For example see the draw_lines.m program which comes with Matlab's help system (find it on the line function reference page, in the section titled "Drawing with mouse motion": http://tinyurl.com/ye262co)
If you put a break point in the function called by the motion handler (in this case function wbmcb(src,event)), you will really screw up the graphics engine.
The only way I was able to clear the problem was by closing all figures, then issuing the following in the command window:
close all
close all hidden
"John " <junk@csd.uwo.ca> wrote in message <hig8li$5v6$1@fred.mathworks.com>...
> I have had the same problem. The reason is because you have too many windows (figures) and Java doesn't have enough space. The solution is to use clf before
> each figure with a pause(n), where n is floating point number of seconds after
> the figure.
>
>
> "JL " <a_fake@hotmail.com> wrote in message <fidof6$1fn$1@ginger.mathworks.com>...
> > I am having the same problem when I have more than 100
> > figures. My machine is a Core 2 Duo with 2G memory. Any help?
> >
> > Thanks,
> >
> > Jean
> >
> > "Kelly Kearney" <kakearney@nospamgmail.com> wrote in message
> > <fbs6lm$cib$1@fred.mathworks.com>...
> > > I just encountered the following error, which appears
> > > consistently in a script of mine when trying to plot the
> > > last in a series of 7 figures:
> > >
> > >
> > > ??? Error using ==> figure
> > > UIJ_AreThereWindowShowsPending - timeout waiting for window
> > > to show up.
> > >
> > > Error in ==> plotecosimresults at 9
> > > figure('Units', 'normalized', 'Position', [.1 .1 .8 .8]);;
> > >
> > > Error in ==> test at 31
> > > plotecosimresults(Out, Ewein.name);
> > >
> > >
> > > I'm running R2007a on MacOS X on an Intel Mac. I found one
> > > other thread in the newsgroup mentioning the same error,
> > > also on an intel mac and with the same version of Matlab
> > > (unfortunately with no replies). Anyone know what might be
> > > causing this?
> >
|