ContributionsMost RecentMost LikesSolutionsRe: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. Thanks, the issue can't appear now. If it still be there, I'm glad to have a try. Re: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. For virtus detected in China, I'm sorry I'm late to reply you. Thanks all, I found this issue can't appear in our test cases. Re: TC report an error " Unexpected window: '' " for one normal subobject. Thanks, the issue still exists in my project. But for your information, I know how to trigger the unexpected window. Maybe tested App has conflict with Testcomplete. I will work on it to solve. Re: TC report an error " Unexpected window: '' " for one normal subobject. " If Window.WndClass = "#32770" Then " wascommented and should be deleted. TC report an error " Unexpected window: '' " for one normal subobject. Like the pic, it report an error for unexpected window, but it don'ttriggermy events llike last unexpected window, And the unpxected point to " Sys.Process("Inventor").WPFObject("HwndSource: MiniFrameBorder", "", 1) " that belongs to my tested app.But If last waring unexpected window don't appear, the error unexpected window won't appear. So my question how to handle the second error unexpected window? And it's my events: Sub GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams) Call Log.Picture(Window, "Screen image", "This image was added to TestLog from the GeneralEvents_OnUnexpectedWindow procedure") Log.Warning "Unexpected Window",, pmNormal If Window.WndClass = "#32770" Then If Window.waitWindow("Button","&Yes",,5000).Exists Then Window.waitWindow("Button","&Yes",,5000).Click If Window.waitWindow("Button","&OK",,5000).Exists Then Window.waitWindow("Button","&OK",,5000).Click End If End Sub SolvedRe: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. OK, I will have a try. Thanks a lot. Re: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. Oh, it's a work window like PS work area. They are belong to the same windows client. Re: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. It don't need be fullscreen because the test object is under the app that isfullscreen. Re: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. Yeah, the DPI setting is 100% and the help doc I can't find any ways to solve this random issue. Thanks! Re: There was an attempt to perform an action at point (1439, -108), which is out of the window bounds. Refreshmappinginfo method can' t solve this issue. Actually, it's random question in my test case. Appeared on running project and not appear on running single case. Like the picture, So I don't know the testcomplete how to calculate the coordinate. Now I will cancel the unstable this case. Thanks!