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

[Clip] Re: SetDebug xxx.txt

Expand Messages
  • Sheri
    ... Not just that, but if the CPU has other programs running in the background, or a scheduled event suddenly starts up, it will run more slowly than usual and
    Message 1 of 6 , Jul 18, 2007
    • 0 Attachment
      --- In ntb-clips@yahoogroups.com, "ebbtidalflats" <ebbtidalflats@...>
      wrote:
      > --- In ntb-clips@yahoogroups.com, Eric Fookes <egroups@> wrote:
      > >
      > > No need to use the Wait command to do that. The ^!KeyboardDelay
      > > is what you need if you want to slow down key strokes.
      >
      > On the one hand, delay will work for each keystroke, but it must
      > be set long enough to work with any CPU, even the slowest. That
      > may seem an awfully long wait on a fast CPU.
      >

      Not just that, but if the CPU has other programs running in the
      background, or a scheduled event suddenly starts up, it will run more
      slowly than usual and that can throw off the timing. Sending blind
      keystrokes is a very primitive way of trying to automate windows
      processing. What would be nice is if it were possible to test other
      aspects of the focused window besides the ^$GetAppTitle$ to make sure
      your keystrokes did their job. Then you could put other tests in your
      clip to make sure the keystrokes sent had the desired effect before
      proceeding to the next set of clip instructions.

      Regards,
      Sheri
    Your message has been successfully submitted and would be delivered to recipients shortly.