Mercurial > sdl-ios-xcode

view README.Epoc @ 563:04dcaf3da918

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Massive Quartz input enhancements from Darrell Walisser. His email: Enclosed is a patch that addresses the following: --Various minor cleanups. Removed dead/obsolete code, made some style cleanups --Mouse Events Now keep track of what button(s) were pressed so we know when to send the mouse up event. This fixes the case where the mouse is dragged outside of the game window and released (in which case we want to send the mouse up event even though the mouse is outside the game window). --Input Grabbing Here is my take on the grabbing situation, which is the basis for the new implementation. There are 3 grab states, ungrabbed (UG), visible (VG), and invisible (IG). Both VG and IG keep the mouse constrained to the window and produce relative motion events. In VG the cursor is visible (duh), in IG it is not. In VG, absolute motion events also work. There are 6 actions that can affect grabbing: 1. Set Fullscreen/Window (F/W). In fullscreen, a visible grab should do nothing. However, a fullscreen visible grab can be treated just like a windowed visible grab, which is what I have done to help simplify things. 2. Cursor hide/show (H/S). If the cursor is hidden when grabbing, the grab is an invisible grab. If the cursor is visible, the grab should just constrain the mouse to the window. 3. Input grab/ungrab(G/U). If grabbed, the cursor should be confined to the window as should the keyboard input. On Mac OS X, the keyboard input is implicitly grabbed by confining the cursor, except for command-tab which can switch away from the application. Should the window come to the foreground if the application is deactivated and grab input is called? This isn't necessary in this implementation because the grab state will be asserted upon activation. Using my notation, these are all the cases that need to be handled (state + action = new state). UG+U = UG UG+G = VG or IG, if cursor is visible or not UG+H = UG UG+S = UG VG+U = UG VG+G = VG VG+H = IG VG+S = VG IG+U = UG IG+G = IG IG+H = IG IG+S = VG The cases that result in the same state can be ignored in the code, which cuts it down to just 5 cases. Another issue is what happens when the app loses/gains input focus from deactivate/activate or iconify/deiconify. I think that if input focus is ever lost (outside of SDL's control), the grab state should be suspended and the cursor should become visible and active again. When regained, the cursor should reappear in its original location and/or grab state. This way, when reactivating the cursor is still in the same position as before so apps shouldn't get confused when the next motion event comes in. This is what I've done in this patch.
author Ryan C. Gordon <icculus@icculus.org>
date Fri, 27 Dec 2002 20:52:41 +0000
parents 74a8f672f2f8
children
line wrap: on
line source


==============================================================================
Using the Simple DirectMedia Layer with EPOC/SymbianOS 6.0
==============================================================================

==============================================================================
I.  Building the Simple DirectMedia Layer libraries:

  You can get Symbian SDK from: 
    http://www.symbian.com.
 
  First create "Epoc" directory under SDL main directory and unpack 
  EpocBuildFiles.zip in it.
   
  To build the librarys goto "epoc" directory and type:
    bldmake bldfiles
    abld makefile vc6 (for creating Microsoft Visual C++ makefiles)
    abld build wins udeb (building for wins emulator)
    abld build armi urel (building for real device)

==============================================================================
II. Building the Simple DirectMedia Layer programs:

  Building SDL test programs is easy once you have built the libraries:
    abld test build wins udeb
    abld test build armi urel

  Supported real screen resolutions
    320 x 200 x  8 bit
    320 x 200 x 12 bit
    640 x 200 x  8 bit
    640 x 200 x 12 bit
  Supported "emulated" screen resolutions 
    640 x 400 x  8 bit
    640 x 400 x 12 bit
    640 x 480 x  8 bit
    640 x 480 x 12 bit
  "Emulated" resolutions are implemented by by shrinking the screen vertically 
  i.e. only every second scanline is drawn. This is mainly ment to be used for 
  testing quick ports of programs. Using faked resolutions is a waste of memory 
  and cpu power!

==============================================================================
III. Running test programs

  Copy executable to the device and run it from the File manager.   The Esc 
  key quits demo programs. In Crystal, Exe programs do not appear in task list 
  nor in Extras :-(. Test programs are tested in Nokia 9210 Communicator.

  Special keys used in SDL:
    The Caps lock key enables or disables the virtual cursor. 
    Function keys are mapped as follows: 
    F1=chr+q, F2=chr+w,..., F8=chr+i, 
    F9=chr+a,..., F12=chr+d.

==============================================================================
IV.  Enjoy! :)

  If you have a project you'd like me to know about, or want to ask questions,
  go ahead and join the SDL developer's mailing list by sending e-mail to:

	sdl-request@libsdl.org

  and put "subscribe" into the subject of the message. Or alternatively you
  can use the web interface:

	http://www.libsdl.org/mailman/listinfo/sdl

  You can find more info about Epoc version of SDL from Hannu Viitala's 
  homepage
    http://www.mbnet.fi/~haviital
  
==============================================================================