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

I'm preparing new packages now....

I'd first like to see if simple openMSX settings can already improve the experience to some extent. Did you have a chance to try out the suggestions I did, so we can make an optimal default configuration for N900?

About the stuff you mentioned: I'm not sure those go well with SDL... we do not use X directly anywhere in our code. So, I'm not sure this is (easily) feasible.

Better, now keyboard sort-of works. The main problem is that many keys on the N900 keyboard are accessed through alt+keypress which openmsx doesn't recognize -- unfortunately that includes characters like underscore and all numbers so it makes adjusting settings in the console a little bit difficult. It seems the "kbd_trace_key_presses" setting is not read from settings.xml and since I cannot enable it from the console because I cannot enter an underscore I'm out of luck I'll try to add some alt+key bindings manually to the settings.xml but I'm not sure if I can use that to replace "missing" keys like bind alt+g "_".

Quickly judging I'd say running with scale_factor 1 gives full framerate but on the other hand the graphics get quite small Running fullscreen with resampler set to fast and default scale_factor also plays Metal Gear 2 at almost full framerate which makes me believe full framerate could be achieved if the display composition was disabled. I understand if you do not want to introduce platform specific code to openmsx but the trick I linked to should (not a promise) be usable with SDL as well since you can acquire a handle to the X Window SDL is using via SDL_GetWMInfo.

The keys actually work in the emulated MSX, i.e. when I press alt+Q on the N900, I get a '1' in the MSX BASIC as it should. It's just the console that doesn't read input from these "shifted" keys.

I'll experiment with the other settings you mentioned, unfortunately I have to do this by manually editing the settings.xml in the XTerminal because I cannot enter any numbers either in the console :/

I'd be glad to help but I only have Macs and the Maemo devenv only works on Linux. I know I could set up a virtual machine and work from there, I'll look into it.

According to the key trace log, when the console is open I get no key press events with the mode key, only release events. On the other hand, when console is closed, both press and release events are reported.

An excerpt from the trace log below. I have mapped CTRL+Q to "toggle console" command. What I do is I'm first in MSX BASIC, enter numbers 1,2,3 by pressing MODE + Q, W, E respectively, open the console and try to do the same.

Key pressed, unicode: 0x0000, keyCode: 0x00139, keyName: MODE
Key pressed, unicode: 0x0031, keyCode: 0x200071, keyName: Q+MODE
Key released, unicode: 0x0000, keyCode: 0x600071, keyName: Q+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x00139, keyName: MODE
Key pressed, unicode: 0x0032, keyCode: 0x200077, keyName: W+MODE
Key released, unicode: 0x0000, keyCode: 0x600077, keyName: W+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x00139, keyName: MODE
Key pressed, unicode: 0x0033, keyCode: 0x200065, keyName: E+MODE
Key released, unicode: 0x0000, keyCode: 0x600065, keyName: E+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x00132, keyName: LCTRL
Key released, unicode: 0x0000, keyCode: 0x440071, keyName: Q+CTRL,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400132, keyName: LCTRL,RELEASE
Key released, unicode: 0x0000, keyCode: 0x600071, keyName: Q+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x600077, keyName: W+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x600065, keyName: E+MODE,RELEASE
Key released, unicode: 0x0000, keyCode: 0x400139, keyName: MODE,RELEASE

OK, Wouter had some ideas:
<Quibus> i.e. why he only gets release events in the console and not when typing in the MSX
<wouter_> that's beause of the location of the logging .. logging in done in the MSX keyboard code, and when the console is up, keydown events are not send to the msx anymore (in 0.7.2, though this recently changed, now not even keyup events are passed to the msx)
<wouter_> the console only processes 'normal' keys (CommandConsole::normalKey()) when no modifier or only SHIFT is pressed
<wouter_> maybe, in the console code, we shouldn't look at the modifier state at all, but only to the unicode field?

And he gave me a patch for that. Will build a new openMSX package for that (replacing the old one).

If you have a dev env yourself now, this is the patch against SVN HEAD (won't apply to 0.7.2):

diff --git a/src/console/CommandConsole.cc b/src/console/CommandConsole.cc
index 1ff7bcc..ad96868 100644
--- a/src/console/CommandConsole.cc
+++ b/src/console/CommandConsole.cc
@@ -199,7 +199,12 @@ bool CommandConsole::handleEvent(const KeyEvent& keyEvent)
 			if (down) clearCommand();
 			break;
 		default:
-			used = false;
+			if (chr) {
+				if (down) normalKey(chr);
+			} else {
+				used = false;
+			}
+			break;
 		}
 		break;
 	case Keys::KM_SHIFT:
@@ -275,7 +280,12 @@ bool CommandConsole::handleEvent(const KeyEvent& keyEvent)
 		}
 		break;
 	default:
-		used = false;
+		if (chr) {
+			if (down) normalKey(chr);
+		} else {
+			used = false;
+		}
+		break;
 	}
 	if ((key == Keys::K_LSHIFT) || (key == Keys::K_RSHIFT) ||
 	    (key == Keys::K_LCTRL)  || (key == Keys::K_RCTRL)  ||