Mercurial > sdl-ios-xcode

view README.Qtopia @ 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 2c5d4c22a2ac
children
line wrap: on
line source


==============================================================================
Using the Simple DirectMedia Layer with Qtopia/OPIE
==============================================================================

==============================================================================
I.  Setting up the Qtopia development environment.

  This document will not explain how to setup the Qtopia development
  environment. That is outside the scope of the document. You can read
  more on this subject in this excellent howto:

	http://www.zauruszone.com/howtos/linux_compiler_setup_howto.html

==============================================================================
II.  Building the Simple DirectMedia Layer libraries using the arm
     cross-compiler

  This is somewhat tricky since the name of the compiler binaries
  differ from the standard. Also you should disable features not
  needed. The command below works for me. Note that it's all one
  line. You can also set the NM, LD etc environment variables
  separately.

	NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ RANLIB=arm-linux-ranlib AR=arm-linux-ar ./configure --enable-video-qtopia --disable-video-dummy --disable-video-fbcon  --disable-video-dga --disable-arts --disable-esd --disable-alsa --disable-cdrom --disable-video-x11 --disable-nasm --prefix=/opt/Qtopia/sharp/ arm-unknown-linux-gnu

  One thing to note is that the above configure will include joystick
  support, even though you can't have joysticks on the Zaurus. The
  reason for this is to avoid link / compile / runtime errors with
  applications that have joystick support.

==============================================================================
III.  Building the Simple DirectMedia Layer test programs:

  After installing, making sure the correct sdl-config is in your
  path, run configure like this:

	NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ AR=arm-linux-ar ./configure arm-unknown-linux-gnu

==============================================================================
IV.  Application porting notes

  One thing I have noticed is that applications sometimes don't exit
  correctly. Their icon remains in the taskbar and they tend to
  relaunch themselves automatically. I believe this problem doesn't
  occur if you exit your application using the exit() method. However,
  if you end main() with 'return 0;' or so, this seems to happen.

  Also note that when running in landscape mode - i.e requesting a
  window that is HEIGHT pixels wide and WIDTH pixels high, where WIDTH
  and HEIGHT normally is 240 and 320 - the image is blitted so that
  the hardware buttons are on the left side of the display. This might
  not always be desirable but such is the code today.


==============================================================================
V.  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
  
==============================================================================
VI.  What is supported:

Keyboard (Sharp Zaurus)
Hardware buttons
Stylus input (mouse)
Video. Allows fullscreen both in portrait mode (up to WIDTHxHEIGHT
size window) and in landscape mode (up to HEIGHTxWIDTH). 

All other SDL functionality works like a normal Linux system (threads,
audio etc).

-- 
David Hedbor <david@hedbor.org>
http://david.hedbor.org/ 	http://eongames.com/