On Jul 26, 2006, at 5:29 PM, Jonathan Johnson wrote:
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...
Correct. And that's what it does. The Focused control menu handler
is what you would implement in a subclass. It's called before the
intrinsic one is called.
I think you may have missed my point.. If my Handler in the subclass
returns false because I want it handled at a higher level I would not
want the intrinsic handler called ever...
In other words for a SUBCLASS if i define a menuhandler, I have
decided I DON'T want the intrinsic handler and so take full
responsibility for the handler even if I decide to return false...
I'm saying I think that in this case (a handler created in a
subclass) that handler should override the intrinsic handler, not
just come before it in the calling chain... IMO there SHOULD be a way
to do that.
There can times when menu actions need to depend contexually on the
state of more than one control and you want it it handled at the
window level...
There can be problems when RB tries to be TOO helpful! BTW I thought
adding intrinsic handlers to a jack of all trades such as the
listbox was just such a a case.
- 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>
