Loading ...
Sorry, an error occurred while loading the content.

584RE: [perlguitest] Re: PushChildButton problems

Expand Messages
  • Coleman Tom
    Sep 30, 2004
    • 0 Attachment
      nice article.

      interesting how the id and window text can get mixed up

      Some languages allow you to specify if the value being provided is a handle,
      id, or caption with a special character that precedes the value.

      PushChildButton( $parrent, "=5436" ); # control handle
      PushChildButton( $parrent, "#5436" ); # control ID
      PushChildButton( $parrent, "@5436" ); # control ordinal ( tab order )
      PushChildButton( $parrent, "5436" ); # control caption

      I would suggest not using this secret code, but rather add another optional
      argument, so one can specify what to look for.

      -----Original Message-----
      From: pkaluski [mailto:pkaluski@...]
      Sent: Friday, September 24, 2004 11:53 PM
      To: perlguitest@yahoogroups.com
      Subject: [perlguitest] Re: PushChildButton problems


      Hi,
      I had the same problem. And I believe I have found the reason why it
      happens. I placed a detailed explanation on my website. Have a look:
      http://www.piotrkaluski.com/automation/gui/carfl_pushcb.html
      <http://www.piotrkaluski.com/automation/gui/carfl_pushcb.html>

      --- In perlguitest@yahoogroups.com, "chobitex" <chobitex@y...> wrote:
      > Hello,
      >
      > I have been using the GuiTest package for automation data
      gathering.
      > I have noticed that the PushChildButton() function is inconsitant,




      -------------------------------------------------------------------------------
      This message and any included attachments are from Siemens Medical Solutions
      USA, Inc. and are intended only for the addressee(s).
      The information contained herein may include trade secrets or privileged or
      otherwise confidential information. Unauthorized review, forwarding, printing,
      copying, distributing, or using such information is strictly prohibited and may
      be unlawful. If you received this message in error, or have reason to believe
      you are not authorized to receive it, please promptly delete this message and
      notify the sender by e-mail with a copy to Central.SecurityOffice@...

      Thank you

      [Non-text portions of this message have been removed]
    • Show all 4 messages in this topic