Yes it can. The problem is when the user hits enter - say 10 times. Lets say the program clears the screen, prints the message, and has a 'press any key to continue' type prompt. After the user presses enter, you clear the screen again and continue on your way.
If the user presses enter all these times, then the message will flash by in an instant (depending on the speed of the terminal etc..). So, doing an INPUTCLEAR (Im spelling it right these days) before the next input prompt, "Press any key to continue", will clear all those key strokes the users haphazardly pressed and force them to read the message. Anthony -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Taylor Sent: Thursday, September 29, 2005 2:43 PM To: [email protected] Subject: Re: [U2] CLEARINPUT - Universe PRINT @(-1) prior to the printing the error message will clear the screen and move the cursor to the top left corner of the screen so that the error message can be viewed without confusion. Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated EDI Translation and DataSync Integration www.sysmarkinfo.com ----- Original Message ----- From: "Anthony Dzikiewicz" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, September 29, 2005 9:22 AM Subject: [U2] CLEARINPUT - Universe > I don't know why I cant find the CLEARINPUT statement documented. > Maybe it was a suggestion from the group way back when. We are > working on a program that pops up error messages. I want to be sure > that the users see this message. What happens a lot, is that our > 'speed typers' are about 10 strokes ahead of the program. A lot of > what they do is redundant and they arent always in the habit of paying > attention to what is on the screen. So, I asked the programmer > working on this to put a CLEARINPUT before the pop up messages. This > way, the error message will have a better chance of being seen. > > I have used CLEARINPUT in the past and this statement is in a handful > of existing programs. The programmer said she had never heard of this > and when she looked in the manual and HELP BASIC CLEARINPUT. She > didn't find anything. So, now Im wondering - how did I find out about > this ? I looked in an old (real printed and bound) BASIC manual and I > didn't find it. I looked in the PDF BASIC manual and I didn't find > it. Actually, it is in the reserved word list. > > I would assume this is still a valid command - it does compile. > > Can anyone enlighten me ? My concern is that this could be an old > command that was replaced by something new ? I don't want to continue > to use something that might not be supported. > > Anthony > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
