Thread Subject: set(get(gcf,'JavaFrame'),'Maximized',1)

I'm trying to load a maximized figure. Adding Yair Altman's hack to
the openingFcn function:
set(get(gcf,'JavaFrame'),'Maximized',1);
or even manually changing the size of the figure from within the
openingFcn does indeed work, but only for a few miliseconds because
later on later on gui_mainfcn continues, which in turn calls
movegui('onscreen'), and that, in line 185 of movegui.m [Matlab
r2007a] defines a margin of 30 pixels from the left hand side of the
screen. Hence the figure is again resized and it no longer remains
maximized.

Annoying, to say the least.

Any known hack for this?

Thanks...

Yoav.

Yoav Mor wrote:
>
> I'm trying to load a maximized figure. Adding Yair Altman's hack to
> the openingFcn function:
> set(get(gcf,'JavaFrame'),'Maximized',1);
> or even manually changing the size of the figure from within the
> openingFcn does indeed work, but only for a few miliseconds because
> later on later on gui_mainfcn continues, which in turn calls
> movegui('onscreen'), and that, in line 185 of movegui.m [Matlab
> r2007a] defines a margin of 30 pixels from the left hand side of
> the screen. Hence the figure is again resized and it no
> longer remains maximized.
>
> Annoying, to say the least.
>
> Any known hack for this?
>
> Thanks...
>
> Yoav.
  

Try placing this in your openingFcn:

%timerFcn = 'set(get(gcf,''JavaFrame''),''Maximized'',1)';
timerFcn = @(o,e)
set(get(get(o,'userdata'),'JavaFrame'),'Maximized',1);
start(timer('StartDelay',5,'Userdata',gcf,'TimerFcn',timerFcn));

(Modify the 5-secs timer startup delay to whatever fits your needs)

Yair

im not sure about the whole maximization business, but you can avoid
the annoying 30 pixel border by defining a gui_LayoutFcn up in the
"do not edit" part of the m-file (assuming you used guide to make the
gui)

example:
gui_State = struct('gui_Name', mfilename, ...
    'gui_Singleton', gui_Singleton, ...
    'gui_OpeningFcn', @test_OpeningFcn, ...
    'gui_OutputFcn', @test_OutputFcn, ...
    'gui_LayoutFcn', @test_Layout , ...
    'gui_Callback', []);
  
then add the following function to your mfile:
function h=test_Layout(varargin)
h=openfig('test.fig','new','invisible');

this is just the default figure opening command that your gui
normally uses, but by having it defined in the layout function it
will bypass the annoying resizing.

ps, i start it out invisible and then at the end of the OpeningFcn
turn visibility on to avoid it flickering while it loads. (tested in
2006 a,b)

Thanks matt!

That's the best solution I've found so far!
Works like a charm!

Thanks again,
Yoav.

 matt dash wrote:
>
>
> im not sure about the whole maximization business, but you can
> avoid
> the annoying 30 pixel border by defining a gui_LayoutFcn up in the
> "do not edit" part of the m-file (assuming you used guide to make
> the
> gui)
>
> example:
> gui_State = struct('gui_Name', mfilename, ...
> 'gui_Singleton', gui_Singleton, ...
> 'gui_OpeningFcn', @test_OpeningFcn, ...
> 'gui_OutputFcn', @test_OutputFcn, ...
> 'gui_LayoutFcn', @test_Layout , ...
> 'gui_Callback', []);
>
> then add the following function to your mfile:
> function h=test_Layout(varargin)
> h=openfig('test.fig','new','invisible');
>
> this is just the default figure opening command that your gui
> normally uses, but by having it defined in the layout function it
> will bypass the annoying resizing.
>
> ps, i start it out invisible and then at the end of the OpeningFcn
> turn visibility on to avoid it flickering while it loads. (tested
> in
> 2006 a,b)

Let's try this source code.

jf =get(gcf,'JavaFrame');
jf.fClientProxy.getFrameProxy.getClientFrame.setMaximized(1)

It works.

Best wishes,

Huy Phan