[maemo-developers] Details on the information required to replace the tklock (touchscreen/key lock) systemui plugin
From: David Weinehall david.weinehall at gmail.comDate: Tue Jul 5 16:24:49 EEST 2011
- Previous message: Details on the information required to replace the tklock (touchscreen/key lock) systemui plugin
- Next message: Can anyone tell me how the N900 vibrator driver works?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5 July 2011 13:18, Jonathan Wilson <jfwfreo at tpgi.com.au> wrote: [snip] > The SYSTEMUI_TKLOCK_OPEN_REQ handler gets passed a uint argument for the > lockscreen mode, can be TKLOCK_ENABLE, TKLOCK_ONEINPUT or > TKLOCK_ENABLE_VISUAL. TKLOCK_ONEINPUT is for the blank screen lock mode > (called "event eater mode" in the code) and TKLOCK_ENABLE_VISUAL is for the > slide to unlock screen. Not sure what TKLOCK_ENABLE is for exactly. TKLOCK_ENABLE was used for the tklock in earlier versions of Maemo (where you'd press the power button followed by center button to unlock). > The second parameter is a boolean argument labeled "silent" by the code. The > code says "true = disable infoprints, false = enable infoprints". The third > parameter is a flag that seems to indicate if there is a "flicker key" > (whatever that is). Both the second and third parameters seem to be ignored > by the stock tklock plugin. The flicker key is the lock key available on the N810 and N900; the 770 and N800 doesn't have one. Called flicker because it's not a slider key -- it "flickers" back. And indeed these parameters are ignored. Regards: David
- Previous message: Details on the information required to replace the tklock (touchscreen/key lock) systemui plugin
- Next message: Can anyone tell me how the N900 vibrator driver works?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]