Mercurial > sdl-ios-xcode
view README.NanoX @ 4384:6800e2560310 SDL-1.2
Fixed bugs #882 and 865, re-opening bug #634
Ronald Lamprecht to SDL
Hi,
Sam Lantinga wrote:
The problem with that fix is that it breaks IME events again. Maybe
we can handle keyboard events differently to prevent this issue?
Spending an hour reading MSDN, analysing SDL and another hour testing the reality on XP I am really wondering how patch r4990 could have ever worked in any situation. It's main effect is to break the unicode translation and causing spurious activation events!
Why does TranslateMessage(&msg) nothing useful? Simply because it does not affect "msg" at all! All keyboard events are dispatched without the slightest change (see MSDN). TranslateMessage() just appends additional WM_CHAR, WM_DEADCHAR, WM_SYSCHAR, WM_SYSDEADCHAR event messages to the queue. But I could not find any SDL event handling routine that catches these events and transforms them to proper SDL keyevents while eliminating the corresponding WM_KEYDOWN, etc. events. Thus any IME input like the '@' generated by "Alt + 6(Numpad) + 4(Numpad)" is simply lost.
But the situation is even worse! Up to r4990 the TranslateKey()/ToUnicode() calls did evaluate dead keys and did deliver proper key events for subsequent key strokes like '´' + 'e' resulting in 'é'. ToUnicode() needs proper key state informations to be able to handle these substitutions. But unfortunatly TranslateMessage() needs the same state information and eats it up while generating the WM_CHAR messages :-( Thus the current 1.2.14 breakes the partial IME support of previous releases, too.
The key state race condition between ToUnicode() and TranslateMessage() requires to avoid any ToUnicode() usage for receiving proper WM_CHAR, etc. messages generated by TranslateMessage(). (Yes - the '@' and 'é' appear as WM_CHAR messages when unicode is switched off).
The spurious SDL activation events are *not* caused by additional WM_ACTIVATE Windows messages! Besides DIB_HandleMessage() SDL_PrivateAppActive() is called by another source which I am not yet aware of - any hints?
Thus I do strongly recommend the deletion of the TranslateMessage(&msg) call as a quick fix.
A proper support of unicode and IME requires a clean SDL keyboard input concept first. Which SDL keyboards events should be transmitted to the app when the user presses '´' + 'e' ? Within the current unicode handling the first key stroke is hidden. Even though ToUnicode() delivers the proper key SDL does ignore it in TranslateKey(). Just the composed key event is transmitted to the app. That is what you expect for text input, but the app can no longer use keys like '^' as a key button because it will never receive a key event for it!
With a given concept it seems to be necessary to regenerate SDL key events out of the WM_CHAR, etc. events and to drop all related direct WM_KEYDOWN, etc. events while the remaining basic WM_KEYDOWN, etc. events would still have to result in SDL key events.
Anyway the source of the spurious WM_ACTIVATE should be located to avoid future trouble.
Greets,
Ronald
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Tue, 17 Nov 2009 04:59:13 +0000 |
parents | 26dafefeebb2 |
children |
line wrap: on
line source
================================================================= Patch version 0.9 of SDL(Simple DirectMedia Layer) for Nano-X API ================================================================= Authors: Hsieh-Fu Tsai, clare@setabox.com Greg Haerr, greg@censoft.com This patch is against SDL version 1.2.4. It enhances previous patch 0.8 by providing direct framebuffer access as well as dynamic hardware pixel type support, not requiring a compile-time option setting for different framebuffer modes. Tested against Microwindows version 0.89pre9. Older Microwindows versions =========================== If running on a version older than Microwindows 0.89pre9, the following items might need to be patched in Microwindows. 1. Patch src/nanox/client.c::GrClose() It fixes the client side GrClose(). In the original version, GrOpen() can only be called once. When the GrOpen() is called at the second time, the program will terminate. In order to prevent this situation, we need to insert "nxSocket = -1" after "close(nxSocket)" in GrClose(). If you do not have this problem, you may skip this step. 2. Patch src/nanox/clientfb.c to return absolute x,y coordinates when using GrGetWindowFBInfo(). Copy the version 0.89pre9 of src/nanox/clientfb.c to your system, or configure using --disable-nanox-direct-fb. ============= Quick Install ============= 1. ./configure --disable-video-x11 --disable-video-fbcon \ --enable-video-nanox \ --with-nanox-pixel-type=[rgb/0888/888/565/555/332/pal] 2. make clean 3. make 4. make install (as root) ============ Nitty-gritty ============ --enable-nanox-direct-fb Use direct framebuffer access --enable-nanox-debug Show debug messages --enable-nanox-share-memory Use shared-memory to speed up When running multi-threaded applications using SDL, such as SMPEG, set THREADSAFE=Y in Microwindows' config file, to enable GrXXX() system call critical section support. ============================================= Some programs can be used to test this patch. ============================================= 1. http://www.cs.berkeley.edu/~weimer/atris (a tetris-like game) 2. http://www.libsdl.org/projects/newvox/ 3. http://www.libsdl.org/projects/xflame/ 4. http://www.libsdl.org/projects/optimum/ 5. http://www.gnugeneration.com/software/loop/ 6: http://www.lokigames.com/development/smpeg.php3 (SMPEG version 0.4.4) ========= Todo List ========= 1. Create hardware surface 2. Create YUVOverlay on hardware 3. Use OpenGL 4. Gamma correction 5. Hide/Change mouse pointer 6. Better window movement control with direct fb access 7. Palette handling in 8bpp could be improved ===================== Supporting Institutes ===================== Many thanks to go to Setabox Co., Ltd. and CML (Communication and Multimedia Laboratory, http://www.cmlab.csie.ntu.edu.tw/) in the Department of Computer Science and Information Engineering of National Taiwan University for supporting this porting project. Century Embedded Technologies (http://embedded.censoft.com) for this patch. =================== Contact Information =================== Welcome to give me any suggestion and to report bugs. My e-mail address : clare@setabox.com or niky@cmlab.csie.ntu.edu.tw or greg@censoft.com