Wt

Name : wt-devel

Arch : x86_64

Version : 3.3.0

Release : 2.fc19

on the prior Wt version if I did not at least specify a null string on a WCheckbox, it would not let me setText later, so I have a bunch of

check_box = new Wt::WCheckbox(""); // need to specify a string, or setText will be refused

in the code. Now with this version (specified above), if I give WCheckbox a null string a lot of weird behavior occurs. I'm getting Wt internal errors, and extraneous default box checking. All of this goes away if I provide a non-null string to the constructor:

check_box = new Wt::WCheckbox("why?"); // need to specify a non null string or bad things happen

man, and this was not obvious, took hours to find and prove this out ... finally found it by accident when messing with the constructors