dodes_po
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Visual C++ Open Application Access violation
Hey Allen, >> Will it be possible to make a wxWidgets plugin same as MFC or Qt one? > No. Currently, you can only create .NET and WPF control support modules. Is there any plan in future (near? :)) to support also other controls than .NET one? Or is there some other way to add custom wxWidgets control support? > Please send the file to us via our Contact Support form (http://www.automatedqa.com/support/message). Done Thanks Dodes1.7KViews0likes0CommentsRe: Visual C++ Open Application Access violation
Hey, I've read the manual about plugins. Will it be possible to make a wxWidgets plugin same as MFC or Qt one? With this approach I'll be able to support any wxWidgets based classes. But in manual you can find: Creating plug-ins that support third-party Win32, Java, Qt and other controls is currently not available. But how are Qt, MFC plugins created then? Thanks Trigve1.7KViews0likes0CommentsRe: Visual C++ Open Application Access violation
Thanks for reply, No I don't see the icon as stated in help topic. Yes I know I can use TC without internal properties but I want to try some script code which uses public interface of wxWidgets objects. I think something is wrong with debug symbols reading. I've compiled sample application from wxWidgets and can post it to you if you want example which demonstrate the problem (Cannot attach it there because .zip has about 13 MB and allowed size is only 10). Thanks Dodes1.7KViews0likes0CommentsRe: Visual C++ Open Application Access violation
Hi Alexei, As I've said I've already read the manual about C++, Open Application s, wxWidgets, etc... Neither of those links provided answer to my question. I've compiled my app as stated in manual. When I then run thy application and locate it in the object browser I cannot see any wxWidget's instances show there. I see only generic windows "objects". As stated in manual there are 2 options to use wxWidgets.The first one is to use some special wrapper classes. This method as I understand is provided automatically for MFC, Win32, ... (Or?). The second one is to use debug info agent. If I understand it correctly, this method read debug info (probably .pdb files) and get from there instances which are associated to windows. Should I provide some more info to TC to be able see some wxWidgets instances in object browser? And now my question: I have an wxWidgets application which is compiled as stated in manual with debug info ON, etc... What exactly should I do to be able see/use wxWidgets's based instance in TC object browser/script? Thanks Dodes1.7KViews0likes0CommentsRe: Visual C++ Open Application Access violation
Thanks for reply, Ok I'll try to not run the app in debuger. I've also already read "Open Applications in Visual C++" in manual. I've also forget to mention that I'm using wxWidgets 2.9.x from svn trunk. In which state is it supported in TC? Because I cannot find any wxWindow instances and so in object browser. Thanks Dodes1.7KViews0likes0CommentsVisual C++ Open Application Access violation
Hi, I'm trying trial version of TestComplete. I have C++ application which is compiled as Open Application as suggested by manual with debug info, RTTI, etc. When I then run application from VS and click at Object Browser in TC I've got Access violation reading location 0xXXXXXX. When I run the application without debugger attached (Not from VS) and refresh Object Browser in TC I see my app but WITHOUT the symbol that signals if the application is opened (Open Application). Someone knows what could be wrong? I'm using VS 2010, Vista 32 bit. Here is stack where the exception occurs: > kernel32.dll!_IsBadReadPtr@8() + 0x3c bytes kernel32.dll!_IsBadCodePtr@4() + 0xf bytes tcDelphiHook.dll!111839bf() [Frames below may be incorrect and/or missing, no symbols loaded for tcDelphiHook.dll] tcTextSpy.dll!1139c82d() tcTextSpy.dll!1139c5f4() tcTextSpy.dll!113cf72e() tcTextSpy.dll!1139c995() tcDelphiHook.dll!111d70ce() tcDelphiHook.dll!111815e7() tcDelphiHook.dll!11168c37() tcDelphiHook.dll!1116603d() tcDelphiHook.dll!11167904() tcDelphiHook.dll!1116612b() tcOpenAppHook.dll!127f807e() tcOpenAppHook.dll!127f84e8() tcOpenAppHook.dll!127f8190() oleaut32.dll!_DispCallFunc@32() + 0xb2 bytes oleaut32.dll!CTypeInfo2::Invoke() + 0x1b1 bytes oleaut32.dll!_DispInvoke@32() + 0x23 bytes tcOpenAppHook.dll!127dde1b() oleaut32.dll!_IDispatch_Invoke_Stub@48() + 0x52 bytes oleaut32.dll!_IDispatch_RemoteInvoke_Thunk@4() + 0x5b bytes rpcrt4.dll!7758fb31() rpcrt4.dll!77525599() rpcrt4.dll!77526d4a() rpcrt4.dll!77526ccc() rpcrt4.dll!775265b2() rpcrt4.dll!775250ea() rpcrt4.dll!7752788e() rpcrt4.dll!77530573() rpcrt4.dll!7753011c() rpcrt4.dll!775300e3() rpcrt4.dll!77530166() kernel32.dll!@BaseThreadInitThunk@12() + 0x12 bytes ntdll.dll!___RtlUserThreadStart@8() + 0x27 bytes ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes Thanks Dodes16KViews0likes11Comments