Well, the actual question asks why it occurs, not really how to fix it,
So...
In Universe Basic one doesn't have to define the length of an input value,
tho' one can,
eg INPUT ANS,1
Instead it allows any length of input, so a space bar entry might just be
part of a string entered - as one
This would happen if someone replaced the BASIC command with either a
paragraph or cataloged proggie? I've been known to do this in the past -
when I wanted to know who had compiled what. If the proggie then failed to
compile, there would be nothing to run...
The VOC entry for BASIC on this site
If I could extend the question just a little ... would anyone like to share
their Standard.Input.Sub that they call from all their input screens. Its
always illuminating to see how others do it.
-Baker
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit
Allen:
I ran into a side-note recently. I've used a character-parsing loop for years
like:
****
MenuExit = 0; ** initialize menu-exit variable
DecStr = NULL$; ** initialize decimal
A cruel trick using a no-op and VOCLIB?
On 4/30/08, Baruch Salamander [EMAIL PROTECTED] wrote:
Greetings,
Did anyone ever experience the following on Universe?
BASIC BP TEST
The program didn't compile in TCL and no error messages appeared after
pressing return. The same
Check Permissions on BP (and BP.O)?
Mark
-Original Message-
Did anyone ever experience the following on Universe?
BASIC BP TEST
The program didn't compile in TCL and no error messages appeared
after
pressing return. The same occurred in multiple accounts using
multiple
You can also try ANS = KEYIN()
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Ferries
Sent: Tuesday, April 29, 2008 2:46 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Press any key to continue...
Hi All,
We were coding a standard INPUT ANS
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
You might want to look at CINPUT.SUB.B in the APP.PROGS file in the UV
account.
Roy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Baker Hughes
Sent: Wednesday, April 30, 2008 10:53 AM
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] Press any key
We had one user (a lawyer - go figure) complain, quite vigorously, that the
Shift key wouldn't be accepted as ANY key.
Colin Alfke
Calgary, Canada
-Original Message-
From: Steve Ferries
Hi All,
We were coding a standard INPUT ANS after asking a user to Press any
key to continue We
In this case, simply re-labeling the Enter key as Any would be the
best way to proceed
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Colin Alfke
Sent: Wednesday, April 30, 2008 4:13 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Press any key to
Ah. a new product line MS Keyboard, esquire
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Harbeson
Sent: Wednesday, April 30, 2008 3:50 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Press any key to continue...
In this case, simply
I think you could just get away using the IN() form of input.
CH.IN = SEQ(IN())
This is from the word processor I wrote where it returns the numeric value
of any key pressed *including* the space bar. You wouldn't need to evaluate
the response for your purpose though
hth
Allen
In message [EMAIL PROTECTED], Glen Batchelor
[EMAIL PROTECTED] writes
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of Anthony W. Youngman
Sent: Saturday, April 26, 2008 9:14 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Guaranteed
14 matches
Mail list logo
