On Fri, 31 Jul 2009, Martin Wittemann wrote:
> Hello,
>
> you are right. A better message could be reasonable here. I changed
> the warning to:
> Wrong data type detected. setValue is used with Dates now.
Much clearer, thanks!
> If you still want to use the online version of the API-Viewer (as I
Hello,
you are right. A better message could be reasonable here. I changed
the warning to:
Wrong data type detected. setValue is used with Dates now.
If you still want to use the online version of the API-Viewer (as I do
sometimes), take the devel version of it. This one will be updated
eve
Hello Martin
I just updated to rev 19730 and got yet another warning message. However, I
looked at the source (as Tobi, our local Qooxdoo-Yedi suggested) and found
the problem:
qx.ui.from.DateField.setValue() expects a Date object as argument and not
String (as the API says).
I suggest that the
Hello Fritz,
I just gave your code a try in the trunk and in a checkout from your
given date. In both cases, I don't get a deprecation warning using
setValue on the date field. The setDate method is deprecated so its ok
to get a warning there.
That both ways are working like expected is good
Hello,
I am using a DateField widget with a svn checkout from July 29th 2009:
var dateField = new qx.ui.form.DateField();
var format = new qx.util.format.DateFormat("dd.MM.");
dateField.setDateFormat(format);
So far, so good. Then when trying to set the textfield:
