I'm a novice user, and I can see that this has been discussed before, however, none of the answers are either suitable or complete enough to help.I have recorded a test which involves entering text into list boxes and tabbing to the next and entering more text. The test is saved as vbscript and is completeley stand alone. On play back, this works fine for the first and second boxes, but on the third I always recieve "The 'Test Element 1' window is invisible and thus cannot be activated" error message. The subroutine posted below is exactly as it was recorded. Immediate play back failed, as have all subsequent play backs.Sub Test4Dim wndPrestigeSystemAdminDim toolbarWindow32Dim editSet wndPrestigeSystemAdmin = Aliases.Pradmin.wndPrestigeSystemAdminSet toolbarWindow32 = wndPrestigeSystemAdmin.ReBarWindow32.ToolbarWindow32Call toolbarWindow32.ClickItem("Add", False)Set edit = wndPrestigeSystemAdmin.page327702.Item.EditCall edit.SetText("Test 1")Call edit.Keys("[Tab]")Call edit.SetText("Test Element 1")Call edit.Keys("[Tab]")Call edit.SetText("T1")Call toolbarWindow32.ClickItem("Save", False)End SubCan anyone please suggest what is going wrong, or offer a work around?Thanks

Question to help diagnose:When you type in "Test Element 1" into the one field (the second field in that recorded script) is there any sort of component or screen refresh? What it seems is that, upon typing into that field and then tabbing to the next, some sort of screen update/redraw is happening that causes TC to lose the handle of the window you have referenced as "edit".

Hi,Also, in which line of your routine does this error occur? Also, what is in the 'additional info' section of the error in the log?

Hi MartinNo refresh that I am aware of, but some error checking does take place after text entry. I will take a look at the source code to check. The text is simply entered and immediately tabs to the next cell. The script fails at this line:Call edit.SetText("T1")The cursor can clearly be seen flashing in the correct cell for a few seconds, until the error message occurs.Tha additional information contains the following:Tested object:Aliases.Pradmin.wndPrestigeSystemAdmin.page327702.Item.Edit(Sys.Process("PrAdmin").Window("PrestigeSystemAdmin", "Elements - P-Series System Administrator", 1).Window("#32770", "", 6).Window("PrListCtrl", "0", 1).Window("Edit", "", 1))The above text is identical to that seen in the additional information for the previous succesfull text entry.Thanks for prompt response

I have the same problem, but at a bigger scale.My whole main window became invisible to TestComplete (it used to be ok before). When I look at it in Display Object Properties Window, the "VisibleOnScreen" property is true, but when I run any script involving any objects from the main window, this property is false for all of them including the main window itself. Somewhere on this forum there is an advice to activate the parent object first (before calling an object that has invisibility problem), but the parent of the main window is the application's process, and a process doesn't have "Activate" method. I tried Sys.Refresh() too, didn't help.I use TC 7.52 (JScript), Windows7x32 (I tried to switch Aero off, didn't help), the application is developed in Visual Studio 2010 (C++) and has a COM component.

Hi,VisibleOnScreen of an object is true only if this object is currently drawn (you can see it on your monitor). If it is not drawn, VisibleOnScreen will always be false, not matter how many times you refresh the object tree. Try using Visible instead.As for Activate, process shouldn't have it. This method is applied to windowed objects.

Window is invisible and thus cannot be activated

17 Replies

YMinaev
Staff
15 years ago
Hi Gary,

According to the snapshot, your control's Visible property is false. This can happen if the control is not drawn on the form when you're trying to access it. Do you see this edit box when TC tries to access it? I suspect that the click on toolbar (toolbarWindow32.ClickItem("Add", False)) doesn't perform the needed actions correctly.
Gary_1
Occasional Contributor
15 years ago
Hi Jared

Sorry for slow response. I have been working away from the office.

Yes, we are able to see the edit box. We can actually see the cursor in the box, yet this message is the result. There are definitely no overlapping windows. The test is played back exactly as recorded, with no changes whatsoever.

This is now a serious problem for us, for after investing in this product, we find we cannot test this apparently simple case, and cannot continue.

Any suggestions as to how we can resolve this issue would be welcome.

Gary
YMinaev
Staff
15 years ago
Hi Gary,

Does it help if you remove any user iteraction (such as clicks) with your control from your test and assign a value to it via its wText property (obj.wText = "value"). Assigning values to controls' properties shouldn't cause such errors.
sanketsamsi
14 years ago
I am seeing the same issue.

I am testing some screens which are tabbed. There are 3
tabs on one screen and the next screen has about 8 tabs. On the first screen (with 3 tabs), I double click on an
item which takes me to the second screen (with 8 tabs). When I try to playback the double click action on the first
screen, the test fails saying that ‘The window is invisible and thus cannot be activated’.

I have included the script and the screenshots for the
same. Please tell me as to how this issue can be resolved.

function Test2()

{

Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndOptions.ui60Drawn_W32.ui60Drawn_W32.btnSprint3.ClickButton(); Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndOptions.ui60Drawn_W32.ui60Drawn_W32.btnCmdashboard.ClickButton();

Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndui60MDIdocument_W32.ui60Drawn_W32.ui60Viewcore_W32.ui60Drawn_W322.Click(52, 14);

Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndui60MDIdocument_W32.ui60Drawn_W32.ui60Viewcore_W32.ui60Drawn_W32.Click(53, 59);

Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndui60MDIdocument_W32.ui60Drawn_W32.ui60Viewcore_W32.ui60Drawn_W32.Edit.Click(36, 9);

Aliases.ifrun60.wndui60MDIroot_W32.MDIClient.wndui60MDIdocument_W32.ui60Drawn_W32.ui60Viewcore_W32.ui60Drawn_W321.btnPriorityList.ClickButton();

}
YMinaev
Staff
14 years ago
Hi,

We are working with you via e-mail on this already.
Gary_1
Occasional Contributor
14 years ago
I am still seeing this problem. Any information you can share would be invaluable.
Gary_1
Occasional Contributor
14 years ago
I am still seeing this problem. Any information you can share would be invaluable.

Forum Discussion

Window is invisible and thus cannot be activated

17 Replies

Recent Discussions

Object spy crashes application

NameError: name 'Aliases' is not defined

....Preparing an object recognition hint....

Related Content

Window is invisible and thus cannot be activated

ListView Items invisible, thus cannot be activated

Test Execute window is Invisible