perdon, si es 64 bits 2010/4/28 Lucas Caro™ <[email protected]>: > lu...@mayhem:~/pkg/cocos2d-0.3.1-beta/test$ python > Python 2.5.5 (r255:77872, Feb 2 2010, 00:25:36) > [GCC 4.4.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. >>>> import ctypes >>>> ctypes.c_uint is ctypes.c_ulong > False >>>> > > my python2.6 dice: > > lu...@mayhem:~/pkg/cocos2d-0.3.1-beta/test$ python2.6 > Python 2.6.5 (r265:79063, Mar 20 2010, 03:56:44) > [GCC 4.4.3] on linux2 > Type "help", "copyright", "credits" or "license" for more information. >>>> import ctypes >>>> ctypes.c_uint is ctypes.c_ulong > False >>>> > > y al ejecutar el test: > > on_enter > grabbing fbo > idx: c_uint(1L) > pt: <cparam 'P' (0x2d685b0)> > freeing fbo > Traceback (most recent call last): > File "test_del__fbo.py", line 64, in <module> > director.run (main_scene) > File "../cocos/director.py", line 411, in run > event_loop.run() > File "/usr/lib/pymodules/python2.6/pyglet/app/xlib.py", line 94, in run > sleep_time = self.idle() > File "/usr/lib/pymodules/python2.6/pyglet/app/__init__.py", line 187, in idle > dt = clock.tick(True) > File "/usr/lib/pymodules/python2.6/pyglet/clock.py", line 696, in tick > return _default.tick(poll) > File "/usr/lib/pymodules/python2.6/pyglet/clock.py", line 295, in tick > item.func(delta_t, *item.args, **item.kwargs) > File "../cocos/cocosnode.py", line 714, in _step > action.step(dt) > File "../cocos/actions/base_actions.py", line 101, in step > self.update( min(1, self._elapsed/self.duration ) ) > File "../cocos/actions/base_actions.py", line 346, in update > self.actions[ found ].start() > File "../cocos/actions/instant_actions.py", line 134, in start > self.func(*self.args, **self.kwargs) > File "test_del__fbo.py", line 57, in del_fbo > glDeleteFramebuffersEXT(1, ce.byref(idz)) > ctypes.ArgumentError: argument 2: <type 'exceptions.TypeError'>: > expected LP_c_uint instance instead of pointer to c_ulong > > > > > On Tue, Apr 27, 2010 at 11:39 PM, claudio canepa <[email protected]> wrote: >> >> >> On Tue, Apr 27, 2010 at 11:16 PM, Facundo Batista <[email protected]> >> wrote: >>> >>> On Tue, Apr 27, 2010 at 3:30 PM, claudio canepa <[email protected]> >>> wrote: >>> >>> > 1. in cocos.menu.Menu.__init__ schedule a do_nothing (tested, works) >>> > or >>> > 2. in cocos.menu.Menu boost temporaly the fps when on_key_press and >>> > key.DOWN >>> > or KEYUP (tested, works) >>> > or >>> > 3. modify the relevant tests to add a do_nothing in the Menu subclass >>> > (tested, works). Add the appropriate comment so that users knows why the >>> > do_nothing is used. Anyway, they must know this for scenes that not >>> > contain >>> > a menu. >>> > I favor the third, because it exposes a behavior that the user must >>> > know, >>> > but I open to adopt other. >>> >>> Agree that if user finds this behaviour in other scene, she would need >>> to find out why it's happening, and learn it. >>> >>> But, I'd go for the least surprising behaviour. Don't leave it hard to >>> get it right with a comment "you should know this", make it the way >>> that it just works. >>> >>> So, I'd go for 1 or 2, I think 1 is the simplest, right? >>> >>> -- >>> . Facundo >>> >> >> >> >> Yes, 1 will be simpler, and 2 only will save some batery if the user left >> running such a menu screen for a long time. >> Will commit 1. >> >> -- >> claudio >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "cocos2d discuss" 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/cocos-discuss?hl=en. >> > > > > -- > Lucas S. Caro > [email protected] > 202-657-Go33 (4633) > http://www.triplesmart.com >
-- Lucas S. Caro [email protected] 202-657-Go33 (4633) http://www.triplesmart.com -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" 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/cocos-discuss?hl=en.
