AutoIt Window Info crashing app

[mgillow]

newbie - just started experimenting with AutoIt yesterday. I was getting pretty excited about it, then ran into this problem. App in question is a fat client GUI written in VB6, running on a win2003 server. I'm trying to use the window info utility to identify controls. When I try to use it on some of the screens in the app, after a brief pause the app unceremoniously shuts down (window info app does not). The Application event log shows an application error and a Dr Watson entry - app error entry says "faulting module is msvcrt.dll" and the Dr Watson entry indicates exception error c0000005 at (msvcrt!strncpy).

This app's screens are pretty busy - there is a lot of dynamic info on it, some using an older version of the FarPoint spread control (spr32x30.ocx). Overall, what I'm trying to accomplish is automating input of test data into a clean install of an account management package, using the application GUI.

If I can't get control info for particular screens using the window info utility, is there some other way that I can find it? I tried WinGetClassList and it returns info (so much that the window used to display it won't fit on a 2360x1770 display), but I haven't been able to figure out how to make use of it.

Thanks!

[Community On Patrol]

Hi mgillow,

1st Welcome to the AutoIt Forums!

Some of the following tips may not apply to you, but it may make your life a bit easier here on the forum in the future.

CODE

• Did you know that we have an awesome search feature?

  You can find many answers to your current questions, just by typing in the right search patterns.

• A suggestion is to use the Advanced Search mode:

• Type your specific search term in quotes.
• Click the forum you want to search in (the one most likely to have your information would generally be the Example Script forum and or the General Help and Support Forum).
• Click on "Search titles only" radio button.
• Click perform search.

The above will help you narrow down your searches and prevent you from unneccesarily posting a new thread.

[*]Also, you should try to read the Sticky posts that are at the top of each of the AutoIt Forums you enter such as:

• FAQs (Frequently Asked Questions)

• Are my AutoIt EXEs really infected? (About false positives and what to do if you may encounter one)

[*]Keep in mind, the help file will be your best friend, however you may find some of the tutorials written by some of our elite forum members helpful.

• Valuaters Interactive AutoIt 1-2-3 tutorial

• LxPs Learning to script with AutoIt3

[*]Forum Etiquette:

• Making a new thread:
  • Use the Search feature first to see if your question has already been answered.
  • Look in the help file as well before even thinking of posting (When what you want could be obtained by simply reading the help file, you don't generally get a good response from your AutoIt community).
  • Titles are very important here. 1 word titles or titles like "help me", "write something for me", "I'm a noob" etc... aren't tolerated.
  • Make sure you are posting in the correct forum:
    • General Help and Support:
      • This forum is for AutoIt related support questions only. If you have a question related to another language, or nothing at all to do with AutoIt then you need to post in the chat forum, or in that languages perspective forum.
    • Example Script:
      • This forum is for AutoIt scripts/executables only.
      • Source code is preferred but not necessary, you do have the right to just post the binary of your project if you wish.
      • Please don't post questions in this forum unless it's directly related to a thread already existing.
  • Use common sense when creating a new thread.

    Ask yourself if the title is descriptive enough to even interest someone (preferably those that know what they are talking about) to even look at your thread, let alone reply in it.

  • Think about how it would show in the search feature if someone were to look for something just like you are looking for (think of the keywords you used yourself and obviously didn't find anything (because we know you used the search feature ) and use those types of keywords in your title as well).
• Thread content:
  • Be descriptive with your query. (Make sure we actually know what you want to do).
  • Show you've made an effort in coding what you want (provide the reproducer code (generally no more than 50 lines as people lose interest in debugging someones script for free)).
  • Don't talk in ebonics. A lot of the forum members are adults, and a lot of them know how to help you, but talk like a child, you'll be treated as such.
  • Don't ask for help making keyloggers, spam (even if it's to do as a prank), or anything that can be thought of as malicious. You'll more than likely have the thread locked by a moderator, and take a bashing from your fellow AutoIt community.
  • When posting code, use code boxes. This can be accomplished by using [code ]<content here>[/code ] (No spaces between the brackets []).

    Using code boxes will keep the indentation and make it easier to read for others to help you.

• Bumping your threads:
  • Use common courtesy here.

    Keep in mind every time you bump your thread to the top of the forum, you knock the other threads down a notch.

    Everyone posting for help has just as much right for their threads to get read as you do.

    Because of that, do not bump your post more than once in a 24 hour period.

    A Bump is simply posting in your thread with nothing that pertains to your query with the sole purpose of moving it up.

    Deleting previous bumps, and posting new ones is not tolerated, and the moderators can find those deletions, so do yourself a favor and don't cross that line >_< .

• Rude or obnoxious content:

  This falls pretty much under the common sense thing. If you use it (common sense) before posting, you won't have issues.

  • Don't use foul language, remember, a lot of the community is at work when they read these threads.
  • Don't provoke or instigate an argument with someone.
• Double Posting:
  • It's understood that sometimes there's a lag in the system, and sometimes people don't see their post go up right aways so they post again.

    If this happens to you, simply notify a moderator with the report feature in the post, and politely ask them to delete it.

  • If you're just creating another topic because your original topic is not being answered the way you want or at all, this is not tolerated. You could lose your posting privileges all together over it.
• Non-English languages
  • If English is not your primary language, please make an attempt to interpret (yourself or online) and post that interpretation.

    We have wonderful users from around the world, so after you've done your post in English, back it up with your question also in your native tongue (You may find your answer much quicker using both).

That's it for now, I hope you have a wonderful learning experience, and hope to see you contribute to the community as your knowledge grows.

[zfisherdrums]

Had the exact same problem with a legacy app written in C++ using Far Point Spread Controls. Try using the ANSI version of the Window Info tool. It is located in the same folder as the Unicode version.

Zach...

[mgillow]

Zach - thanks! The ANSI version is handling it OK.

Related question - were you able to identify a way to identify cells within the spread control form and read their content?

Appreciate the help!

Mike

[zfisherdrums]

Zach - thanks! The ANSI version is handling it OK.

Related question - were you able to identify a way to identify cells within the spread control form and read their content?

Appreciate the help!

Mike

Unfortunately, I was not able to obtain the cell contents using any direct window messages. My persistence paid off when I discovered that the app I was testing would populate the clipboard when I pressed CTRL-F9 (afer CTRL-C/V had failed ).

Couple follow-up questions: Is the app still in development? Do you have the ability to ask some developers if they can implement some king of logging, or ways to obtain the data differently? Does the control implement Active Accessibility?

Zach...

[mgillow]

Bummer. Hope the clipbaord trick works out for me, too. The app in question is still in maintenance, but they'd be more apt to invest the developer hours into a rewrite (and that wouldn't hurt my feelings a bit - the base app has been out there for 8 years).

Mike