forums.ps2dev.org

[Arwin]

I successfully compiled p_sprint into the mouse and keyboard driver for microwindows.

Although I haven't got a (charged - left my charger somewhere :s) PSP handy, darkshadow88 has helped me to test this and get it to work.

I don't have svn write access but will post here when it works fully (nearly there) for those who are interested.

Is anyone even interested? :D Or is the whole Microwindows thing a dead-end anyway?

[Arwin]

Ok, here's the result of our work so far: a 1.0 Eboot of the Microwindows MDEMO with p-sprint enabled.

Right now it only simulates the ASCII values of keys you press, not scancodes or modifiers (but in p-sprint you can still type CTRL-X and stuff like that, just software in Microwindows that looks at modifier status solely can't do anything with it), so F1 or Left won't work yet. We couldn't figure out yet how Microwindows handles the scancodes or the modifiers properly, and make them compatible with p-sprint, so that'll come later.

Here's the download:
http://www.niwra.nl/psp/p-sprint-c/MDEMOP_SP.rar

The download includes the three files you need to update in the microwindows/src/drivers folder, and the p-sprint files you need to copy there. P-sprint has also been edited, as it reset the controller reads during its own init, which it shouldn't be doing when it reads alongside with the mouse driver or other drivers - in other words, when using p_spReadKeyEx. So that was fixed in this version (which will be released as 0.63a)

[Arwin]

I see that nano-x has a pretty different set of scancodes. So I'll have to add a mapping option to fix this to p-sprint to get the control keys to work. Will do that tomorrow

[Arwin]

I tested a simple switch conversion and that seems to work. But I'll add something to p-sprint itself, either a mode to be able to change the keycode mappings or maybe even a microwindows specific mode, to optimise speed.

Unfortunately Microwindows seems to be rough in some areas. The edit and medit controls (single and multiline textboxes) don't seem to work at all with variable width fonts, and from the looks of it, they never have either, as when asking the font width and height they always simply pas an "X", never the actual character(s) they were looking at.

This causes the cursor to be completely out of step. But the text itself is printed ok (well, almost, except the e is clipped slightly) so somewhere something must work. I'm afraid that it will need some serious work; I couldn't find out yesterday what the problem was (but then I'm a n00b).