On Jan 20, 2006, at 8:16 AM, Suikyo wrote:
The cause seems to have been a collision of the "Open" event.
Right, and if you want to get access to this "Open" event defined to a
REALcontrol, then map that event to a pointer function, which you then
can use internally. That also provides the time point
(X-platform-compatible) where you can safely use REALGetControlWindow,
GEtHWND, and other API's relying on valid window(s).
You use the REALeventInstance struct to map "Open" to a REALproc, and
because you define this mapping to the REALcontrol.eventInstances this
"open" event vanishes from the list of the events that come with a
REALcontrol. It also allows you to redefine "Open", and all this bears
on the similarity when you would subclass a control, implement an open
event of a control, and then remapping of the "Open" event to
subsequent sublasses of the control in the RB-IDE.
Alfred
_______________________________________________
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>
|