This month we offer some tips for BASIC programmers, a little insight on a little-known CP/M feature and a valuable collection of handy 1351 mouse tips & tricks.
1. DISPOSING NEXT
FOR/NEXT loops have only one drawback: there is no way to abort a loop in progress without leaving it "hanging." BASIC 7.0 on the C128 uses an EXIT command as a way out for DO/LOOP but no such command exists for FOR/NEXT. But by its very nature, the FOR/NEXT loop is easy to abort. Just set the index variable equal to the end-of-loop value and use a single NEXT command to close the loop. In English, that translates to "make the computer stop counting by telling it it's done counting." It works rather well and looks something like this:
10 FOR X = 1 TO 10000
20 PRINT X
30 GET X$
40 IF X$<>"" THEN X=10000 : NEXT : PRINT "ABORTED FOR/NEXT LOOP!": END
50 NEXT : PRINT "LOOP COMPLETE"
Keyboard input is checked in line 40. If the user presses any key, the loop will be terminated. The "X=10000 : NEXT" works like an imaginary "DISPOSE NEXT" command. The loop is immediately stopped.
2. CP/M'S BUILT-IN "KEYFIG"
There is a utility program on the CP/M 3.0 boot disk called KEYFIG. This nifty program lets you redefine any key on the C128 keyboard to whatever you like: strings of text, control characters, color changes, etc. It is a little known fact that CP/M 3.0 has a built-in KEYFIG feature that can be used whenever you see the disk drive letter prompt. Detailed instructions on how to use it can be called up by inserting the CP/M boot disk and typing "HELP KEYFIG FOR{$e4}EXPERTS" at the system prompt. The underline character is generated by pressing the back-arrow key just below ESC.
The built-in KEYFIG feature allows editing in either string format or hexadecimal. Keys that may be edited as strings are HELP and the eight function keys. Strangely enough, the RUN key cannot be redefined with a string as in 128-mode.
The following keys must be pressed in order to enter either of the two editing modes prior to selecting a key to edit:
String edit mode:
CONTROL + RIGHT SHIFT + RIGHT ARROW
Hexadecimal edit mode:
CONTROL + RIGHT SHIFT + LEFT ARROW
Hexadecimal mode is for changing the character codes generated from the C128 keyboard. Any key which generates a character or control code may be edited in this fashion.
String edit mode is for the function keys and HELP. In string edit mode there are ways to insert and delete text and move the cursor left and right. The methods used are rather clumsy but do work...
Move cursor left:
CONTROL + RIGHT SHIFT + LEFT ARROW
Move cursor right:
CONTROL + RIGHT SHIFT + RIGHT ARROW
Insert spaces for text:
CONTROL + RIGHT SHIFT + PLUS KEY
Delete characters:
CONTROL + RIGHT SHIFT + MINUS KEY
Accept string & return to CP/M prompt:
CONTROL + RIGHT SHIFT + RETURN
3. IT'S NOTHING, REALLY
Commodore 128 BASIC handles null strings a little better than C64 BASIC. Using the ASC() function on an empty string in C64 BASIC will result in an ?ILLEGAL QUANTITY ERROR while C128 BASIC returns a value of 0.
The difference between a null string and an empty string is not often clearly understood. A null string has a valid character value of zero (as in X$=CHR$(0), for example) while an empty string contains NO characters (X$="").
When retrieving single bytes of data from a disk file using GET# in C64 BASIC, it is necessary to use a special technique in case any zero-byte characters are retrieved. Because of the way GET# works, zero-byte characters are inputted as empty strings, not CHR$(0)'s. Line 40 in the following program demonstrates one way to handle empty strings:
%c10 OPEN 2,8,2, "0:FILENAME,P,R"
%c20 FOR X = 1 TO 254
%c30 GET#2, X$
%c40 PRINT ASC( X$ + CHR$(0) )
%c50 NEXT
%c60 CLOSE 2
With C128 BASIC, the "+CHR$(0)" in line 40 is not needed because of BASIC 7.0's improved ASC() function. Alternate ways of trapping empty strings are:
%c1) X$=X$+CHR$(0)
%c2) IF X$="" THEN X$=CHR$(0)
4. OF MICE AND MEN
Unlike a joystick, Commodore's 1351 proportional mouse is very difficult to program unless you are a machine language expert. Realizing that most of us mere humans would have no idea how to use the mouse in our own programs, Commodore provided a useful demo disk with the device. In true Commodore tradition, though, details on using the mouse are still rather sketchy. Here are some tips on how to use the mouse drivers provided on the 1351 demo disk.
First of all, let's identify the two files we are most interested in. The mouse driver designed for use in 64-mode is called "M1351.64.BIN" and loads into memory location 49152 ($C000). The 128-mode version is called "M1351.128.BIN" and loads into location 6144 ($1800).
The beauty of these particular mouse drivers is that they can support either control port. Both drivers use sprite #0. The other seven are undisturbed.
There are a few drawbacks. The biggest is that there are no programmable boundaries for the moving sprite. It can be moved completely off-screen; it will even "wrap" around to the other side! Another drawback is that while the driver is installed, things slow down ever-so-slightly. This is more noticable on the C128.
Finally, there is no "joystick driver" supplied for performing the same sprite-moving activities as the mouse. If you want your program to offer a choice to the user in case he/she has no mouse, the routine will have to be written from scratch. Commodore has provided source code for both drivers on the demo disk, however, and this can be built upon. The C64 version is saved as "M1351.64.SRC" and the C128 version is called "M1351.128.SRC". Both are SEQ files and, unfortunately, are not compatible with some assemblers.
To activate the C64 mouse driver, first load it into memory. In a BASIC program, this can be done like this:
%c10 IF X=0 THEN X=1 : LOAD"M1351.64.BIN",8,1
Next, we have to install the mouse driver. The program hooks into your computer's regular interrupt schedule, which is performed 60 times per second. So in addition to normal housekeeping tasks, your C64 will also update the position of sprite #0 based on coordinates received from the mouse. This scheme allows BASIC programs and other routines to run at the same time as the mouse driver. In a very general sense, your computer will be "multitasking."
The mouse driver wedge has two "kick start" SYS addresses that correspond to each of the two control ports. You may use either one, although port #2 is recommended because port #1 often interferes with the keyboard. This is also true on the C128.
To install the mouse driver in control port #1 use:
%cSYS 49152
To install the mouse driver in control port #2 use:
%cSYS 49155
Once installed, the only way to switch ports is to use the disable feature. Here it is:
%cSYS 49158
This shuts off the mouse driver, leaving sprite #0 hanging motionless on the screen. When the mouse driver is disabled, it can be restarted again with either of the two SYS enable commands.
The mouse driver does NOT automatically turn on sprite #0. This must be done by your program. Use this command to turn on sprite #0 without affecting the others:
%cPOKE 53269, PEEK (53269) OR 1
Conversely, to turn off sprite #0 without affecting the others use:
%cPOKE 53269, PEEK (53269) AND 254
In 128-mode, things are only slightly different. In a BASIC program, load the mouse driver file into BANK 0 memory with this command:
%c10 BLOAD "M1351.128.BIN",B0
Once loaded, the driver may be installed in one of two ways.
To install the mouse driver in control port #1 use:
%cSYS 6144
To install the mouse driver in control port #2 use:
%cSYS 6147
To disable the mouse driver use:
%cSYS 6150
Like its C64 counterpart, the C128 mouse driver does not turn on sprite #0 when installed. Turn on sprite #0 with this command:
%cSPRITE 1,1
(Refer to your C128 user's manual for more information on the SPRITE command and its parameters.)
To turn off sprite #0, use:
%cSPRITE 1,0
5. OF MICE AND MEN II: THE SEQUEL
Having a mouse-driven sprite skating around the screen is nice but how do we actually USE it? Good question.
"Point-and-click" is one of the simplest user interfaces ever devised, yet writing such a program requires a great deal of effort. What the end-user gains in ease-of-use is paid for by the time and efforts of the programmer who must write the elaborate code to support it.
In BASIC, it is not as difficult as you may imagine to detect a mouse-click and branch when a specific area of the screen has been clicked on. In fact, you could do it like this: (for control port #1)
%c10 WAIT 56321,16,16
Or... (control port #2)
%c10 WAIT 56320,16,16
Using either of these two lines causes BASIC to wait for a fire-button press at the appropriate control port. On the 1351 mouse, a fire button value corresponds to the left input button. (The C128 should be in BANK 15 for these commands to work.)
Conversely, the right input button on the 1351 mouse can be detected as an "up" joystick value. Use this line to WAIT for a right input button press, substituting 56321 or 56320 for "control port":
%c10 WAIT control port,1,1
Both input buttons can be checked at the same time with these commands:
%c10 WAIT control port,17,17 : X=PEEK (control port) AND 17
This technique will yield one of four possible values in variable X after an input button is pressed:
%c17 = no button pressed *
%c1 = left button
%c16 = right button
%c0 = both buttons
* A value of 17 may occasionally slip through if the user quickly taps the mouse button. What happens is that the WAIT statement is executed but because BASIC is so slow, the button is released before the "X=PEEK (control port) AND 17" command can get the proper control port value.
After the button click, it is necessary to get the coordinates of sprite #0. Use a line like this:
%c20 X=PEEK(53248)+ 256*(PEEK(53264) AND 1) : Y= PEEK (53249)
Now let's say we have something on the screen such as an OK box. Picture it as a solid box made out of reversed characters and having the word "OK" in the middle. For us to determine if the sprite coordinates are within this box, we have to figure out the coordinates for the upper-left and lower-right corners. Let's assume that these X,Y coordinates are 112,154 and 175,177. The following line will tell us if the sprite coordinates are within our OK box:
BOX COORDINATES: 112,154 175,177
30 Z=(X>111)+(Y>153)+(X<176)+(Y<178)
35 IF Z=-4 THEN sprite is within the
boundaries of our
OK box!
40 GOTO 10:REM loop back to WAIT routine
There may be instances where keyboard input is expected as well as an input button click. In this case we must run a continuous loop that checks for both. Try this, substituting 56320 or 56321 for "control port":
10 GET X$
12 X=PEEK(control port) AND 16
13 IF X$="" AND X=16 THEN 10
To check what kind of input was used try:
20 IF X=0 THEN mouse click routine
30 IF X$<>"" THEN keypress routine
40 GOTO 10
That wraps it up for this issue. If you have any tips or tricks for performing simple yet useful procedures with your C64 or C128, send them in to:
%cJon Perregaux
%cCommodore Tips & Tricks
%cc/o UpTime Magazine
%c6 John Clarke Road
%cMiddletown, RI 02840
We are looking for tips and tricks that deal in the following subjects:
* POKEs and PEEKs for both the Commodore 64 and 128
* Undocumented features you may have discovered
* Using GEOS on both the 64 and 128
* CP/M Plus on the 128
* The 1541, 1571, and 1581 disk drives
* Important hints about major applications software
