On Thu, Mar 22, 2012 at 4:24 PM, Hello3171 <[email protected]> wrote:
> Well I finally got round to doing it. I updated with the patch in issue > 510 and the astraea example works at least. How come the patch is not > incorporated, lack of testing? > > Although I did get this error when attempting to change into fullscreen > mode: > > Traceback (most recent call last): > File "_ctypes/callbacks.c", line 313, in 'calling callback function' > File "C:\Python27\lib\site-packages\pyglet\window\win32\__init__.py", > line 612 > , in _wnd_proc > result = event_handler(msg, wParam, lParam) > File "C:\Python27\lib\site-packages\pyglet\window\win32\__init__.py", > line 693 > , in _event_key > self.dispatch_event(ev, symbol, modifiers) > File "C:\Python27\lib\site-packages\pyglet\window\__init__.py", line > 1151, in > dispatch_event > if EventDispatcher.dispatch_event(self, *args) != False: > File "C:\Python27\lib\site-packages\pyglet\event.py", line 355, in > dispatch_ev > ent > if handler(*args): > File "astraea.py", line 351, in on_key_release > self.items[self.selected_index].on_key_release(symbol, modifiers) > File "astraea.py", line 423, in on_key_release > self.toggle_func(self.value) > File "astraea.py", line 481, in set_enable_fullscreen > win.set_fullscreen(value, width=ARENA_WIDTH, height=ARENA_HEIGHT) > File "C:\Python27\lib\site-packages\pyglet\window\__init__.py", line > 651, in s > et_fullscreen > self._windowed_location = self.get_location() > File "C:\Python27\lib\site-packages\pyglet\window\win32\__init__.py", > line 321 > , in get_location > _user32.ClientToScreen(self._hwnd, byref(rect)) > ctypes.ArgumentError: argument 2: <type 'exceptions.TypeError'>: expected > LP_POI > NT instance instead of pointer to RECT > > > I also tried running test.py although I'm not sure exactly how that works. > Near the beginning when windows were supposed to start popping up, they > simply didn't. > -- > The last problem seems to be the one reported at issu 559: http://code.google.com/p/pyglet/issues/detail?id=559 It includes code to workaround that. Maybe you can give it a try and do follow ups in issues 510 - 559 ? claudio -- -- 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.
