When the debugger takes over the app is paused for the most part.
This is the only time the control becomes clickable. While the
debugger has not taken over, the control is not clickable in that the
window receives the events instead.
The HIView is the lowest (newest) in the content view of the window.
Yet something, I'm thinking internally with RB, is catching the event
first and thus the control may never be clicked and used.
I'm really not interested in the event itself, I want to know *what*
is catching it first, and how to let my control become clickable.
Like I said, it's clickable when the debugger has taken over, and
events come through. Otherwise, I never receive the event and it
never gets clicked.
--
Thom McGrath
The ZAZ Studios
<http://www.thezaz.com/> AIM: thezazstudios
On Mar 3, 2006, at 3:42 PM, Jonathan Johnson wrote:
I'm not sure what you mean by "paused." If you install a
kEventClassMouse/kEventMouseDown handler on the Window sometime
*after* REALbasic has installed its handler (e.g., the Open event),
you will be called first. I know, because I've done it before.
_______________________________________________
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>
