When I use DateTimeInput , edit of EndTime, How to set it None?
I have to add a button , set value=None.
Is there any other function or property by it self?
- Configure Events ... on the button. (You know this.)
- Use onActionPerformed instead of onClick. onClick events always fire - even if the button is disabled. onActionPerformed events only fire if the button is enabled.
- Script. (You know this.)
- Use the Browse Properties button to find the path to the date picker.
- The chosen path.
self.getSibling("DateTimeInput").props.value = None
You can also use Component Message Handlers | Ignition User Manual if the path is complicated. It avoids all the getSibling / getChild path complexity.
Thank you!
I want to know is there other idea in [DateTimeInput],
not need to add a button?
The sensible thing to do is clear the date on view startup.
You could also clear the date after the user presses the Submit button.
I already read endDT from mysql.
This window is Edit .
I want to clear this EndDate.
But I find no way to clear this EndDate by it self.
So I need to add a button to clear.
In the Submit button I can't know the customer's clear or change demand.
My Question is there other way to clear this EndDate by it self, not add a button?
So, you want the Edit form to open with EndDate = None?
set EndDate =None or edit it to the Selected Date.
Can you modify your SQL to return the None?
SELECT
...,
NULL AS EndTime,
....
Let customer edit it.
Not read it from Mysql.
Sorry, I don't understand what the user is supposed to see or do.
Just use a button.
I realize this is a very old thread, but I’m running into somewhat of a similar issue and I don’t think this is an unreasonable request.
The main culprit is that the DateTimeInput component does not have a built-in clear button; once a date is set (by a binding or by manually setting it) it cannot be unset by the user unless you specifically script an additional button to perform that action. And yet, null is a perfectly valid input for the component, since it also has a placeholder property that is utilized when the value is null. This puts a burden on the developer, who has to go out of their way to add a workaround for something that should work out of the box.
I think this is what one might realistically expect:
This is a good idea. You should make a formal feature request at the Ideas Portal. I'll vote for it. (Put reference links here and there.)
I will also vote for this.