Re: [U2] Press any k
That's the trouble. It CANNOT be used 'all over the place'. Surely you have names and addresses who's lengths are often not their maximum. Even dates can have today as 5/6 instead of 05/06/08. Money values also cannot be dependent upon consistent lengths. Thus, even though every 6 digit PN can be consistent, that's only for one of dozens of other entries which is my original point. The users would have to memorize those that requre enter and those that don't. Plus, how can you cause the errant enter for the answering following the INPUT PN,6 to NOT welcome the enter alone. OR what if enter alone were a valid choice but not the intended choice. It's hard to compare the savings of keystrokes to the 'back-up' concepts of wrong following answers. So in this divided topic, I choose to always require a enter even if it's a Y/N answer. Respectfully, Mark Johnson - Original Message - From: Brutzman, Bill [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Friday, May 02, 2008 10:07 AM Subject: RE: [U2] Press any k We have 6-digit part numbers here. With input PN, 6... I have single-handedly saved the company millions of keystrokes per year. Also... it is not inconsistent if it is used all over the place. Q: Are we not men? A: We are the DevoTees. -Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of MAJ Programming Sent: Thursday, May 01, 2008 7:53 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Press any key to continue... IMHO I find the mixed use of INPUT statements with some not requiring an enter keystroke while most requiring the enter to be incredibly distracting. I've long heard the argument that saving the user the single pathetic keystroke has value but not when things go wrong. In the big picture it's a function of who is programming whom. While it can be argued that some Y/N questions don't require the enter, it creates an inconsistent interface, removing the opportunity should they press Y when they wanted N. I've seen 3, 4 and even date answers of the form INPUT ANS,8: where the enter is implied upon the entry of the 8th character. Then the enter answer could accidentally apply to the next question and then more inconsistency ensues. Just an opinion, Mark Johnson - Original Message - From: Brutzman, Bill [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, April 30, 2008 10:50 AM Subject: RE: [U2] Press any key to continue... On a lot of screens here , I force end-users to type 'x' to exit (per the following code) so that they do not bypass an error message screen. I also use square brackets [#] on a single-character prompts and triangular brackets on multi-character prompts # so that end-users know what to expect. --Bill * Error.Prompt: crt @(-1) crt @(10,10) : ' Descriptive Error Message ' : crt @(10,11) : ' [X] : input Ans.Error, 1 Ans.Error = upcase(Ans.Error) begin case case Ans.Error = 'X' ; null case 1; call *BEEP.BEEP.AND.SLEEP.R0 ; go Error.Prompt end case return to Main.Screen *- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Press any k
It is handled via the prompts... using [square] brackets for standard numbers of digits and triangular brackets for variable length entries. For most users, this takes approx one day to get acclimated. InCorrect entries lead to an error screen with a Beep.Beep.And.Sleep. In all, this method is a fast way to validate entered data. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of MAJ Programming Sent: Tuesday, May 06, 2008 2:00 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Press any k That's the trouble. It CANNOT be used 'all over the place'. Surely you have names and addresses who's lengths are often not their maximum. Even dates can have today as 5/6 instead of 05/06/08. Money values also cannot be dependent upon consistent lengths. Thus, even though every 6 digit PN can be consistent, that's only for one of dozens of other entries which is my original point. The users would have to memorize those that requre enter and those that don't. Plus, how can you cause the errant enter for the answering following the INPUT PN,6 to NOT welcome the enter alone. OR what if enter alone were a valid choice but not the intended choice. It's hard to compare the savings of keystrokes to the 'back-up' concepts of wrong following answers. So in this divided topic, I choose to always require a enter even if it's a Y/N answer. Respectfully, Mark Johnson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Press any k
If your environment has promoted a consistent interface across all programs,
then congratulations on the {} and prompting.
Unfortunately within all of my client's systems, there rarely appears a
consistent interface, thus my perspective on this topic. Even within one set
of programs from the same menu, some prompts for Enter Company use the
automatic enter and some do not. Oddly enough, this example does a R%3
to the answer so even if it is INPUT A,3 then the users either type
1enter or END without. Doesn't paint a good picture.
Also, part of my perspective is that virtually all of my client's systems
are a strong mix of procs and programs and procs don't support the automatic
enter (at least I haven't seen it). So that's another inconsistency that I
deal with.
Thanks
Mark Johnson
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, May 06, 2008 10:15 AM
Subject: RE: [U2] Press any k
It is handled via the prompts... using [square] brackets for standard
numbers of digits and triangular brackets for variable length entries.
For most users, this takes approx one day to get acclimated.
InCorrect entries lead to an error screen with a Beep.Beep.And.Sleep.
In all, this method is a fast way to validate entered data.
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of MAJ Programming
Sent: Tuesday, May 06, 2008 2:00 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Press any k
That's the trouble. It CANNOT be used 'all over the place'. Surely you
have
names and addresses who's lengths are often not their maximum. Even dates
can have today as 5/6 instead of 05/06/08. Money values also cannot be
dependent upon consistent lengths.
Thus, even though every 6 digit PN can be consistent, that's only for one
of
dozens of other entries which is my original point. The users would have
to
memorize those that requre enter and those that don't. Plus, how can you
cause the errant enter for the answering following the INPUT PN,6 to NOT
welcome the enter alone. OR what if enter alone were a valid choice
but
not the intended choice.
It's hard to compare the savings of keystrokes to the 'back-up' concepts
of
wrong following answers.
So in this divided topic, I choose to always require a enter even if
it's
a Y/N answer.
Respectfully,
Mark Johnson
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Press any k
We have 6-digit part numbers here. With input PN, 6... I have single-handedly saved the company millions of keystrokes per year. Also... it is not inconsistent if it is used all over the place. Q: Are we not men? A: We are the DevoTees. -Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of MAJ Programming Sent: Thursday, May 01, 2008 7:53 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Press any key to continue... IMHO I find the mixed use of INPUT statements with some not requiring an enter keystroke while most requiring the enter to be incredibly distracting. I've long heard the argument that saving the user the single pathetic keystroke has value but not when things go wrong. In the big picture it's a function of who is programming whom. While it can be argued that some Y/N questions don't require the enter, it creates an inconsistent interface, removing the opportunity should they press Y when they wanted N. I've seen 3, 4 and even date answers of the form INPUT ANS,8: where the enter is implied upon the entry of the 8th character. Then the enter answer could accidentally apply to the next question and then more inconsistency ensues. Just an opinion, Mark Johnson - Original Message - From: Brutzman, Bill [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, April 30, 2008 10:50 AM Subject: RE: [U2] Press any key to continue... On a lot of screens here , I force end-users to type 'x' to exit (per the following code) so that they do not bypass an error message screen. I also use square brackets [#] on a single-character prompts and triangular brackets on multi-character prompts # so that end-users know what to expect. --Bill * Error.Prompt: crt @(-1) crt @(10,10) : ' Descriptive Error Message ' : crt @(10,11) : ' [X] : input Ans.Error, 1 Ans.Error = upcase(Ans.Error) begin case case Ans.Error = 'X' ; null case 1; call *BEEP.BEEP.AND.SLEEP.R0 ; go Error.Prompt end case return to Main.Screen *- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
