You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of expected behavior and the observed behavior
Let's say we have a DatetimePicker, and a button "Click". We change the date time value, then directly click on the button. In the callback of the button, the selected value is not updated properly. It still shows the time before the latest selection.
It works OK if I first change the date time, click outside to close the pop up, and finally click on the button.
Complete, minimal, self-contained example code that reproduces the issue
After reading through your description a second time. I think the problem comes down to timing. The DatetimePicker updates on the close of the pop-up calendar, and when you click directly on the button, it doesn't have time to sync with the python side.
Nonetheless, I think #3990 will improve the experience.
Yeah, this is an unfortunate consequence of the fact that events (like a button click) are handled immediately while model change events (like the value change of the DatetimePicker) are slightly throttled. Not sure I have a good suggestion for a fix.
Description of expected behavior and the observed behavior
Let's say we have a DatetimePicker, and a button "Click". We change the date time value, then directly click on the button. In the callback of the button, the selected value is not updated properly. It still shows the time before the latest selection.
It works OK if I first change the date time, click outside to close the pop up, and finally click on the button.
Complete, minimal, self-contained example code that reproduces the issue
The text was updated successfully, but these errors were encountered: