[PYTHONMAC-SIG] Incompatible change

[Jack Jansen]

> >where callable() is called for each event and should return non-zero if the
> >event is fully handled (otherwise the sioux and other handlers are called) be
> >good enough, or should I have AddEventHandler/RemoveEventHandler so that
> >different packages can all have their own event handlers?
> 
> Could MacOS.SetEventHandler(None) be shorthand for RemoveEventHandler()?
> And MacOS.SetEventHandler(callable) would replace any previously installed
> handlers.

Sorry, what I meant with Add/Remove was that you could have multiple event 
handlers. After all, in C we already have a couple (sioux, possibly stdwin), 
so I thought it might be more general to allow multiple packages to each 
install their own event handler. But I guess I'll just implement the easy case 
(SetEventHandler) for now, and I'll wait until people ask for multiple 
handlers.

> >> ... so I would prefer backward compatibility for now.
> >
> >Hmm.
> 
> I see that it's harder to keep the old functionality alive, but since many
> people do not update right away, I'd like have some sort of mechanism to
> allow my code to run either in 1.4 or 1.5 (whenever that will be).

Ok. I think that a codebase "in the field" is a good reason for backward 
compatability. I'll leave EnableAppswitch in.

How about SetScheduleTimes?
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@cwi.nl      | ++++ if you agree copy these lines to your sig ++++
http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm 



_______________
PYTHONMAC-SIG  - SIG on Python for the Apple Macintosh

send messages to: pythonmac-sig@python.org
administrivia to: pythonmac-sig-request@python.org
_______________