Button assignment. Any ideas?

[Janis]

The lack of hardware keys (without the keyboard attatched) on the x7501 was my biggest reservation while deciding to buy it. Now I'm having trouble with AEBPlus and HButton (would be perfect if I could use AEBPlus & assgn Hbuttons to the Long Press mode, but it doesn't work). I can't seem to get the flexibilty in button assignments like I had wiith my wizard, I think because a lot of the long keypresses are OS assigned and not UI available.

I don't want to start reg hacking in my random ways if someone has more experience, or better software ideas, and would be willing to share it.

(I keep my unit in the case without the buttons locked when it's in standby, so if I hit a hdwe key, I only have to do that once to get a specific Mortbutton menu up. 2 gestures to anything is my goal. Hbutton often can allow only 1, but I only get 2 keys out of it CommMgr/Record & Camera, my "IE" button longpress seems to be commandeered by VueFlo (cute but pretty useless). If I use that the AEBPlus doesn't seem to work on the other keys.)

UPDATE: I reinstalled AEBPlus, this time with the PC/Activesync installer instead of the cab. The cab installation I did didn't seem to change things. In any case, AEBPlus is working now.

Thanks!

 

[wgary]

The lack of hardware keys (without the keyboard attatched) on the x7501 was my biggest reservation while deciding to buy it. Now I'm having trouble with AEBPlus and HButton (would be perfect if I could use AEBPlus & assgn Hbuttons to the Long Press mode, but it doesn't work). I can't seem to get the flexibilty in button assignments like I had wiith my wizard, I think because a lot of the long keypresses are OS assigned and not UI available.

I don't want to start reg hacking in my random ways if someone has more experience, or better software ideas, and would be willing to share it.

(I keep my unit in the case without the buttons locked when it's in standby, so if I hit a hdwe key, I only have to do that once to get a specific Mortbutton menu up. 2 gestures to anything is my goal. Hbutton often can allow only 1, but I only get 2 keys out of it CommMgr/Record & Camera, my "IE" button longpress seems to be commandeered by VueFlo (cute but pretty useless). If I use that the AEBPlus doesn't seem to work on the other keys.)

Thanks!

AEButton will generally do long presses, double presses, and triple presses... if they are available. As you mention, this seems to be a hardware problem. Example, the "e" (internet) button uses the long press to activate/deactivate the motion sensor within your browser.

As a former Wizard owner, I know where you are coming from. Remapping the "e", "record", and "Win" buttons has given me about 9 quick launches, one of which is WkTask which gives another 12 on a pop-up panel--not to mention showing all open windows on the top bar. Also, the big screen makes iLauncher usable. And I still use good-ole SmallMenu. So I'm doing OK with opening things quickly. But I do miss having all those button launches from the Wizard.

 

[Janis]

Doing better

HButton and AEBPlus don't play well together at all.

I'm on AEBPlus, post flash, and don't get any long-presses, but I have 3 possiblilities on each of the buttons. Along with MortButtons and actually using the CommMgr instead of hdwe keys, I seem to be getting along well enough.

I had the basic edit commands (select all, copy, cut, paste) assigned to a key in AEBPlus, and turn on/off BT and WiFi. That's what I miss. I use MortButtons for it now, so it's a two-step process, but it works.

 

[AE]

The problem with "long keypress'es" for many buttons like Ok/Win/VueFlo etc) is caused by keyboard driver implementation and may not be resolved on application level. The button driver returns both "key was pressed" and "keys was released" events simultaneously, right after button was phisically released. So application could not define time period button was in pressed state to decide if it was long or short keypress...

As for BPlus configuration for my Athena (I have no keyboard at al and use bplus only):

* Button 2 (40C2): (IE button)
1: Call default handler
2: "Messaging"
3: "Notes"

* Button 3 (40C3): (wireless manager)
1: Rotate Screen
2: Show Actions Menu
3: Switch Flashlight Off/On

* OK key (4075):
1: Press Green Button
2: "Contacts"
3: "Calendar"

* Windows key (405B):
1: "Notes"
2: "File Explorer"
3: Show Actions Menu

* Enter/Action (000D):
1: Call default handler
Long: Task Manager

* Volume Up (0075):
Change volume or...
1: Volume Up
2: Backlight Up
Long: Backlight Level 10

* Volume Down (0076):
Change volume or...
1: Volume Down
2: Backlight Down
Long: Backlight Level 1

Action menu items:
Rotate Screen
Switch BlueTooth off/on
Switch WiFi Off/On
Trigger Online
Disable "Power off if not used"...
Device Lock

P.S.: I reviewed this forum very occasionaly so you'd better to ask me via e-mail if any

 

[nonegiven]

AE, love the program but have one problem. The "ok/close" function is never "close", just always "ok".

The only way that I know of to map the OK button to really be "ok/close" is to configure an hbutton key to be "ok/close" and then use AEbplus to make that hbutton.lnk to the OK key. It's a bit convoluted and requires both programs being loaded and running (hbutton uses more memory than aebplus), but it's the only way to make it work.

Any way to fix the "ok/close" function in AEbplus? Even when there is an "X" in the upper right corner, AEbplus only minimizes the app, never closes.

 

[cktlcmd]

Has anyone tried remapping or assigning the keyboard buttons to launch applications?

===

 

[maile76]

Is it possible to get the Half-Press-Function of the Camera-Button assigned for normal working(windows-mode, not camera-mode)??

greetz