Currently the framebuffer console code waits for the user to switch
back to the current console when the user switches away. For 1.0.3,
I would like to send an APPACTIVE message and have the video surface
lock function fail when the user switches consoles.
This will allow the application to do something useful like pause
when the user switches away.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Currently the framebuffer console code waits for the user to switch
back to the current console when the user switches away. For 1.0.3,
I would like to send an APPACTIVE message and have the video surface
lock function fail when the user switches consoles.
This will allow the application to do something useful like pause
when the user switches away.
Maybe this could require “losing the surfaces”, like in DirectDraw? I
really hate the fact that Svgalib stops my game when the user switches
console for example, as I might be the server for a multiplayer game.
Currently the framebuffer console code waits for the user to switch
back to the current console when the user switches away. For 1.0.3,
I would like to send an APPACTIVE message and have the video surface
lock function fail when the user switches consoles.
This will allow the application to do something useful like pause
when the user switches away.
Maybe this could require “losing the surfaces”, like in DirectDraw? I
really hate the fact that Svgalib stops my game when the user switches
console for example, as I might be the server for a multiplayer game.
Hardware surfaces already have to be locked for drawing, and if the
lock fails, so does any blits to the surface. This is already handled.
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
