Nokia promoting emulation on their new N900 device, look MSX!

On second thoughts, this patch appears to be problematic for other situations, so we'll have to find another way.

jr, do you know how other SDL apps turn of that compositing stuff?

I can't see any difference in keyboard functionality. I'll try to setup the development environment in a virtual machine, anything specific I should consider? I'm not very familiar with the debian tool chain but I guess I can skip the packaging parts and play with the naked openmsx binary only.

I'll also try to see if I can get some sensible key mapping done but as the N900 has different key maps on different countries I doubt it will be very useful for non-finnish keyboard layouts

I don't know how many apps in general are actually disabling display composition. A quick google for _HILDON_NON_COMPOSITED_WINDOW reveals that for example the N900 port of scummvm (I hope you know the project) is using it and that is also using SDL. Here's a copy&paste from the scummvm's graphics.cpp:

#include "SDL_syswm.h"

static void maemo5_WM_init(int fullscreen){
//static int fsdone=0;
//static int wmdone=0;
SDL_SysWMinfo info;                                                                                                                                  
SDL_VERSION(&info.version);                                                                                                                          
if ( SDL_GetWMInfo(&info) ) {                                                                                                                        
	Display *dpy = info.info.x11.display;                                                                                                        
	Window win;                                                                                                                                  
	unsigned long val = 1;
        Atom atom_zoom = XInternAtom(dpy, "_HILDON_ZOOM_KEY_ATOM", 0);
	info.info.x11.lock_func();
	win = info.info.x11.fswindow;                                                                                                                
	if (win && fullscreen /* && !fsdone */ ) {
		XUnmapWindow(dpy,win);
	        Atom atom_noncomposited = XInternAtom(dpy, "_HILDON_NON_COMPOSITED_WINDOW", 0);
	        Atom atom_wmstate = XInternAtom(dpy, "_NET_WM_STATE", 0);
	        Atom atom_wmstate_fullscreen = XInternAtom(dpy, "_NET_WM_STATE_FULLSCREEN", 0);
		XSetWindowAttributes xattr;
		xattr.override_redirect = False;
		XChangeProperty (dpy,win,atom_zoom,XA_INTEGER,32,PropModeReplace,(unsigned char *) &val,1); // grab zoom keys
		XChangeProperty (dpy,win,atom_noncomposited,XA_INTEGER,32,PropModeReplace,(unsigned char *) &val,1); // make window not composited
		//XChangeWindowAttributes(dpy, win, CWOverrideRedirect, &xattr); // 
		XChangeProperty (dpy,win,atom_wmstate,XA_ATOM,32,PropModeReplace,(unsigned char *) &atom_wmstate_fullscreen,1); // mark as fullscreen = disable tskswitch button
		XMapWindow(dpy,win);
		//fsdone=1;
	}
	win = info.info.x11.wmwindow;
	if (win && !fullscreen /* && !wmdone */) {
		XUnmapWindow(dpy,win);
		XChangeProperty (dpy,win,atom_zoom,XA_INTEGER,32,PropModeReplace,(unsigned char *) &val,1);
		XMapWindow(dpy,win);
		//wmdone=1;
	}
	info.info.x11.unlock_func();
//	XSync(dpy,False);
}                                                                                                                                                    
}

Yep, indeed, you need to let it use python2.5.

Those 0.8.0 packages didn't have any changed functionality for keyboard stuff or whatever, I was merely rebasing our efforts on the latest code, so that we can more easily solve the problems.

We still need to find a good way to handle that MODE key.

Thanks for looking up that code for ScummVM (of course I know the project ;-), it definitely sounds interesting.

While you're at it, I'll first try to help you to get your environment OK. Please join us on IRC so we can help you directly. I'll keep monitoring this thread as well, of course.

As an alternative to IRC and this forum, you could use the openmsx-devel mailinglist. See https://sourceforge.net/mailarchive/forum.php?forum_name=openmsx-devel

When you think you have found solutions (as you wrote), can you send a diff to that mailinglist, so we can look at it and possibly include it in the main tree?

Yes, you can bind any Tcl command or procedure to a key event and multiple single commands with semicolon separated (as is normal Tcl syntax). E.g.:

bind F6 "foo; bar"