togglemenu doesnt work

[siliman]

[siliman]

[esw]

[siliman]

I did a test where I bound Aux 1-4 all to togglemenu.
All bring up the main menu, but none take it away.

I then realized that this must be due to togglemenu being a console command which may not work when the main menu is up.

Still, in portrait mode, the Menu button on the display does toggle the menu on and off.

So if a code change was made that let Aux 1 be able to call the same c-subroutine that is presently called by pressing the menu button on the display.

I saw in the PQ readme.txt file, that togglemenu was fixed to work with aux2 on mips devices...maybe I'll try this on my old cassio e-125.

apparently the record button on the ipaq is used to escape or cancel out of a menu, but the record button on the axim doesnt seem to be seen by PQ or wolf.

so i think togglemenu needs a code change for the axim.

who knows how to do this?

I only paid $175 for my axim 300 (after 10% discount and $50 rebate)...so I cant really complain

[esw]

[Dan East]

Normally in Quake no keybindings are active when the menus or console is up. I had to modify the menu routine to allow a specific key to be bound while the menu was active, so you could exit in landscape mode. Aux2 worked properly on all devices until now...

Dan East

[siliman]

[sponge]

[siliman]

ok I did what you said, created autoexec.cfg with only the command unbindall in it (not in quotes). None of the buttons show anthing on the screen. When I start PQ, the demo starts up, and I can tap on menu on the screen to toggle the main menu. once the menu is up I can move up and down the menu using the D-pad and can select an item using the 5th button on the D-pad (i.e., pushing straight in now works after installing the new patch from Dell). So I can start a new single player game. once the new game starts, none of the keys do anything or print anything to the screen. I can still access the main menu by tapping on the on-screen menu button with the stylus, and then exit the game gracefully. None of the buttons work during the demo either.

Any other ideas?

ps. Thanks for thinking about this!

[sponge]

[esw]

[sponge]

Weird, I swear I saw the message before..

I guess your best bet is to do something like this

bind aux1 "echo aux1"
bind aux2 "echo aux2"
bind aux3 "echo aux3"

etc, go up to around 10 or so.

[siliman]

ok I did like you said for aux1-12, i.e.,
bind aux1 "echo aux1"
bind aux2 "echo aux2"
bind aux3 "echo aux3"
...
bind aux11 "echo aux11"
bind aux12 "echo aux12"

Then I do get the echos, for aux1 through aux4, which are the front 4 buttons on the axim, from left to right. When I press straigt in on the D-pad, I get:
JOY1 IS UNBOUND, HIT F4 TO SET

Pushing straight in on the d-pad gives the same message:
JOY1 IS UNBOUND, HIT F4 TO SET

The directionals on the D-pad turn and move me in the game as normal. Also, the console button on the screen now works, whereas it didn't with only the unbindall command the autoexec.cfg file.

The record button still shows nothing.

[siliman]

scanned the c-source...
In keys.c, found the following:

//Dan East: Allow our skin keys to register when menu is up
#ifdef _ARM_
menubound[K_AUX5]=true;
#elif defined(_MIPS_)
menubound[K_AUX2]=true;
#else
//Don't know what this should be for HP, etc.
menubound[K_AUX5]=true;
#endif

so how can we determine what key the record button is on the axim. The record button does in fact work to bring up the Notes program (without PQ running).

It must not be an aux key.

[sponge]

Then PQ will require an update apparently. I can't help anymore, as I don't have access to the device, nor do I have the ability to write a program that'll figure out what the key does. I think MameCE3 can help, it shows the key's code in the button config.