On 23-Oct-06, at 4:21 PM, Alfred Van Hoek wrote:
On Oct 23, 2006, at 2:17 PM, Alexander Cohen wrote:
But why do i need to do that. Is rb really messing that much with
the hierarchy?
Yes, RB requires us to give a valid HIViewRef (ControlRef) from the
custom REALcontrol (it fails to do so whether or not the
REALcontrol lives on a composite or non composite window.
Subclassing the canvas is a slightly better alternative, given that
a valid ControlRef is provided when in non-composite mode.
Thus, this limit you to create yourself a HIView using OS_API's
only. If you have an underlying REALcontrol you can use the
REAlcontrol callbacks to create messages that you would send to
your HIView handler (this is a safer way), or do it your way,
directly on the REALwindow. However, this will cause you a lot of
grief, given that your HIView is the last in the control order and
if your HIView is focus aware, all bets are off.
Note that on Windows you will not have these troubles, given that
the REALcontrol always provide you with a valid HWND. So I would
urge you to make the point that the Mac target in the plugin SDK is
not in par with the WIn target in the plugin SDK. Therefore, REAL
should give a very high priority to mature the Mac target.
Ive actually tried a few things such as removing all rb custom
HIView's that they installed... still not getting my tracking events.
Moving myself to the front of the z-Order... still no clicks. Ive
gotta say that i have a feeling that rb is doing something that is
not very kosher with the window or the view hierarchy. I wish they
could actually respond and give some sort of hint of what i need to
do to get this working. RS, i know your listening! :)
AC
_______________________________________________
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>
