CompuServe Messages

That was the problem, Mike. If you specified that in the instructions on the BBS, I missed it. I unpacked it into a "stacks" dir in vd0:, and ran it from there. When I read you instructions here, I un-assigned Ultra: from my dh0:UltraCard dir, and reassigned it to vd0:. Worked like a charm. (Nice job, too). Since I have your ear (eye, whatever), maybe you can help me with a stack I'm working on. I have 12 buttons, the twelve tones of the European scale. I'm "highlighting" them by putting a similar button, but with different colors, on top, and making it invisible. When you click on the visible button, it "set visible [invisible button] true", and when you click on that one, it does the opposite. Works great. However, since only ONE of these buttons should be "lit" at any time, when you click on the unhighlighted button, it should also turn off whatever is on. Right now, the only way I can get this to work is to have it first turn off ALL TWELVE, and then turn on the right one. This is slow. I'd rather save the name of the currently "on" button to a variable, and then have the program first "set visible [variable] false", and then turn itself on, passing its own name to the variable, so it will be turned off in turn when the next button is clicked. I'm sure there is a way to put the name of a gadget into a variable, and then have that variable dump it out into a command line, but I can't for the <continued>