Closed GoogleCodeExporter closed 9 years ago
This behaviour of screen selection is expected: configs are not specific to a
screen
(though a screen may support only a certain subset of configs). If this were
not the
case, a window created on one screen would not be able to be moved onto the
other.
However, the location of the window in the first example looks incorrect (it
should
be on screen 0 at 0,0).
Original comment by Alex.Hol...@gmail.com
on 18 Aug 2008 at 3:54
It's definitely creating the window on the second screen (but with the
dimensions of
the default screen), so there's definitely a bug there - it should be using one
or
the other of the screens.
Is the expected behaviour if you only pass a config (or context I guess) to
create
the window on the default screen? If so, it looks like there's a documentation
bug:
http://pyglet.org/doc/api/pyglet.window.Window-class.html#__init__
"The display, screen, config and context parameters form a hierarchy of
control:
there is no need to specify more than one of these. For example, if you specify
screen the display will be inferred, and a default config and context will be
created."
Original comment by timothy....@gmail.com
on 18 Aug 2008 at 4:05
Thanks, documentation for Window clarified in r2212 (trunk) and r2213
(1.1-maintenance).
Original comment by Alex.Hol...@gmail.com
on 24 Aug 2008 at 4:34
Sorry, your initial report was correct; configs do keep a reference to their
screen.
I've reverted the documentation changes in r2212/3 and fixed the specific case of
initializing Window with a config and no screen in r2214/5.
Original comment by Alex.Hol...@gmail.com
on 24 Aug 2008 at 4:54
Original issue reported on code.google.com by
timothy....@gmail.com
on 18 Aug 2008 at 3:22