Better radio buttons & checkboxes

[LaRetta]

I've found a radio button graphic I would like to use (Buttons & Things site). One is selected, the other isn't. I've tried stacking them, but can't figure out how to use them with an existing value list and how to make the 'selected' graphic display while it's unselected counterpart not. My test is simple - Y, N (auto-enter being no). Is there a way to use these cool buttons? I also found great checkboxes ... same issue ... assigning them to a value list and making them display properly. Can someone point me in the right direction?

[Vaughan]

You'd have to forget using real checkboxes.

Put the images inside container fields (perhaps a repeating global field) and display the appropriate image depending on whether the field contains the value. this will require some fancy calculations. Value changing (toggling the checkbox on and off) will need to be handled by scripts... in other words, it's not a simple job.

[LaRetta]

Thank you. I have a graphics db with containers for graphics. I would need two repeating fields to hold each selection (unchecked & checked) and then a script to 'flag' according to the value? Would I place the value field over the button?

[Vaughan]

I don't know, I've never done it!

The actual field itself need not be displayed on the layout, just a bit of text next to the calculation field that displays the "checkbox" image is sufficient. Clicking on the checkbox image or the text should run a script that toggles the field value and switches the image.

[LaRetta]

Oh, that makes sense! No need to show the field at all! I'm going to figure it out somehow!

[CobaltSky]

Hi LaRetta,

One of the password-free demo files on my site shows graphical radio buttons in action. If you'd like to take a look, it is at:

http://www.nightwing.com.au/FileMaker/demos/AutoListSelect.zip

The demo is mainly concerned with other stuff, but it uses the radio buttons as part of its interface.

Using the technique that Vaughan describes, the resulting checkboxes/Radio buttons are mouse-driven only.

If you want them to also be able to be controlled from the keyboard in the normal way, you should create a corresponding 'normal' checkbox or radio button field, palce it on the layout, include it in the tab order (exclude the calculating container fields), make its fill and borders transparent and then use the 'Object Size' dialog to make it 1px high.

If you then position it along a border of your checkbox or radio-button-group, it will provide a subtle field 'highlight' when tabbed to, and the keyboard will activate the field in the normal way. That way your left brain and right brain can both be happy at once!

[LaRetta]

I'm tickled! I downloaded everything from your website last night but it was too late to look with them! Thank you.

BTW, I don't particularly like the idea of a radio button being activated by tabs particularly on heavy data-entry screens ... I've seen too many radios inadvertently activated by users zooming through them. My pet peev are designs which use radio buttons with two selections that, once clicked, you can't de-select your selection. Ever had that happen? User selects, then decides they shouldn't have made ANY selection at that time, and can't 'remove' their choice. I noticed FM is no exception. Once selected, a radio can't be undone. How do you address this pesky issue? I've always had a third button (no selection) but I'm not happy with it.

[CobaltSky]

In FM, if you tab to a radio button field and press the backspace/delete key it will delete all selections leaving the field empty.

But users have to know this - otherwise, as you say, you have to provide them with an option for 'none' or 'nil' or 'not applicable' (or whatever...) as one of the button values...

Other approaches include having a modifier key which you hold while clicking to clear instead of setting the field, or a 'clear' button next to the field (attached to a script which sets the field to null).

[ldebondt]

Shift + "LeftClick" will also clear a radio button so that no entry has been made.

[LaRetta]

Thanks for the info! Hmmm, I'm not sure whether it's better to put 'clearing instructions' by a radio button or just another 'de-select button. Well, if I wait until a user tells me they inadvertently clicked one, it'll be a long wait! I've been there. You feel iritated, click back and forth and then just forget it, feeling embarrased that you selected something that you were unsure of and shouldn't have selected.

I'm excited about Ray's buttons -- they sure are an improvement!