Hello Jim,
thats a good point. I just checked our Spinner implementation to take
a look if every qooxdoo widget acts like the TextField. The Spinner
does exactly the thing you suggested. So I made a note to the current
bug (http://bugzilla.qooxdoo.org/show_bug.cgi?id=2099) concerning the
If this is intended behavior, then I would contend that it is wrong. There
is a difference between null and and empty string. Null means that there is
no value assigned, and empty string means there is a value assigned, just
that it's empty. I would say this is a bug in the design. The TextField
ne
Hello Mike,
this behavior is like we want it to be. The TextField only accepts
Strings as values. All other types will cause such an exception.
Regards,
Martin
Am 02.04.2009 um 20:04 schrieb mshillin:
>
> Calling qx.ui.form.Textfield.setValue(null)
>
> throws an exception
>
> [Exception... "
Calling qx.ui.form.Textfield.setValue(null)
throws an exception
[Exception... "'Error: Invalid value type: null' when calling method:
[nsIDOMEventListener::handleEvent]" nsresult: "0x8057001c
(NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "" data: no]
This is different from 0.7.x where setting a