The window with the handle exists but did not respond

[m_Ghorbani]

I always get this Error :-(

The window with the 0x00010800 handle exists but did not respond during the auto-wait timeout (150 ms).

My question is: How can I check if handle exists but did not respond?

I want if this error appear, I run the command again.

[AlexKaras]

Hi,

Is this somehow related to TestComplete?

[Wamboo]

Can you show the code you work with?

[m_Ghorbani]

Ja Sure

SearchObject0 = Objects_Toolsbar.OptPageSearchFilter0(PageName,ParentNodeName); 
        if SearchObject0 != 'nothing' and Tools.WaitForAvailablity(SearchObject0):
                SearchObject0Count = Tools.WaitForInt(SearchObject0.wItemCount)
                for SearchObject0Index in range(0,SearchObject0Count,1):
                        Tools.WaitForToolsbarAvailablity(ListViewObject)

			#The Problem is in this line

                        SearchObject0.ClickItem(SearchObject0Index);
                SearchObject0.ClickItem(0)
                Tools.WaitForToolsbarAvailablity(ListViewObject)

[Wamboo]

In my opinion, it's just that this piece of code

Tools.WaitForInt(SearchObject0.wItemCount)

in which the script waits for an object can cause an error. This is your method used in scripts?

I am not an expert in VB but maybe map this object (then NameMapping will manage the "state" of this object).

[m_Ghorbani]

Thank you so much for your reply,

This Code is Python :-)

def WaitForInt(Object, Message = ""):
    Delay(Time.OptTimes('SmallTime'))
    if Object is None or Object == 'nothing':
            return 0
        
    Number = Object
    while True:
            if isinstance(Number,int):
                    break
            Delay(Time.OptTimes('SmallTime'))
            Number = Object
    return Number

[m_Ghorbani]

And can you please explain more about following satatment:

"then NameMapping will manage the "state" of this objec"

[TanyaGorbunova]

Hi @m_Ghorbani,

I recommend that you review the following article:

https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-a...

It explains the recommended approach to wait for a window during the test execution.

Also, 150ms for the Auto-wait timeout may be too small. The default value of this option is 10000. Try increasing this option and see if this affects.

[m_Ghorbani]

Thanks for your Tips.
I have already read it!

Also,
What is problem with WaitProcess
She is just waiting for declared time and that is < 1Million ms!!!!
That is a big problem. Because some time I need to test an update a software and Progress bar need 5 hours to 100%

What is a Problem for exists!
She is True when the Object is just created but not ready for use!

What is problem for auto-wait 10k:
That too big for me, now I test a software, that have more than 40k object to test just in a one page.

[AlexKaras · Accepted solution]

Hi,

> What is a Problem for exists!
> She is True when the Object is just created but not ready for use!

Exactly so and this is by design. TestComplete searches for the object and lets you know through the .Exists property whether or not the object was found.

The 'readiness' of the object is specific to your given tested application. One object can become to be ready immediately, another one - only after it is populated with data over dead-slow connection and the third object may never become ready because the data provider is not accessible at all.

Also, there is no clear definition of 'readiness'. Usually, you may expect that the object is enabled. But an opposite situation is quite possible too. For example, you may need to wait until all object's entities are processed and the object becomes disabled or not visible.

So TestComplete has no internal criteria to determine if the object is ready and this must be implemented in code by you using your knowledge of the given tested application.