Re: [ocemp-devel] ocemp-devel Digest, Vol 5, Issue 2

[<ma...@sy...>]

e-n...@we...:

> When using pygame events put pygame.event.pump() in the mainloop. Otherwise
> you will get events with an "Unknown event"-type. Note that when using

Right. I'll add that to the _loop() processing.

> pygame.event.wait() the program will do nothing in that time. Nothing means
> so blinking cursor, no animations, no "Player 1 has finally finished his

Blinking cursors and such stuff which is directly handled by the GUI framework
using the SIG_TICK event, which is raised all 10ms.

> turn"-message, and when playing online the game will keep saying "waiting for
> player soandso" until you cause an event. I would advice to use
> timer=pygame.time.Clock() #below the imports
> timer.tick(30) #in the mainloop

Currently the timer.wait()/delay() methods are used. I do not see any
difference between those methods and using the Clock class here.

> Maybe start thinking about threads NOW. Its really hard adding them
> afterwards. See
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/491280

No. For which purpose there should be threads? There are currently no async
operations, polling or whatsoever and will definitely _not_ go into the GUI
(again).

> It would be nice if someone could post a step-by-step tutorial (to
> e-n...@we...) about how to get ocemp to work. I seem to be too
> stupid or something to do that myself. Once i manage i will start
> contributing.

The ocemp CVS module does not work. It is broken in several ways and won't be
fixed anymore as it is superseded by some code lying on my local harddrives.
I'll check the new stuff in at monday.

Regards
Marcus