Ed Leafe wrote: > On Jun 19, 2008, at 8:41 PM, Paul McNett wrote: > >> and you are proposing: >> >> def _onOk(self, evt): >> self.onOk(evt=None) > > > OK, I wasn't thinking of code that is already written to accept the > call; I was thinking of subclasses that would have made the call. > > I'll try wrapping the methods with the sort of hack you proposed, but > I think that the fundamental problem is that "on*" means "event > handler" in Dabo. I'm changing the stub methods to be run* instead. > The handlers will try calling on*; if that errors, it will issue a > deprecation warning and re-call with a None param. Then it will call > the run* method. All new code should be written to use the run* > methods to process the standard buttons. Does that sound reasonable?
I see your point with on* being for event handling, but when I think about it these *are* events, even if they don't happen to receive any sort of event object. The user pressed "Ok", and we are responding to the event. I vote for keeping it as on*. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
