Reply
Thread Tools
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#191
here ya go. this is NOT a release, as i havent tested it. literally havent even run it, sorry.

this deb has new conditions: screenUnlocked, appNotFocused
and new buttons: cameraButton {n950}, powerButton


all you do to configure n9bm how i said, is change /home/user/.config/n9-button-monitor.ini

Code:
doubleClickDelayMs=2000
trebleClickDelayMs=3000
action=cmd(SECURITY-LOCK-CMD),powerButton,singleClick,screenUnlocked
by the way, this assumes you HAVE a command that will enter security lock mode. i have no idea how to do that, and it has nothing to do with n9bm.
Attached Files
File Type: deb n9-button-monitor_0.5.2_armel.deb (20.2 KB, 94 views)
__________________
~ teleshoes ~
 

The Following User Says Thank You to wolke For This Useful Post:
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#192
ok, i tested it, and it works fine.

turns out double-click-power IS useful. it will work in lock, unlock, and different apps, where the volume buttons already have actions reserved.

it could, for instance, toggle power saving mode when locked, open my most recent pictures in meeseepics if im on the home screen, and toggle silent/ring everywhere else.
__________________
~ teleshoes ~
 

The Following User Says Thank You to wolke For This Useful Post:
solbrit's Avatar
Posts: 126 | Thanked: 59 times | Joined on Jan 2011
#193
Thankyou!
I just installed the deb, although no /home/user/.config/n9-button-monitor.conf (or /home/user/.config/n9-button-monitor.ini) is created. Is this normal? Do i grab the one in OP and throw it in there (changing it according to your instrucions)?

Edit: ...you load the default config file from the ui, got it!

Last edited by solbrit; 2013-02-24 at 18:55.
 
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#194
Originally Posted by solbrit View Post
Thankyou!
I just installed the deb, although no /home/user/.config/n9-button-monitor.conf (or /home/user/.config/n9-button-monitor.ini) is created. Is this normal? Do i grab the one in OP and throw it in there (changing it according to your instrucions)?

Edit: ...you load the default config file from the ui, got it!
oh snap, i thought the default one got created when the file didnt exist. apparently not, so thats a bug i should fix.

i wouldnt recommend using the gui for anything at all ever.
__________________
~ teleshoes ~
 
solbrit's Avatar
Posts: 126 | Thanked: 59 times | Joined on Jan 2011
#195
It works perfectly, thankyou!

Btw, the torch feature is really nice too. No more unlock-screen-locate-flashlight-app-in-the-app-menu-activate-flashlight...

Last edited by solbrit; 2013-02-24 at 19:40.
 
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#196
Originally Posted by solbrit View Post
It works perfectly, thankyou!

Btw, the torch feature is really nice too. No more unlock-screen-locate-flashlight-app-in-the-app-menu-activate-flashlight...
cool. glad you like it!
__________________
~ teleshoes ~
 
Posts: 359 | Thanked: 322 times | Joined on Jun 2010
#197
There is a great new open source camera app for the N9 located here: http://talk.maemo.org/showthread.php?t=89278

I think that this could be my new default camera app, but I don't want to lose the Button Monitor camera functions.

Could you set up Button Monitor so that this camera app can be a new condition name in the GUI? Is there an easy way I can make this happen?
__________________
Hitting this thanks button will make you smile and feel good ----------------------------------------------------------------->
 

The Following 2 Users Say Thank You to Hacker For This Useful Post:
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#198
AWESOME! im so excited, i despise the n9 camera app. thanks for this news, ill be checking it out very soon.

now, its very easy to do the condition. you just do appFocused(window-class-name). default camera app is "camera-ui", and his is probably "camera-plus".

cameraFocused == appFocused(camera-ui)
both do exactly the same thing.


now as for the ACTIONS, theyre a little trickier.
what they really do is simulate dragging your finger to certain spots on the screen. if he moved the camera button a little, it will break.

so if he DID move the button, you will need to play with the "tap" action. again, clickCameraSnap and clickCameraFocus are just shorthand for the tap action with an argument.

these do exactly the same thing:
clickCameraSnap == tap(820x240,820x240)
clickCameraFocus == tap(820x240-820x100*200+5)
__________________
~ teleshoes ~
 

The Following 3 Users Say Thank You to wolke For This Useful Post:
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#199
i lied, its not class name, its WM_COMMAND.
so you dont even have to use xprop to find out, you can just use the executable name.
__________________
~ teleshoes ~
 

The Following 2 Users Say Thank You to wolke For This Useful Post:
Posts: 986 | Thanked: 1,526 times | Joined on Jul 2010
#200
btw, released 0.5.2
buttons: camera {n950}, power
conditions: screenUnlocked, appNotFocused
actions: tap {generic click}
__________________
~ teleshoes ~
 

The Following 2 Users Say Thank You to wolke For This Useful Post:
Reply

Tags
harmattan, nokia n9


 
Forum Jump


All times are GMT. The time now is 11:30.