I'm running OS 10.5.2, so I'll give pyglet 1.1 beta 1 a shot!
Thanks :O)
On Jun 4, 8:02 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote:
> On 6/5/08, Mike Lawrence <[EMAIL PROTECTED]> wrote:
>
>
>
> > I have an oldish monitor I'm using in my experiments that lists a
> > capacity to run at 1024x768 120Hz but anytime you pump it up that fast
> > it goes crazy and prints an 'invalid sync' message on screen. The next
> > lowest setting is 100Hz which is fine for me, but
> > pyglet.win.Window(fullscreen=T) automatically tries the 120Hz setting
> > and I'm having trouble figuring out how to override this behaviour and
> > get it to satisfy itself with 100Hz. Any suggestions?
>
> Which OS are you running? I recently fixed this bug on OS X (should
> be fixed in 1.1 beta 1 or SVN head). pyglet is supposed to keep the
> current resolution and rate when going fullscreen, so this is
> considered a bug.
>
> Alex.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
