DateField should zero fields that are not part of the resolution

[romain.wilbert]

A DateField with resolution DAY should have hour/minutes/seconds/milliseconds automatically set to 0. With resolution month, DAY should also be reset. The current behavior is most troublesome when initializing a date field (resolution day) with a null value as this causes the date field to use the current hour/minute/second.

[Matti Tahvonen]

cant' do this in 6.5, might change existing apps.

[Marko Gronroos]

Might not be desirable. It's always possible to truncate the time to the DateField resolution in the user code, but not de-truncate an automatically truncated value.

For example, if you create a custom date+time selector by compositing a DateField with day resolution and a custom time selection component, changing the date should not set the time to 00:00.

[auke]

Replying to Marko Gronroos:

Might not be desirable. It's always possible to truncate the time to the DateField resolution in the user code, but not de-truncate an automatically truncated value.

For example, if you create a custom date+time selector by compositing a DateField with day resolution and a custom time selection component, changing the date should not set the time to 00:00.

In which case it is still desireable, since you've created two components the combined field is responsible for setting the correct time (from the custom time component) on the java.util.Date. So the DateField still only needs to give back the truncated date.

[Artur Signell]

I don't see the reason for not zeroing it but doing it to 7.0 as it might break apps.

[Artur Signell]

Ended up only zeroing only the unused parts when there is no value for now, i.e. when doing new DateField() and not setting a value. Will need to reconsider still if setValue(Date date) should remove parts that are outside the scope of the resolution. It could be unwanted if you are using time zones and/or showing only the d/m/y part of a Date. Maybe it should be an option.