Fullscreen mode on devices with hardware button

[Thomas Senyk]

ok seems I'm not going to have time this week 
... maybe next, or in a month or so ;)

anyway ... seems I'm the only one having problems with that for now (and I can 
live with it at the moment)

... so I'll going to investigate further when I find some time for it

Greets
Thomas

On Monday, May 14, 2012 04:05:20 PM Thomas Senyk wrote:
> Ah, ok: it's DeclarativeView.
> 
> One can't "view->showFullScreen()" in you main.cpp because it will be
> overwritten/reset "later".
> 
> ... but if you set a timer and do it even later again, you can switch forth
> and back (fullscren<->maximized)
> 
> 
> I guess the problem is that DeclarativeView isn't the TLW itself, it has a
> viewport it "forwards" all the widget-stuff to.
> 
> 
> I'm now building a android-qt and look into androidjnimain.cpp :
> setFullScreen ... maybe I find out how to prevent the "setFullScreen false"
> for the declarativeview case
> 
> Greets
> Thomas
> 
> On Saturday, May 12, 2012 12:53:51 AM ext BogDan wrote:
> > Hey Thomas,
> > 
> > Long time no see !
> > 
> > It should be fixed, please make sure that you are not using any hack!
> > Check the attachment.
> > 
> > Cheers,
> > BogDan.
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > 
> > > From: Thomas Senyk <thomas.senyk at nokia.com>
> > > To: necessitas-devel at kde.org
> > > Cc: ext BogDan <bog_dan_ro at yahoo.com>; android-qt
> > > <android-qt at googlegroups.com>; Marco Bernasocchi
> > > <marco at bernawebdesign.ch> Sent: Friday, May 11, 2012 3:47 PM
> > > Subject: Re: Fullscreen mode on devices with hardware button
> > >
> > >T hat's not fixed in the released libs/plugins, right?
> > >
> > > I tried several ways (including AndroidManifest.xml) but nothing is
> > > working.
> > > 
> > > The problem I actually have is that some when down the road I got
> > > several
> > > D/Qt      ( 4373): setFullScreen true         and
> > > D/Qt      ( 4373): setFullScreen false
> > > 
> > > 
> > > ... some of my opengl-resources (created and manager via c++) are
> > > created
> > > between 2 of those and get invalid after  "setFullScreen false"
> > > 
> > > ... I know how to hack around it, but I guess if there is a solution for
> > > that it would be good if there aren't too much (no?) fights between true
> > > and false
> > > 
> > > :)
> > > 
> > > ... what would be really cool: if you could overwrite everything with
> > > the
> > > 
> > > AndroidManifest.xml:
> > >     android:theme="@android:style/Theme.NoTitleBar.Fullscreen"
> > > 
> > > ... that could(!) mean you only got one "setFullScreen true" and all
> > > other are
> > > blocked.
> > > 
> > > 
> > > 
> > > Again: I can hack around this problem, nothing urgent :)
> > > 
> > > Greets
> > > Thomas
> > > 
> > > On Thursday, March 29, 2012 08:06:25 AM ext BogDan wrote:
> > >>  Hi,
> > >>  
> > >>  I think I know why it happens, please open an issue, I'll fix it
> > >>  before
> > >>  alpha4.
> > >>  
> > >>  Cheers,
> > >>  BogDan.
> > >>  
> > >>  Sent from Yahoo! Mail on Android