Mercurial > sdl-ios-xcode
view README.QNX @ 4139:568c9b3c0167 SDL-1.2
* Added configure option --enable-screensaver, to allow enabling the screensaver by default.
* Use XResetScreenSaver() instead of disabling screensaver entirely.
Full discussion summary from Erik on the SDL mailing list:
Current behaviour
=================
SDL changes the user's display power management settings without
permission from the user and without telling the user.
The interface that it uses to do so is DPMSDisable/DPMSEnable, which
should only ever be used by configuration utilities like KControl, never
by normal application programs, let alone by the libraries that they
use. Using an interface that is not at all intended for what SDL tries
to achieve means that it will not work as it should. Firstly, the power
management is completely disabled during the whole lifetime of the SDL
program, not only when it should be. Secondly, it makes SDL
non-reentrant, meaning that things will break when multiple SDL programs
are clients of the same X server simultaneously. Thirdly, no cleanup
mechanism ensures that the setting is restored if the client does not do
that (for example if it crashes).
In addition to that, this interface is broken on xorg,
[http://bugs.freedesktop.org/show_bug.cgi?id=13962], so what SDL tries
to do does not work at all on that implementation of the X Window
System. (The reason that the DPMSEnable works in KControl is that it
calls DPMSSetTimeout immediately after,
[http://websvn.kde.org/tags/KDE/3.5.9/kdebase/kcontrol/energy/energy.cpp?annotate=774532#l343]).
The problems that the current behaviour causes
==============================================
1. Information leak. When the user is away, someone might see what the
user has on the display when the user counts on the screensaver
preventing this. This does not even require physical access to the
workstation, it is enough to see it from a distance.
2. Draining battery. An SDL program that runs on a laptop will quickly
drain the battery while the user is away. The system will soon shut down
and require recharging before being usable again, while it should in
fact have consumed very little energy if the user's settings would have
been obeyed.
3. Wasting energy. Even if battery issues are not considered, energy as
such is wasted.
4. Display wear. The display may be worn out.
The problems that the current behaviour tries to solve
======================================================
1. Preventing screensaver while playing movies.
Many SDL applications are media players. They have reasons to prevent
screensavers from being activated while a movie is being played. When a
user clicks on the play button it can be interpreted as saying "play
this movie, but do not turn off the display while playing it, because I
will watch it even though I do not interact with the system".
2. Preventing screensaver when some input bypasses X.
Sometimes SDL uses input from another source than the X server, so
that the X server is bypassed. This obviously breaks the screensaver
handling. SDL tries to work around that.
3. Preventing screensaver when all input bypasses X.
There is something called Direct Graphics Access mode, where a
program takes control of both the display and the input devices from the
X server. This obviously means that the X server can not handle the
screensaver alone, since screensaver handling depends on input handling.
SDL does not do what it should to help the X server to handle the
screensaver. Nor does SDL take care of screeensaver handling itself. SDL
simply disables the screensaver completely.
How the problems should be solved
=================================
The correct way for an application program to prevent the screensaver
under X is to call XResetScreenSaver. This was recently discovered and
implemented by the mplayer developers,
[http://svn.mplayerhq.hu/mplayer?view=rev&revision=25637]. SDL needs to
wrap this in an API call (SDL_ResetScreenSaver) and implement it for the
other video targets (if they do not have a corresponding call, SDL
should do what it takes on that particular target, for example sending
fake key events).
1. When a movie is played, the player should reset the screensaver when
the animation is advanced to a new frame. The same applies to anything
similar, like slideshows.
2. When the X server is handling input, it must handle all input
(keyboards, mice, gamepads, ...). This is necessary, not only to be able
to handle the screensaver, but also so that it can send the events to
the correct (the currently active) client. If there is an input device
that the X server can not handle for some reason (such as lack of Plug
and Play capability), the program that handles the device as a
workaround must simulate what would happen if the X server would have
handled the device, by calling XResetScreenSaver when input is received
from the device.
3. When the X server is not handling the input, it depends on the
program that does to call XResetScreenSaver whenever an input event
occurs. Alternatively the program must handle the screensaver countdown
internally and call XActivateScreenSaver.
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Fri, 29 Feb 2008 13:55:44 +0000 |
| parents | 05c551e5bc64 |
| children | 0bc41e0361d3 |
line wrap: on
line source
README.QNX by Mike Gorchak <mike@malva.ua>, <lestat@i.com.ua> Last changed at 24 Apr 2004. ====================================================================== Table of Contents: 1. OpenGL. 2. Wheel and multi-button mouses. 3. CDROM handling issues. 4. Hardware video overlays. 5. Shared library building. 6. Some building issues. 7. Environment variables. ====================================================================== 1. OpenGL: OpenGL works well and is stable, but fullscreen mode has not been heavily tested yet. If you have QNX RtP version 6.1.0 or above you must download the Photon3D runtime from http://developers.qnx.com or install it from the public repository or from the public CD, available with QNX. OS versi- ons below 6.1.0 are not supported. When creating an OpenGL context, software renderer mode is artifi- cially selected (QSSL made acceleration only for Voodoo boards in fullscreen mode, sorry but I don't have this board to test OpenGL - maybe it works or maybe not :)). If you want acceleration - you can remove one line in the source code: find the file SDL_ph_image.c and remove the following OGLAttrib[OGLargc++]=PHOGL_ATTRIB_FORCE_SW; line in the ph_SetupOpenGLContext() function or change the argument to PHOGL_ATTRIB_FORCE_HW or PHOGL_ATTRIB_FAVOR_HW. ====================================================================== 2. Wheel and multi-button mouses: Photon emits keyboard events (key up and down) when the mouse wheel is moved. The key_scan field appears valid, and it contains zero. That is a basic method of detecting mouse wheel events under Photon. It looks like a hack, but it works for me :) on various PC configura- tions. I've tested it on: 1. Genius Optical NetScroll/+ PS/2 (1 wheel) 2. A4Tech Optical GreatEye WheelMouse PS/2, model: WOP-35. (2 wheels + 2 additional buttons). The wheel for vertical scrolling works as usual, but the second wheel for horizontal scrolling emits two se- quential events up or down, so it can provide faster scrolling than the first wheel. Additional buttons don't emit any events, but it looks like they're handled by photon in an unusual way - like click to front, but works not with any window, looks like a fun bug-o-fe- ature :). ====================================================================== 3. CDROM handling issues: Access to CDROM can only be provided with 'root' privileges. I can't do anything about that, /dev/cd0 has brw------- permissions and root:root rights. ====================================================================== 4. Hardware video overlays: Overlays can flicker during window movement, resizing, etc. It happens because the photon driver updates the real window contents be- hind the overlay, then draws the temporary chroma key color over the window contents. It can be done without using the chroma key but that causes the overlay to always be on top. So flickering during window movement is preferred instead. Double buffering code is temporarily disabled in the photon driver code, because on my GF2-MX it can accidentally cause a buffer switch, which causes the old frame to show. S3 Savage4 has the same problem, but ATI Rage 128 doesn't. I think it can be fixed later. Current code works very well, so maybe double buffering is not needed right now. Something strange happens when you try to move the window with the overlay beyond the left border of the screen. The overlay tries to stay at position x=0, but when attempting to move it a bit more it jumps to position x=-60 (on GF2-MX, on ATI Rage128 this value a bit smaller). It's really strange, looks like the overlay doesn't like negative coordinates. ======================================================================= 5. Shared library building: A shared library can be built, but before running the autogen.sh script you must manually delete the libtool.m4 stuff from the acinclu- de.m4 file (it comes after the ESD detection code up to the end of the file), because the libtool stuff in the acinclude.m4 file was very old in SDL distribution before the version 1.2.7 and doesn't knew anything about QNX. SDL 1.2.7 distribution contains the new libtool.m4 script, but anyway it is broken :), Just remove it, then run "libtoolize --force --copy", delete the file aclocal.m4 if it is exists and after that run the autogen.sh script. SDL 1.2.8 contains fixed libtool.m4, ltmain.sh and config.sub files, so you can just run the autogen.sh script. ====================================================================== 6. Some building issues: Feel free to not use the --disable-shared configure option if you' ve read the above comment about 'Shared library building'. Otherwise this option is strongly recommended, as without it the sdl-config script will be broken. Run the configure script without x11 support, e.g.: a) for OpenGL support: ./configure --prefix=/usr \ --disable-video-x11 \ --disable-shared b) without OpenGL support: ./configure --prefix=/usr \ --disable-video-x11 \ --disable-shared \ --disable-video-opengl And of course dont forget to specify --disable-debug, which is on by default, to disable debug and enable the expensive optimizations. In the test directory also run the ./configure script without x11 support, e.g.: ./configure --with-sdl-prefix=/usr \ --with-sdl-exec-prefix=/usr \ --prefix=/usr --without-x ====================================================================== 7. Environment variables: Please note that the photon driver is sensible to the following environmental variables: * SDL_PHOTON_FULLSCREEN_REFRESH - this environment variable controls the refresh rate in all fullscreen modes. Be carefull !!! Photon drivers usually do not checking the maximum refresh rate, which video adapter or monitor supports. * SDL_VIDEO_WINDOW_POS - can be set in the "X,Y" format. If X and Y coordinates are bigger than the current desktop resolution, then win- dow positioning across virtual consoles is activated. If X and Y are smaller than the desktop resolution then window positioning in the current console is activated. The word "center" can be used instead of coordinates, it produces the same behavior as SDL_VIDEO_CENTERED environmental variable. * SDL_VIDEO_CENTERED - if this environmental variable exists then the window centering is perfomed in the current virtual console. Notes: The SDL_VIDEO_CENTERED enviromental variable has greater pri- ority than the SDL_VIDEO_WINDOW_POS in case if both variables are sup- plied to the application.