Sesame supports an Undecided state with checkboxes and radio buttons.  Is there a way to turn this off?  I'd like to be able to initialize the underlying data elements with default values and then only allow a user to select/delect a checkbox and have always at least on radio button item within a group selected.

You will want to put ^ that code into the On Element Immediate Change event of the Checkbox. That will give the checkbox the choices of Yes or Undecided.

If you want the choices of Yes or No, You will want the following code in the On Element Immediate Change event of the Checkbox

If @IsBlank(ThisElement) Then
{
	ThisElement = 1
} 

-Ray

Quote:

Thanks.  However, I can't get similar code to work (using a static variable to hold the previous value) with a Radio Button Group.  The On Element Immediate Change event is not consistently(*) triggered when a Radio Button Group is set to Null (using v2.0.3).

To test, I wrote a very simple application with a Male/Female radio button with the following code in the On Element Immediate Change event:

If @IsBlank( ThisElement ) Then
	WriteLn( "Gender is NULL" )
Else
	WriteLn( "Gender is: " + ThisElement ) 

(*) I say "consistently" because every so often the event would fire when the Radio Button Group was set to NULL.  I couldn't figure out the pattern though.

i have found the following code to work with an unbound check box to have the choice between true and false.
i believe i originally found it somewhere in the forum

in the global code:

stat cb_state as int = -1

in check box on immediate change

f cb_state = 1 then
{
     thiselement = 0
}
else
{
     thiselement = 1
}
cb_state=thiselement

If you don't want the extra static variable, this works fine for me On Element Immediate Change of an unbound checkbox.

If ThisElement <> 0
{
	ThisElement = 1
}
ForceRedraw()

 

Hello Scott,

By default a Check box will be Blank also known as the unset state. The order of toggling states is as follows

Blank(Raised Box)
On(Down Box with a Check)
Off(Down Box with no Check)

And then back again to Blank. My code says that if we reach the Blanked state go straight to the On State.
So it goes like the following starting from On

Click
Programming Runs. Nothing Happens
Off
Click
Programming Runs. Element is Blank now so Value is set to One
On
Click
Programming Runs. Nothing Happens
Off
Click
Programming Runs. Element is Blank now so Value is set to One
On
etc. etc.

So it limits it to the choices of On and Off.

Your Code says that if the value of the check box is anything other than One, clear it. So when it reaches the Off State(which comes right after On as you can see from the list above) it flips to the Blanked state. So it goes like the following starting from On


Click
Programming Runs. Element is Off which is Not equal to One so Element is Blanked
Blank
Click
Programming Runs. Nothing Happens
On
Click
Programming Runs. Element is Off which is Not equal to One so Element is Blanked
Blank
Click
Programming Runs. Nothing Happens
On

Does that help?

-Ray

I've discovered I cannot use = or /= to search check boxes, I can only toggle a state.  Checking it retrieves all those records that are checked.  Unchecking it (no) retrieves no records at all.  However, leaving it blank retrieves ALL records, both checked and unchecked.

I have decided I dislike tri-state boolean elements, as they're a pain in the a$$.

Infinity wrote on Jan 31^st, 2008 at 6:16pm:

NULLs.  You either love 'em or hate 'em.