1README.QNX by Mike Gorchak <mike@malva.ua>, <lestat@i.com.ua> 2Last changed at 24 Apr 2004. 3 4====================================================================== 5Table of Contents: 6 71. OpenGL. 82. Wheel and multi-button mouses. 93. CDROM handling issues. 104. Hardware video overlays. 115. Shared library building. 126. Some building issues. 137. Environment variables. 14 15====================================================================== 161. OpenGL: 17 18 OpenGL works well and is stable, but fullscreen mode has not been 19heavily tested yet. 20 If you have QNX RtP version 6.1.0 or above you must download the 21Photon3D runtime from http://developers.qnx.com or install it from the 22public repository or from the public CD, available with QNX. OS versi- 23ons below 6.1.0 are not supported. 24 When creating an OpenGL context, software renderer mode is artifi- 25cially selected (QSSL made acceleration only for Voodoo boards in 26fullscreen mode, sorry but I don't have this board to test OpenGL - 27maybe it works or maybe not :)). If you want acceleration - you can 28remove one line in the source code: find the file SDL_ph_image.c and 29remove the following 30 31 OGLAttrib[OGLargc++]=PHOGL_ATTRIB_FORCE_SW; 32 33line in the ph_SetupOpenGLContext() function or change the argument to 34PHOGL_ATTRIB_FORCE_HW or PHOGL_ATTRIB_FAVOR_HW. 35 36====================================================================== 372. Wheel and multi-button mouses: 38 39 Photon emits keyboard events (key up and down) when the mouse 40wheel is moved. The key_scan field appears valid, and it contains zero. 41That is a basic method of detecting mouse wheel events under Photon. 42It looks like a hack, but it works for me :) on various PC configura- 43tions. 44 45I've tested it on: 46 471. Genius Optical NetScroll/+ PS/2 (1 wheel) 482. A4Tech Optical GreatEye WheelMouse PS/2, model: WOP-35. (2 wheels 49 + 2 additional buttons). The wheel for vertical scrolling works as 50 usual, but the second wheel for horizontal scrolling emits two se- 51 quential events up or down, so it can provide faster scrolling than 52 the first wheel. Additional buttons don't emit any events, but it 53 looks like they're handled by photon in an unusual way - like click 54 to front, but works not with any window, looks like a fun bug-o-fe- 55 ature :). 56 57====================================================================== 583. CDROM handling issues: 59 60 Access to CDROM can only be provided with 'root' privileges. I 61can't do anything about that, /dev/cd0 has brw------- permissions and 62root:root rights. 63 64====================================================================== 654. Hardware video overlays: 66 67 Overlays can flicker during window movement, resizing, etc. It 68happens because the photon driver updates the real window contents be- 69hind the overlay, then draws the temporary chroma key color over the 70window contents. It can be done without using the chroma key but that 71causes the overlay to always be on top. So flickering during window 72movement is preferred instead. 73 Double buffering code is temporarily disabled in the photon driver 74code, because on my GF2-MX it can accidentally cause a buffer switch, 75which causes the old frame to show. S3 Savage4 has the same problem, 76but ATI Rage 128 doesn't. I think it can be fixed later. Current code 77works very well, so maybe double buffering is not needed right now. 78 Something strange happens when you try to move the window with the 79overlay beyond the left border of the screen. The overlay tries to 80stay at position x=0, but when attempting to move it a bit more it 81jumps to position x=-60 (on GF2-MX, on ATI Rage128 this value a bit 82smaller). It's really strange, looks like the overlay doesn't like 83negative coordinates. 84 85======================================================================= 865. Shared library building: 87 88 A shared library can be built, but before running the autogen.sh 89script you must manually delete the libtool.m4 stuff from the acinclu- 90de.m4 file (it comes after the ESD detection code up to the end of the 91file), because the libtool stuff in the acinclude.m4 file was very old 92in SDL distribution before the version 1.2.7 and doesn't knew anything 93about QNX. SDL 1.2.7 distribution contains the new libtool.m4 script, 94but anyway it is broken :), Just remove it, then run "libtoolize 95--force --copy", delete the file aclocal.m4 if it is exists and after 96that run the autogen.sh script. SDL 1.2.8 contains fixed libtool.m4, 97ltmain.sh and config.sub files, so you can just run the autogen.sh 98script. 99 100====================================================================== 1016. Some building issues: 102 103 Feel free to not use the --disable-shared configure option if you' 104ve read the above comment about 'Shared library building'. Otherwise 105this option is strongly recommended, as without it the sdl-config 106script will be broken. 107 108 Run the configure script without x11 support, e.g.: 109 110 a) for OpenGL support: 111 ./configure --prefix=/usr \ 112 --disable-video-x11 \ 113 --disable-shared 114 115 b) without OpenGL support: 116 ./configure --prefix=/usr \ 117 --disable-video-x11 \ 118 --disable-shared \ 119 --disable-video-opengl 120 121 And of course dont forget to specify --disable-debug, which is on 122by default, to disable debug and enable the expensive optimizations. 123 124 In the test directory also run the ./configure script without 125x11 support, e.g.: 126 127 ./configure --with-sdl-prefix=/usr \ 128 --with-sdl-exec-prefix=/usr \ 129 --prefix=/usr --without-x 130 131====================================================================== 1327. Environment variables: 133 134 Please note that the photon driver is sensible to the following 135environmental variables: 136 137 * SDL_PHOTON_FULLSCREEN_REFRESH - this environment variable controls 138the refresh rate in all fullscreen modes. Be carefull !!! Photon 139drivers usually do not checking the maximum refresh rate, which video 140adapter or monitor supports. 141 142 * SDL_VIDEO_WINDOW_POS - can be set in the "X,Y" format. If X and Y 143coordinates are bigger than the current desktop resolution, then win- 144dow positioning across virtual consoles is activated. If X and Y are 145smaller than the desktop resolution then window positioning in the 146current console is activated. The word "center" can be used instead of 147coordinates, it produces the same behavior as SDL_VIDEO_CENTERED 148environmental variable. 149 150 * SDL_VIDEO_CENTERED - if this environmental variable exists then the 151window centering is perfomed in the current virtual console. 152 153Notes: The SDL_VIDEO_CENTERED enviromental variable has greater pri- 154ority than the SDL_VIDEO_WINDOW_POS in case if both variables are sup- 155plied to the application. 156