As far as we know, it's just OnClipRendered and OnChildClipRendered.
They both do something special on disconnect that other events don't do,
and it was that thing that was causing the problem.
For the sake of completeness, I'll also point out that scripts that
don't use our ConnectEvent and ConnectObject methods to sink Window
events are also at risk of causing this lockup, but I don't think there
are a lot of those out there yet.
Jeff Bishop wrote:
Ron,
Is this for all events?
Jeff
----- Original Message ----- From: "Ron Parker" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, August 08, 2008 9:18 AM
Subject: Re: OnChildClipRendered issue
For now, I suggest just removing the Disconnect inside of OnShutdown
and letting the built-in failsafe handle disconnecting it for you.
We've tracked down the problem and fixed it, so eventually you'll be
able to disconnect the event on shutdown, but the fix didn't make it
into beta 2.
Sean Farrow wrote:
Hi: When trying to use the OnChildClipRendered of he ActiveWindow in a
script, when the application exits the application appears to exit
successfully but after a few seconds window-eyes freezes.
Note: There is currently no code in the OnChildClipRendered event. The
application is codegear rad studio 2007. The code is disconnected in
the
onShutdown event.
Using public beta 2.
Any help/thoughts apreciated.
Sean.
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3340 (20080808) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
