DateItem without Time

[sachage]

Hello

Version v10.1p_2016-03-22/Pro Deployment Chrome 49.0.2623.87 m

My codes creates a DateItem with inputfields for time:



Code:


Don't want time fields. But want arrows for month and year.
How can i get a simple Datechooser? It worked with the previous version 4

[Isomorphic]

The time fields show up by default when the field is declared to be of type "datetime". This is an intentional enhancement. If you want to reverse it for some reason, use DateChooser.showTimeItem - this can be set system-wide via setDefaultProperties().

[sachage]

As you can see the field is declared as type "DateItem" and not "DateTime". The result is still with Timefields........? What can i do to hide this fields?

[Isomorphic]

Incorrect: "datetime" is a data type, "DateItem" is a subclass of FormItem. Re-read the previous post more closely - we already answered your question.

[edulid]

look in the datasource for the data type definition

[sachage]

Now i can control the "TodayButton", can "TimeItem" disable, but can not hide the timeItem with "setShowTimeItem(false). Also the navigation icon for the calendar do not appear.
I tried also to set DateItem.setType("date") but it has no effect.

DateChooser dc = new DateChooser();
dc.setShowTimeItem(false);
dc.setShowTodayButton(false);
TimeItem ti = new TimeItem();
ti.disable();
dc.setTimeItemProperties(ti);;


DateItem didatum = new DateItem("didatum");
didatum.setTitle("Datum");
didatum.setPickerProperties(dc);

[edulid]

why don't you just change the data type to "date"?

[sachage]

This is just a form to send the formvalues to the server. There is no Datasource...

I tried to change the type via DateItem.setType("date") but it had no effect..

[Isomorphic]

Your code to not show the TimeItem needs to be executed before you create any components. You also should not apply TimeItem properties, even an attempt to disable it, since you are also asking for it not to be shown at all.

As far as setType("date") not working to suppress the chooser, we are not reproducing that.

Try taking just the relevant code and running it in a new project with nothing else, and using the latest patched version. If you still have a problem there, post the complete code for the test and we can double-check on our end.