http://www.perlmonks.org?node_id=1079840


in reply to Is GUITest SetForegroundWindow/Sendkey thread safe?


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^2: Is GUITest SetForegroundWindow/Sendkey thread safe?
by MPQC (Initiate) on Mar 26, 2014 at 17:40 UTC

    Sad to hear that's the case, but thanks for the information nonetheless. I'll try to come up with a different solution which doesn't require me finding a unique name & sending a key to it. :)

      Sad to hear that's the case

      You could greatly increase your chances of not getting interrupted at an inopportune moment by (temporarily) raising the priority of your process.

      Of course, if the other application takes the same approach, your back to square one.

      I'll try to come up with a different solution which doesn't require me finding a unique name & sending a key to it. :)

      If you tell us what application your driving, someone might have another solution.


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.

      Sorta sounds like you have control over both the driven and driving sides of the system. How about you tell us a little more about what you want to achieve and we may be able to offer an alternative way to solve the problem (about three different ways spring to mind depending on what you need to do).

      <c>
      Perl is the programming world's equivalent of English