[Pythoncard-users] Re: Pythoncard-users digest, Vol 1 #23 - 4 msgs

[Peter C. <pe...@pe...>]

At 06:05 PM 9/3/2001 -0700, pyt...@li... 
wrote:
>Just because we can support key down and up (and indeed mouse down and mouse
>up) do we actually need these events in PythonCard? In the spirit of
>KISS maybe we could leave them out. Or not, I'm just thinking out loud
>here so feel free to join in if you have an opinion.

I'm a big fan of a complete event model when I can get it.  At first I was 
surprised to see the mouseMove() event, which was not present in 
HyperCard.  But I assume it's there because wxWindows provides it, and I 
can see utility.  In HC I used to do Drag handlers in a loop on 
mouseDown(), but it would be more natural to use mouseMove(), so as not to 
block the thread.

I'm in favor of keeping KeyDown and KeyUp.  Some applications (especially 
games) can't be done without these events.  Of course, if they slow down 
the event loop too much, I might wish for a way to turn them off.  If 
performance became as issue, perhaps a set of flags could enable/disable 
each event type, with less common events turned off by default.