Thread: TDateTimePicker and Windows 10
 |
This question is not answered.
Helpful answers available: 2.
Correct answers available: 1.
|
|
Replies:
2
-
Last Post:
Apr 17, 2018 11:13 AM
Last Post By: Jayme Jeffman
|
|
|
Posts:
20
Registered:
3/2/98
|
|
|
Hello,
I hadn't noticed yet, but it seems that any of the Windows 10 updates has blocked the TDateTimePicker::OnUserInput event. I have defined a handler to it and when I type any numbers on TDateTimePicker interface the event is not fired.
Do someone have the same problem ?
Best regards,
Jayme Jeffman
|
|
|
Posts:
9,447
Registered:
12/23/01
|
|
Jayme Jeffman wrote:
I hadn't noticed yet, but it seems that any of the Windows 10 updates
has blocked the TDateTimePicker::OnUserInput event. I have defined a
handler to it and when I type any numbers on TDateTimePicker
interface the event is not fired.
Let's start with the simplest possibilities before we start blaiming
Microsoft or Embarcadero for breaking something:
- did you verify that the OnUserInput handler is actually assigned at
runtime?
- did you verify that the ParseInput property is set to True at runtime?
--
Remy Lebeau (TeamB) |
|
|
|
|
Posts:
20
Registered:
3/2/98
|
|
Hi Remy.
Thank you very much for answering me.
Let's start with the simplest possibilities before we start blaiming
Microsoft or Embarcadero for breaking something:
- did you verify that the OnUserInput handler is actually assigned at
runtime?
- did you verify that the ParseInput property is set to True at runtime?
--
Remy Lebeau (TeamB)
Yes, the answer to both your questions is yes.
Best regards.
Jayme Jeffman |
|
|
|
Legend
|
|
Helpful Answer
(5 pts)
|
|
Correct Answer
(10 pts)
|
|
Connect with Us