tim@hoptoad.uucp (Tim Maroney) (05/03/90)
A word about all the calls for using opaque buttons in the card layer to hide unwanted background buttons for a particular card -- this only works against a flat white background, and flat white backgrounds are usually pretty unattractive. Some shade of gray is usually greatly preferable. So stick with the openCard and closeCard handlers. And do use lock screen while hiding or showing more than one button, so they'll pop up in a synchronized way. -- Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com If you vote for clowns, you have no right to complain that only clowns make it to the ballot.
DN5@psuvm.psu.edu (05/03/90)
In article <11296@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) says: >A word about all the calls for using opaque buttons in the card layer >to hide unwanted background buttons for a particular card -- this only >works against a flat white background, and flat white backgrounds are >usually pretty unattractive. Some shade of gray is usually greatly >preferable. So stick with the openCard and closeCard handlers. And do >use lock screen while hiding or showing more than one button, so >they'll pop up in a synchronized way. While this method works, I prefer to put a card button over the background button, however, if I have a graphic, I paint over the background button AND use a transparent card button to ignore the mouse clicks. I find this solution better than having openCard and closeCard handlers to hide and show background buttons. To me it seems more intuitive. Depending upon the size of the graphic needed to cover up the button, the hide/show solution may be more memory efficient, however. ()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()() D. Jay Newman ! Do not throw your butts in Learning Technologies Group ! the urinal, for they are dn5@psuvm.psu.edu ! subtle and quick to anger.