>I love the menu that pops up when the power button is pressed in SHR. It allows the user to quickly choose what they want to do in a nice clean interface suitable >for the touchscreen. However, I hate that the only action associated with the AUX button is locking illume. This option is already implemented by selecting the >"lock" button from the power button menu. Duplicating this functionality is bad as we such limited tactile input.
+1 agreed. I've assigned the Alt button to bring up the phone app via the illume "wrench" settings (input | key bindings). I thought that a rotate button on the power button menu might be useful, but I think I like your idea below better, except that I've lost a quick way to access the phone quickly. How easy is it to add a function button (maybe user configurable) to the power menu? >Short press: bring up/get rid of the keyboard (because clicking the tiny qwerty button is a pain) >Long press (2 secs): Rotate the screen to the current accelerometer reading. If the keyboard doesn't come up automatically, it takes 2 taps to get it. Rotation right now is currently a mess (IMO) >Where is the aux's lock functionality defined? I realize I can probably set both of these by setting some rules in the rules.yaml to call a bash script on the dbus->message occuring....but is this the correct way? >How would I go about disabling the current illume-lock on aux functionality? As mentioned above, it's currently assigned by E's input settings. You can actually assign a program or a script to it quite easily by choosing the command option and putting that into the form field. The limitation here I believe is you can't capture long press, short press events. Russell Dwiggins
_______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
