On Tue, Nov 6, 2012 at 3:30 AM, Harald Oehlmann
<[email protected]> wrote:
> Am 06.11.2012 09:48, schrieb Jeff Lawson:
>> I have verified that it now seems fixed for textareas with your
>> change. I will try to confirm with my colleague about his purported
>> failure with checkboxes and construct an example if needed.
>
> Thank you, Jeff.
>
> The reason for this change was to correctly interpret list and values to
> avoid a malfunction or crash, if the user enteres something, which is
> not a list.
>
Here is another example that demonstrates the difference in checkbox
behavior... In form 1.0, there are several checkboxes selected by
default, but on form 2.0 none of them are. Note that -value is not
specified for the checkboxes, but any "true" value was accepted as
signalled a checked state under form 1.0
package require form 1.0
set response(comnav_O) t
set response(comnav_L) t
set response(comnav_D) t
set response(comnav_G) t
set response(comnav_R) t
form myform -defaults response -method post
myform start
puts "<table><tr>"
foreach key {V O L D G R W H I J} {
puts "<td>"
myform checkbox comnav_$key -id comnav_$key
puts "<label for=\"comnav_$key\">$key</label>"
puts "</td>"
}
puts "</tr></table>"
myform submit save_tps -value "Save Report"
myform end
myform destroy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
