|Column Tag:||Basic School
Color Mixer Creates Custom Colors
By Dave Kelly, MadTutor Editorial Board, Ontario, California
ZBasic Does Mac II Color!
Yes, thats right! The new ZBasic version 4.01 now supports the Mac IIs full 256 colors. There is no need to restrict yourself to the 8 colors of the old Quickdraw.
To use the 256 color mode, ZBasic now provides a LONG COLOR statement. The syntax is: LONG COLOR blue%, green%, red%, [ background]. LONG COLOR is used to set the colors and grey levels for subsequent graphic commands used on the Macintosh II. The command is ignored by other Macs.
The values of blue%, green% and red% may range from 0 to 65535. They may also be represented as long integers (65535 as a long integer is -32767 as a regular integer). The colors are used in RGBColor calls to the Mac II ROM where 0 is the darkest and 65535 is the lightest.
The background variable is used as a flag to indicate if the color should be set in the foreground or in the background. A background value of 0 causes the background color to be set to the blue%, green%, red% color indicated. Subsequent LONG COLOR statements that have no background variable or background is set to other than 0 will set the foreground color. The background color will be used the next time it is needed, when the screen gets updated or is cleared with CLS.
Inside Macintosh Volume V has the new color information we need to understand how the Mac II gets its color and how to use color in your applications. Before using color you should read the User Interface chapter of Inside Macintosh Vol. V. One of the most important thing you should try do is leave the selection and choices of color in the hands of the user. The study of color and how it affects people is not well defined. One of my co-workers is color-blind and has a totally different way of looking at color than I do. If color is not used carefully it could hinder instead of help to enhance your software.
Traditionally (and on that other computer) color has been used to help distinguish different things on the screen and show relationships between items on the screen. Some colors have special significance. For example: red means stop, green means go, yellow means caution. Colors can enhance in this way, however, remember that after the user has seen the same color combinations several dozen times, the color becomes commonplace and he might still make mistakes that the color was supposed to help him avoid. In fact, the bright colors used to warn a user may actually attract him to select that color.
Inside Mac encourages you to start out the design of your program in black and white and add color as a supplement to provide extra for people who have color capability. Color use should be limited to the content area of your windows. Let the user decide what color his menus, borders, controls etc. should be. The Colorizer application and CDEV let the user select his own colors for these items. If the user selects colors for somethings then your application comes along and changes part of these colors, there might be some pretty strange color combinations left over. Many suggestions are available in Inside Mac which you should know so that your applications will be consistent and wont conflict with the user interface.
Fig. 1 Mixing colors, in this case white!
The blue%, green%, and red% that you specify in the LONG COLOR is used by the Color Manager to return the pixel value that best represents that color. The Color Manager searches through the color table for the RGB color that most closely matched the desired color. Color Quickdraw then places that color on the screen. The way that each pixel is assigned a color to display is by way of the Color Look-Up Table (CLUT). The video card takes each pixel and compares it to the CLUT to determine which RGB value that pixel represents. The RGB value is split off into three separate electrical signals (red, green, and blue) to the video monitor. By the way, when red=green=blue you get shades of gray. By using the Palette Manager (if you could from Basic) you could change the drawing environment to use a different palette.
Color Selection routines have been provided to the Macintosh II by Apple via the Color Picker routines. Here is the problem: ZBasic doesnt support all the new calls for the Mac II yet. Zedcor has promised to send me format and structure information to add more calls to ZBasic as required, but Andy Gariepy has been to busy to send it to me. So that being the case I have no choice but to write my own color selection routines. Also the Color Picker is PACK_12 in system 4.2. Im not sure it would be that easy to call a PACKage from ZBasic without it being defined by the language itself. Maybe we will have to wait for Zedcor to implement it. In the mean time I have made my own quick and dirty version of a Color Picker.
If you think about it, the Apple Color Picker routine really does do a lot! It allows you to type in the red, green, blue colors, but also will adjust these colors when you set the hue, saturation, and brightness. Proper adjustment of the red, green, and blue will result in the same hues, saturation, and brightness, but it just isnt as convenient to setup.
The color wheel concept is interesting too. You can learn a lot about how colors can be mixed by watching the values of red, green, and blue while moving the mouse around the color wheel. Move more towards blue and watch how the numbers change! Amazing! The color wheel really is a good way to allow you to select colors. The only other good approach is to allow the user to pick from a color palette. The problem is how to decide which colors are defined in the palette.
My example suggests a simple way that colors could be selected by the user. By choosing the Pick Colors menu or button you are given a set of 3 scroll bars to adjust the amount of blue, green, and red. You can mix the amount of each color and see the effect of mixing each. This might even be useful for showing young children the effects of mixing colors. If you like the color then click on OK or else cancel to return to the original color setting.
The problem with my Color Selection demo is that because of the way ZBasic does event trapping it is difficult to make the routines be stand alone. My color mixer program provided here must become an integral part of the application because of the way that ZBasic automatically generates the event loop. I tried using separate ON DIALOG GOSUB traps, but it somehow didnt work. I could only get one of the ON DIALOG statements to take effect.
There are a few problems that have shown up with my early version of ZBasic 4.01. First, the scroll bars dont scroll properly when using the max and min values that are given in the ZBasic manual. If +32767 is used and you scroll to the right (or down) by clicking on the right (or down) arrow, when the bar reaches the max it will jump to the minimum! Also if you change the max value to between 32100 and 32766 and click in the scroll bar between the arrow and box, when the max is reached it also jumps down to the minimum. UGH! And if -32768 is used for the minimum the scroll bar returns a 0 when the box is set at the minimum. -32767 works fine. I am forced to adjust these values in the program, but it wont matter much because the selected color will likely be the same anyway because we only have 256 possible.
Hierarchical Menu Notes
Using Hierarchical menus isnt so simple with ZBasic. Hierarchical menus are stored as resources of the type MENU just as other menus may be stored. However, to use MENU resources with ZBasic AND have ZBasic be able to use them, you have to set up your own event loop using GETNEXTEVENT. Then you have to handle each event with the standard Macintosh way of programming and cant use ZBasics event trapping routines (they get in the way). What we need is a way to use MENU, WINDOW, CONTROLs and other resources from ZBasic which can be invoked with ZBasic statements (which are integrated in with the ZBasic automatic event loop. It would also be useful to be able to automatically install a resource into an application when ZBasic compiles as an application. Maybe Zedcor can put these things on their THINGS TO DO list for version 4.02?
A submenu is associated with a menu item by using 2 fields of the MenuInfo data structure. When the itemCmd field is set to hex $1B, the itemMark field should contain the menuID (in hex) of the associated hierarchical menu. These values can be created/modified with ResEdit 1.1B3.
By using Menu Manager calls (pg. E-181 in ZBasic manual) you can find out which menu is selected in the GETNEXTEVENT loop as you would with regular type menus. More on this in a future column.
Professor Macs ZBasic Color Mixer
By Dave Kelly
MENU 1,1,1,Select Color
EDIT MENU 2
Find out screen size.
WINDOW 1,Main Window,(10,44)-(PortRight-4,PortBottom-4)
BUTTON #7,1,Pick Color,(120,WINDOW(3)-50)-(195,
LONG COLOR blue&,green&,red&
PRINT Blue:;blue&; Red:;red&; Green:;green&;SPACE$(10)
WINDOW PICTURE #1,Pic1&
ON DIALOG GOSUB Event
ON MENU GOSUB MenuEvent
DIALOG ON:MENU ON
DIALOG STOP:MENU STOP
IF Menunumber<>1 THEN RETURN
WINDOW PICTURE #1,0
KILL PICTURE Pic1&
ColorPick:A Color Selection routine
min%=-32767:Manual says that -32768 is Min. max%=32766:Manual says
that 32767 is Max.
WINDOW 5,Color Chooser,(PortLeft+10,PortTop+30)- (PortRight-10,
SCROLL BUTTON #1,currentblue&-32767,min%,max%,100,(20,
SCROLL BUTTON #2,currentgreen&-32767, min%, max%, 100, (20, WINDOW(3)-150)-(WINDOW(2)-20,
SCROLL BUTTON #3,currentred&-32767, min%, max%, 100, (20,
GOSUB Button1:set blue
GOSUB Button2:set green
GOSUB Button3:set red
GOSUB Button4: OK button was pressed
GOSUB Button5: Cancel button was pressed
LONG COLOR currentblue&,currentgreen&,currentred&
Button1:blue scroll bar
COLOR=4:set text color to blue
Button2:green scroll bar
COLOR=2:set text color to green
Button3:red scroll bar
COLOR=6:set text color to red
FOR J=1 TO 5
BUTTON CLOSE J
WINDOW CLOSE 5
LONG COLOR blue&,green&,red&
PRINT Blue:;blue&; Red:;red&; Green:;green&;SPACE$(10)
WINDOW PICTURE #1,Pic1&
GOSUB Quit:if close box selected
At MacWorld Expo in San Francisco someone asked if we knew a way to effectively mask out the command-option keys in HyperCard. The following information was given in WINOID issue #1, a newsletter for the Apple HyperCard Users Group. I hope that this will answer your question.
How can I hide buttons from command-option key peek?
When you dont want people peeking at your buttons, it is necessary to trap the command and option keys. While there are several ways of doing this, here is one that is simple and works about 99% of the time.
The basic idea is to take the user to another card when the command and option keys are both pressed. This can be a no peeking card or a rules card or some other kind of card. When the user releases both keys, you then return to the card the user was viewing before trying to peek. Following are the two scripts that accomplish this. Put the top one in your stack script and the other in the no peeking card script.
For the stack script:
if the commandkey is down and the optionkey is down then
push this card
go card no peeking
For the no peeking card script:
if the commandkey is up and the optionkey is up then