You can use programming to force the value.

Something like:
If MyCheckbox <> 1
{
       MyCheckbox = 0
}

Steve,

The secret to resizing a check box is to make the height and width the same. You can make them as large as you want.

Quote:


I answered as I did because you described having trouble making the checkbox itself larger and said the users had too small a target. I wanted you to know that you can indeed make the checkbox area itself as large as you wish by resizing the element equally. Doing so will require less precision on the part of the user. Rather than us making a "live" area around the box that, in effect, makes the box pretend to be larger than it is, you can make the box itself actually larger. I would think that an actually larger box would be more predictable than a box which invisibly pretends to be larger, especially if they are placed close together.

The checkboxes in HTML and in many other programs cannot be reliably resized (ususally they can't be resized at all), therefore, they have to do tricks like you describe to make up for their inability to be made larger. Sesame's checkboxes can actually be made as large as you wish, so there should be no need for such tricks. 

In addition, the "solid, predictable" behavior you mention is entirely browser dependent. Checkboxes may behave as you describe in IE, but they do not have that extra "live" zone in Netscape.

You can just drag any of the 4 corners and resize the checkbox.  Or as suggested earlier, you can change the width and height to the same size, then drag corner to make it easy to resize to a user friendly size. 

Default checkbox is WxH = 20x18. 

If my normal fields' H=18, I have found that changing the checkbox to 30x30 gives a reasonable size for the user.  These WxH values can be changed in the Property Editor, Tab for Look/Position.

I tried Erika's suggestion to Beagle to make my check boxes '2 state' but didnt have any luck. My program reads:

If ThisElement <> 1 then ThisElement = 0 in both Element Change and Element Immediate Change. No results.

Also tried the same thing using the actual element name, but still no results.

Maybe check boxes dont trigger Element change events?

Any thoughts?

Shall I wait for 1.0.5 before posting any more issues I'm bumping into?

Thanks,
Steve

Thanks Beagle.

However, putting the program into 'On Exit' isn't going to work for me. I have a form with 50+ check boxes and the user needs to select 10 or so for each of the 3000+ records. Use of the mouse is critical to this form.

Sesame should be able to handle this just fine provided the mentioned program can fire from "on element immediate change".

I suspect its a bug and hopefully ver 1.0.5 will be the cure.

Thanks for your feedback.

Steve