On Tue, Mar 01, 2011 at 06:25:59PM +0200, Hans de Goede wrote:
> This avoids us trying to restore the original resolution when we're fullscreen
> and an X error happens. As restoring fullscreen is a bad idea then as this
> involves making more X calls, which can get us stuck (in side an XLockDispla
Perhaps the client should fork and the parent process can watch for this
scenario and restore the resolution safely that way?
O
n Tue, 2011-03-01 at 18:25 +0200, Hans de Goede wrote:
> This avoids us trying to restore the original resolution when we're fullscreen
> and an X error happens. As rest
This avoids us trying to restore the original resolution when we're fullscreen
and an X error happens. As restoring fullscreen is a bad idea then as this
involves making more X calls, which can get us stuck (in side an XLockDisplay
call for example).
---
client/x11/platform.cpp |4 ++--
1 file
