Hi ron: 
In some applicatins I need to use colour information to determine when
to speak new text. In one instance I can hook and unhook it based on the
onChildFocus. In othe applications this won't work, as the script needs
to be global, I may be able to use of the onshow events possibly. Are
all problems fixed internally?
Chers
Sean.

-----Original Message-----
From: Ron Parker [mailto:[EMAIL PROTECTED] 
Sent: 08 August 2008 17:51
To: [email protected]
Subject: Re: OnChildClipRendered issue


That's not good.  It seems the automatic cleanup happens under the same 
conditions as the manual version, which means that while that problem is

also fixed post-beta-2, it won't do what you need.

Unfortunately, I don't have any other ideas at the moment other than to 
suggest either looking for another way to get the information you're 
currently getting from the OnClipRendered event or looking for some 
other event that can reliably tell you when to hook and unhook the event

so that you don't have it active all the time (which will tend to slow 
things down) and so that you don't have to disconnect it on shutdown 
(which, as we've seen, breaks things.)

What are you intending to use the event for?


Sean Farrow wrote:
> Hi Ron: 
> Even afte removing the disconnect line, the system still freezes.
> Any other ideas?
> Cheers
> Sean. 
>
> -----Original Message-----
> From: Ron Parker [mailto:[EMAIL PROTECTED] 
> Sent: 08 August 2008 17:29
> To: [email protected]
> Subject: Re: OnChildClipRendered issue
>
> 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
>>>>  
>>>>
>>>>   
>>>>         
>>>       
>
>  
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3340 (20080808) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>  
>  
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3340 (20080808) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>  
>
>   

 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3340 (20080808) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3340 (20080808) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

Reply via email to