Mercurial > sdl-ios-xcode

view README.Watcom @ 4384:6800e2560310 SDL-1.2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 488eba319a25
children 8c72321542f6
line wrap: on
line source


Using SDL under Windows with the OpenWatcom compiler
====================================================

Prerequisites
-------------

I have done the port under Windows XP Home with SP2 installed. Windows
2000 should also be working. I'm not so sure about ancient Windows NT,
since only DirectX 3 is available there. Building should be possible,
but running the compiled applications will probalbly fail with
SDL_VIDEODRIVER=directx. The windib driver should work, though.

To compile and use the SDL with Open Watcom you will need the following:
- Open Watcom compiler. I used version 1.5. The environment variables
  PATH, WATCOM and INCLUDE need to be set appropriately - please consult
  the OpenWatcom documentation and instructions given during the
  installation of the compiler.
  My setup looks like this in owvars.bat:
    set WATCOM=C:\watcom
    set INCLUDE=%WATCOM%\h;%WATCOM%\h\nt
    set PATH=%PATH%;%WATCOM%\binnt;%WATCOM%\binw
- A fairly recent DirectX SDK. The original unmodified DX8 SDK works, as
  well as the minimal DirectX 7 SDK from the Allegro download site
  (<http://alleg.sourceforge.net/files/dx70_min.zip>).
- The SDL sources from Subversion
- The file Watcom-Win32.zip (now available in Subversion)


Building the Library
--------------------

1) In the SDL base directory extract the archive Watcom-Win32.zip. This
   creates a subdirectory named 'watcom'.
2) The makefile expects the environment variable DXDIR to be set to the
   base directory of a DirectX SDK. I have tried a stock DX8 SDK from
   Microsoft as well as the minimal DirectX 7 SDK from the Allegro
   download site.
   You can also edit the makefile directly and hard code your path to
   the SDK on your system.
   I have this in my setup:
     set DXDIR=D:\devel\DX8_SDK
3) Enter the watcom directory and run
     wmake sdl
4) All tests from the test directory are working and can be built by
   running
     wmake tests

Notes:

 The makefile offers some options to tweak the way the library is built.
 You have at your disposal the option to build a static (default)
 library, or a DLL (with tgt=dll). You can also choose whether to build
 a Release (default) or a Debug version (with build=debug) of the tests
 and library. Please consult the usage comment at the top of the
 makefile for usage instructions.

 If you specify a test target (i.e. 'wmake tests' for all tests, or
 selected targets like 'wmake testgl testvidinfo testoverlay2'), the
 tests are always freshly compiled and linked. This is done to
 minimise hassle when switching between library versions (static vs.
 DLL), because they require subtly different options.
 Also, the test executables are put directly into the test directory,
 so they can find their data files. The clean target of the makefile
 removes the test executables and the SDL.dll file from the test
 directory.

 To use the library in your own projects with Open Watcom, you can use
 the way the tests are built as base of your own build environment.

 The library can also be built with the stack calling convention of the
 compiler (-6s instead of -6r).


Test applications
-----------------

I've tried to make all tests work. The following table gives an overview
of the current status.

 Testname        Status
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
checkkeys       +
graywin         +
loopwave        +
testalpha       +
testbitmap      +
testdyngl       +
testerror       +
testfile        +
testgamma       +
testgl          +
testhread       +
testiconv       - (all failed)
testkeys        +
testlock        +
testoverlay     + (needs 'set SDL_VIDEODRIVER=directx')
testoverlay2    + (needs 'set SDL_VIDEODRIVER=directx')
testpalette     +
testplatform    +
testsem         +
testsprite      +
testtimer       +
testver         +
testvidinfo     +
testwin         ? (fading doesn't seem right)
testwm          +
torturethread   +
testcdrom       +
testjoystick    not tested
threadwin       +
testcursor      +


TODO
----

There is room for further improvement:
- Test joystick functionality.
- Investigate fading issue in 'testwin' test.
- Fix the UTF-8 support.
- Adapt the makefile/object file list to support more target systems
- Use "#pragma aux" syntax for the CPU info functions.


Questions and Comments
----------------------

Please direct any questions or comments to me:  <mailto:macpete@gmx.de>

   Happy Coding!

   Marc Peter