Contributions
Re: issue with XTPReport control on 64-bit
I tried TC8, same issue exisits. Attached please find screenshots, I captured same XTPPropertyGrid and XTPReport objects in 32-bit and 64-bit (TC7 and TC8). It looks like MSAA doesn't work forall XTPcontrols on 64-bit application, for example, forXTPToolBar object on 32-bit, each menu item is recognized as ObjectType 'MenuItem', but on 64-bit no childitem is recognized. I found a workaround for this viacombination of Text Recognition and OCR,but it's slowerand not as reliable. XTPPropertyGrid and XTPReport are a biggerissue for me,as they are widely used in my application, andI haven't found any reliable workaround for this. If you can provide a workaround/hotfix for this, that'llhelp a lot. Thanks.1.7KViews0likes0Commentsissue with XTPReport control on 64-bit
I've an application that uses XTPReport control (from Xtreme toolkit) that is supported in TestComplete by MSAA, it worksall rightin 32 bit application. This is table like object, MSAA shows ObjectType Table with child Row and Cell elements. But, in 64-bit, this doesn't get recognized as Table, it's shown as Panel object with no child. Is there anything special I need to do to use TestComplete on 64-bit, from help it seems there isn't a different installer for 64-bit. I'm using TestComplete 7.52. Will appreciate any help.27KViews0likes3CommentsRe: WaitNamedChild fails to find object
''What other criteria do you use in your name mapping for this object? Is the only thing you're using the #32770 class? If so, then I'm not surprised as there are many other objects, items, etc., that may appear with that same class.'' I use two - objecttype=dialog and wndclass=#32770, actually parent of 'Report' has only 1 child, so it doesn't actually matter. And, I check Exists and Visible property of 'Report' before searching its children. This is in MFC desktop application. "Where error shows up in your test log on this? There's an additional information panel in your test log which may give additional information" - log posts no error, do search operations not trigger logging? Is there any way to turn on the level of logging? By the way, I'm on version 7.52. "I would not use MappedName in a FindChild call at all because MappedName is first of all depending upon the object being recognized as being mapped in NameMapping. If you're already having trouble with WaitNamedChild, MappedName will almost certainly fail. Again, I think the root cause of the problem is not with the Print button itself, but something in how you're mapping to the Report object is handled." - That's what I expected, but actually FindChild successfully finds it. "Now, another possibility is that this call to find the print button is probably occurring after some sort of test step that generates the report in the first place. So, there is probably a delay between clicking the button to generate the report and when the report appears on screen. I would suggest going further up in your code and getting your actual Report object using a WaitChild or WaitNamedChild or something and using a delay parameter of something significantly greater than 0 (like 60000)" - This was my first guess, so after FindChild successfully found it, I called WaitNamedChild again, unfortunately, it still failed. Also, as I mentioned in previous post, this actually works fine when in TestComplete script, it's only when I make the call via connected app, which suggests there is a bug with WaitNamedChild, possibly in how string parameter from connected app is handled. Attached please find screenshots of the hierarchy. Appreciate your input. Thanks, Akash1.4KViews0likes0CommentsRe: WaitNamedChild fails to find object
Hi Robert, Here's an example: I've'Report' where Report is#32770 class. I use WaitNamedChild to get Print Button in 'Report' - mapped name - 'Print' - properties mapped with - objecttype = Button, objectidentifier = Print. There is only one child with these properties. (screenshot attached) validate after this call doesn't exist:validate = parent["WaitNamedChild"](name, 0); (where parent is Report object and name is "Print") As a workaround, I call FindChild, two properties, visible,mappedname,depth=0.Report can have anywhere from 20-70 children, so this is quite slow, but finds it all right. So far, I've seen this fail only when parent is class#32770, but not consistently. If I call WaitChild for this same object it finds it all right. Also, I called WaitNamedChild in TestComplete directly, exact same parameters, and it worked. I'm using connected application - C#, I tried the same in VB.net, just in case, but same result. It appears there is a problem only when using this with connected app. Thanks.1.4KViews0likes0CommentsWaitNamedChild fails to find object
I'm using this methodto find mapped objects in an MFC application, in various cases, it fails to find the object even though it's there. Seems it's when parent object has WndClass #32770. For all popup windows, it consistently fails.There also are regular (non-popup)windows that have this class, where it is inconsistent.Using FindChild - depth 0, finds it all right, downside being, it is slower. Is there any way to fix this?Or, afaster way to find child? Thanks.15KViews0likes5CommentsTestComplete 7.52 on 64-bit windows 7
We've an enterprise version and have been using on 32-bit machines successfully. Now that I'm trying to installit on64-bitmachine, it fails to even start up. Installation goes through all right, but as I start up, it stays in not responding mode - screenshots attached. I noticed it's still the 32-bit TestComplete.exe running, is there a different package for 64-bit? If so, where can I get it from? Any help is appreciated.21KViews0likes2CommentsRe: Application crashes when using testcomplete Refresh
Attached please find the dump and log from AQTime. This time I was refreshing the a tabcontrol object MSVC class name 'CMainTabCtrl' and application closed. If I take out the call to refresh, this issue is resolved, but it sometimes failsto find dynamic object in the tree. Thanks, Aakash1KViews0likes0Comments