Re: [Tuxmath-devel] Fullscreen issues

[B. L. <che...@gm...>]

Duh, of course. I was so busy playing around with xorg.conf, I didn't
even think to use the GUI control. Same issue:

Optimal resolution is 1280x800
X Error of failed request:  BadValue (integer parameter out of range
for operation)
  Major opcode of failed request:  134 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x55
  Serial number of failed request:  115
  Current serial number in output stream:  117

X seems to recover for me, though. If SDL had any way to query the
system rather than hardware, I'd have thought it would be
SDL_ListModes. It even passes SDL_VideoModeOK(); it's the actual
request that effects a crash and burn. I can't think of any way around
it other than using another API to find out what X is running at.
Perhaps we ought to test it on Windows and Mac to see if there are
similar problems.

Brendan

On Wed, Jun 18, 2008 at 5:56 PM, Tim Holy <ho...@wu...> wrote:
> Hi Brendan,
>
> On Wednesday 18 June 2008, you wrote:
>> Interesting. I'm not at all well-versed in X, but for what it's worth
>> I played around with settings and got an extended dual screen
>> up--1280x800 on the laptop and 1280x1024 on the external. When I ran
>> the game, SDL detected an "optimal" resolution of 2560x1024! It ran
>> fine, too, besides the fact that the 1280x224 bottom-left portion of
>> the screen wasn't being displayed at all :) The only other display I
>> could get to work was the external forced to 800x600, which also ran
>> the game fine.
>
> You probably have already done all this (or whatever similar steps are
> appropriate for your system) already, but just in case.... Here's what I did
> on my system (Kubuntu Hardy):
> 1. Go to "System Settings"
> 2. Choose Monitor & Display
> 3. Make the screen size smaller & click OK.
>
> It's possible that it's a driver-specific thing, and that my ATI card&driver
> will behave differently than another system.
>
>>
>> "3. If I'm running without the monitor, but running X & my desktop at
>> 1280x1024 anyway, then I was getting X lockups on fullscreen but not
>> --windowed."
>>
>> Hmmm. X thinks that 1280x1024 is where it's at, but SDL_ListModes gets
>> its information from hardware and knows better. So when SDL queries,
>> it bypasses X, but when it tries to use that mode, it does go through
>> X somehow. Out of curiosity, are you getting a hardware surface? Mine
>> is in software.
>
> Same here.
>
> --Tim
>