View Single Post
Old 04-08-2013, 01:42 PM   #10
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Yeah. I do that because BY DEFAULT some machines (Including mine) DISABLE going to screensaver.

Thus the "Press Button to Exit" thing would "do nothing"

Quote:
SSSTATE=`lipc-get-prop com.lab126.powerd preventScreenSaver` # The previous setting
lipc-set-prop com.lab126.powerd preventScreenSaver 0 # prevent screensaver for the application lifetime
that (as you know) STORES the previous selection. So I don't have to reset it after I exit the application.

When the application is full screen there is no status bar. And with no Home Button obviously the user is "stuck" inside the application.

This works on the touch too by the way, just press the power button to test it.

: )

I recognise the Eureka? call to fix the status bar visibility.

I restarted pillow as a dirty hack. and added the TODO to make it tidier.

so I guess restart pillow could read

Code:
lipc-set-prop com.lab126.pillow interrogatePillow '{"pillowId": "default_status_bar", "function": "nativeBridge.showMe();"}'
instead

Last edited by twobob; 04-08-2013 at 02:54 PM.
twobob is offline   Reply With Quote