My tips ideas

Well, learn to enumerate processes by pid and/or to associate pids with windows, (see TidPid GetWindowThreadProcessId, see Win32::FindWindow, patch GuiTest.xs, Win32::GUI::GetWindowThreadProcessId())

and use PostMessage() for everything that GuiTest doesn't already have a wrapper for (example Win32::GUIRobot says CloseWindow $HWND Sends close signal to a window. ),

and fix hwndSendKeys so you can send keys without corruption (not capslocks and other global state stuff -- not Ctrl+F4 when you have CloseWindow -- just the keys you need),

and use autoit to fill in the blanks ( FWIW, if you look at http://search.cpan.org/~shimi/Win32-Watir-0.06-withoutworldwriteables/MANIFEST or Win32::IEAutomation you can see they're using AutoIt COM interface from perl :)

Does this make sense?

more generic win32 tips

If you want to automate anything on win32 you have to absorb the following knowledge . It mostly consists of learing the ole/excel/powerpoint... object model, and using Win32::OLE to call it or sending messages using guitest. OLE is essentially a fancy/standardised way of sending messages. Its very much like web-scraping, you have to know HTTP/HTML DOM .... the rest is just legwork

In reply to Re: Is GUITest SetForegroundWindow/Sendkey thread safe? by Anonymous Monk
in thread Is GUITest SetForegroundWindow/Sendkey thread safe? by MPQC

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.