Re: [iPAQ] Prboom xmodmap mappings?

On Tue, May 08, 2001 at 09:33:05AM -0500, Cpt_Kirks wrote:
> OK, what keys are you using? I guess <space> to fire and...?

Ask Tangent, I think he did a nice modmap for it. Anyway, the day I will
package this up for Familiar 0.4, I will need to package a modmap with it :-)

> That may be possible. A cruder method I use for xgb and xmame is to launch
> them with a script that maps the keys for the game, then remaps them to the
> default on exit. Not great, but if you don't try to run other programs that
> need button input at the same time as the game, it gets the job done.

Yeah, but well, if we want consistency, we should put all this in common
somewhere. I do not want to have 15 different launching scripts that sets
the keyboard for each app.

If ever we manage to do a 'one app == one desktop == full screen' kind of
environment, we should have a key mapping per desktop and have some WM hints
so that the app can ask the window manager to set a specific keymap.

> Is the constant output to the console (frame xxx...) debugging data? How do
> you exit cleanly? <cntrl> <c> works sometime, but hangs the iPAQ others.
> Remapping the buttons so I can use the menu should fix that.

I usually quit by going to the menu (doing an escape with 'fstroke' when I
think of starting non-full screen), or by 'kill' using my desktop :-)

And 'frame ...' is some debug data. I do not remember though if I added it
or if it was already there :-)

> Where did you compile prboom? On the skiff? Is you source (with a working
> makefile) available? I need to get gcc up on my udrive...

I built prboom on my Intimate-powered iPAQ. And the source is at 99.9 % the
standard prboom release, except for some __attribute__((packed)) added :-)
(apparently, ARM and x86 GCC do not pack things the same way).

I will look at the latest prboom release, see if I can get my iPAQ patch
incorporated, and then it should compile out of the box.

         Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/