--
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
To post to this group, send email to jfxtra...@googlegroups.com.
Visit this group at http://groups.google.com/group/jfxtras-users.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "JFXtras Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jfxtras-users/mtswO-JW9xE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jfxtras-user...@googlegroups.com.
Give it a try (r2-SNAPSHOT)
On 2014-5-14 16:23, Jay Moss wrote:
That makes sense, if the your field requires a value and it doesn't get one it's an error. Â I think behavior in that situation would be up to the app to deal with - the 'today' value might make sense in some cases, but I wouldn't expect the control to operate that way by default.
So, looking at the code (I have 8.0-r1) it looks like you have a TODO for this idea already. Â
Is there a way to set the CalendarPicker allowNull property from the CalendarTextField?
-jay
On Wednesday, May 14, 2014, tbeernot <tbee...@gmail.com> wrote:
CalendarPicker in fact already has such a "allowNull" property, which disabled the unselect behavior. The question is what this would mean in context of the CalendarTextField.
If CalendarTextField would have an allowNull set to false, what would happen if the user would clear the textfield? In order not to force any specific behavior (like inserting "today" or showing an error popup), I would handle an empty text field with "allowNull" set to false as a parse error and call the parseErrorCallback.
Tom
On 2014-5-14 15:55, Jay Moss wrote:
Interesting, that makes sense. Â Offhand, I can't think of a better way to set a null value, especially if there's no text field visible. Â
But, in my situation I never want a null value set for the field, in fact I'd prefer to specifically prohibit that. Â So maybe the answer could be to add a boolean property "allow nulls" or some such - if true just keep the current behavior. Â If false, keep the previously selected (re-selected) value. Â That should work whether the text field is shown or not.
On Tuesday, May 13, 2014, tbeernot <tbee...@gmail.com> wrote:
Interesting, it is not a bug, it is the expected behavior, but maybe the behavior is not what a user feels is logical... For me it makes sense.
What you are describing is the way to set a null value without using the keyboard. If CalendarPicker is used stand alone there is no way of erasing the date (because there is no textfield to clear), so the behavior is that if a selected data is clicked, then it is unselected thus resulting no selected dates (which equals null).
When used in the popup of CalendarTextField it must be able to show "null", after all the textfield may be empty. So no dates selected correctly indicates "null", the question is: given a textfield with a date, how would you set that to null using the popup?
I decided to use the same behavior for both stand alone and popup.
Regards, Tom
On 2014-5-14 0:44, CosMoss wrote:
I'm using CalendarTextField in a Java 8 app and I've noticed what I think is a bug.Â
In my app I set an initial date - that works fine. If I 'pop' the calendar and selec
--
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
To post to this group, send email to jfxtra...@googlegroups.com.
Visit this group at http://groups.google.com/group/jfxtras-users.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
To post to this group, send email to jfxtra...@googlegroups.com.
Visit this group at http://groups.google.com/group/jfxtras-users.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
To post to this group, send email to jfxtra...@googlegroups.com.
Visit this group at http://groups.google.com/group/jfxtras-users.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "JFXtras Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-user...@googlegroups.com.