• Subject: RE: Client Access Emulator Macros with 10 Second Waits
  • From: Chris Bipes <rpg@xxxxxxxxxxxxxxx>
  • Date: Mon, 25 Oct 1999 07:53:57 -0700

Without keyboard buffering you will need the waits.  With keyboard buffering
you do not need the waits.  Thank you IBM for always putting in the waits
weather you have keyboard buffering on or off.  A statement like: "If
keyboard buffering = *OFF..." would make it better.

With keyboard buffering off, you get the old keyboard lock errors if the
macro tried play back a key and the system was not ready.  It would be
really nice if the macro playback just waited until the keyboard was
unlocked before sending the next sequence of keys and not code the waits
into the macro.  How about it IBM?

Chris B.         mailto:RPG@Cross-Check.com



-----Original Message-----
From: Reger, Bill [mailto:breger@levitz.com]
Sent: Wednesday, October 20, 1999 8:19 AM
To: 'Midrange-L'
Subject: Client Access Emulator Macros with 10 Second Waits


One thing that has always puzzled me is why IBM puts the 10-second waits
into the Macros that you can record and playback in the Client Access
Emulator.  The following is an example of a macro after recording:

[wait app]
"addlible qgpl
[enter]
[wait inp inh]
wait 10 sec until FieldAttribute 0000 at (20,6)
wait 10 sec until cursor at (20,7)
[wait app]
"addlible qtemp
[enter]

These 10-seconds waits sometimes cause the macro to take a lot longer to
playback than it should.  I have generally gone into the macro and removed
the 10-second wait line(s) and the [wait app] line immediately following.
Removing these lines has never caused my any problem other than it's a royal
pain in the neck to remove these, particularly on big macros.  Does anyone
know why these waits are inserted and whether removing them might cause me
some grief someday?  Is anyone at IBM listening who would like to respond?

William K. Reger
Senior Project Manager
Levitz Furniture Corporation
Phone:  (561) 994-5114
E-mail:  breger@levitz.com <mailto:breger@levitz.com> 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.