Closed GoogleCodeExporter closed 9 years ago
a workaround is to set window.set_fullscreen(True) directly after creating it.
Original comment by gar...@spacetaken.net
on 29 Aug 2008 at 11:57
Cannot reproduce. Can you download the source release (.zip or .tar.gz) and run
python tests/test.py window-fullscreen
Follow the prompts, and attach the pyglet.*.log file that's created. Thanks.
Original comment by Alex.Hol...@gmail.com
on 30 Aug 2008 at 12:52
I found a very similar problem which I was able to fix in trunk. If you're
able to,
can you check that the problem still exists in r2237? (Note that generally
trunk is
not usable at the moment, but it can run this example).
Original comment by Alex.Hol...@gmail.com
on 30 Aug 2008 at 1:07
with source release:
INFO:root:Beginning test at Sat Aug 30 11:08:09 2008
INFO:root:Capabilities are: GENERIC, WIN
INFO:root:sys.platform = win32
INFO:root:Reading test plan from tests\plan.txt
INFO:root:Testing window.WINDOW_INITIAL_FULLSCREEN.
INFO:root:Begin unit tests for window.WINDOW_INITIAL_FULLSCREEN
INFO:root:1 tests run
INFO:root:User marked pass for window.WINDOW_INITIAL_FULLSCREEN
INFO:root:Testing window.WINDOW_SET_FULLSCREEN.
seems to work
Original comment by gar...@spacetaken.net
on 30 Aug 2008 at 10:09
the problem appears to be fixed in trunk
Original comment by gar...@spacetaken.net
on 30 Aug 2008 at 10:13
Thanks, closing issue (will not backport to 1.1-maintenance, as changes would be
extensive).
Original comment by Alex.Hol...@gmail.com
on 30 Aug 2008 at 10:39
Original issue reported on code.google.com by
gar...@spacetaken.net
on 29 Aug 2008 at 11:42