On Jul 26, 2006, at 4:47 PM, Jonathan Johnson wrote:
1) Focused Control Menu Handler
2) Intrinsic focused-control menu handler (ie, built-in handler)
3) Window Menu Handler
4) "Parent" window menu handler (in the case of floating windows,
this would be the next non-floating window)
5) App Menu handler
6) MenuItem Action event
So, to override the default copy behavior of an EditField, create
an EditField subclass with an EditCopy menu handler.
Wait,that says if even if I have menu Handler but in my subclass but
want it handled at the window or app level for generality, it's now
impossible if an intrinsic handler exists? That seems VERY wrong, if
I have a handler and it returns false, it means I want to handle it
at higher level nota lower one.. and an intrinsic handler SHOULD be
the lowest one... Which means if I have defined a handler, no matter
if it handles it or not, the intrinsic handler should not be called
because it have been overridden
In other words if I define a handler in a subclass the intrinsic
handler should not be called as my intension is to override it...
Intrinsic handler are of dubious value IMO... Not having them and
always providing functions that we can call from our own handlers
would be best I think
- Karen
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
