Micro$oft can do no wrong!!!!!!!!!!!! (Hey Drew, this CODE WILL WORK!)

by Pete

But if they could, they wouldn't get that right, either. Good find Galleon.

Workaround:

 

DECLARE SUB getkey ()
DECLARE SUB showcode ()
SCREEN 0, 0, 0, 0

DIM SHARED code$(1000), display, over, k$, movedown
display = 21
over = 50
movedown = 1


DO
k$ = INKEY$ ' storing the INPUT into the variable K

getkey ' this sub gets user input and outputs it correctly
LOOP

SUB getkey


SELECT CASE k$ ' menu selection for user input (K)

CASE CHR$(0) + CHR$(77) ' USER ENTERS RIGHT

IF over < 80 THEN

over = over + 1

LOCATE movedown, over: PRINT "X"

END IF


CASE CHR$(0) + CHR$(75) ' USER ENTERS LEFT

IF over > 9 THEN
over = over - 1


LOCATE movedown, over: PRINT "X"
END IF


CASE CHR$(0) + CHR$(80) ' USER ENTERS DOWN
IF movedown < 21 THEN
movedown = movedown + 1

LOCATE movedown, over: PRINT "X"
END IF


CASE CHR$(0) + CHR$(72) ' USER ENTERS UP
IF movedown > 3 THEN

movedown = movedown - 1

PCOPY 0, 1: SCREEN 0, 0, 1, 1
LOCATE movedown, over: PRINT "X"; : ' this is the part that is broken, i think
PCOPY 1, 0: SCREEN 0, 0, 0, 0


END IF

END SELECT


END SUB

SUB showcode ' JUST IGNORE, IDKK WHAT I WANT THIS TO DO, YET
position = 1

FOR A = display - 20 TO display
position = position + 1

IF A < 10 THEN LOCATE position, 1: PRINT A; " : "
IF A > 9 AND A < 100 THEN LOCATE position, 1: PRINT A; " : ";
IF A > 99 THEN LOCATE position, 1: PRINT position; " : ";

LOCATE position, 9: PRINT code$(A)

 

NEXT A

 

END SUB

------------------------------------------

Page flipping will refresh the screen. FOR/NEXT LOOPS for multiple printing, CLS, priniting to another screen area and coming back, etc. all fail BTW.

 

Pete

 

Posted on Mar 20, 2008, 5:29 PM
from IP address 70.177.5.114

Respond to this message   

Goto Forum Home


Response TitleAuthor and Date
loll! so i found an error in microsoft.. what are the odds?drew on Mar 20
 *With Windows? I'd say about 100 to 1, your favor. on Mar 21
  * Why not look for bugs in TeX? Knuth pays $327.68/bug on Mar 21