TUnimDatePicker bug on OnChangeEvent

[Andrea Franco]

Hi,

I'm using build 1531 (uniGUI Complete - Professional Edition) and I found a bug in TUnimDatePicker component, if I initialize the date from object inspector ('18/05/2020' or '16/05/2020') or from code using "date" function (:=date or :=date-2) starting from the initialized date and moving to other dates the OnChange event works correctly, but returning to the same initialized date the event doesn't works. Everything works fine initializing the component's date using the "now" function.

[Andrea Franco]

OnChangeValue event is not working too, it works only with changes from code, not from GUI, we can't continue to use build 1531 and all new versions until you solve the problem, we need to revert to build 1526.

[Sherzod]

17 minutes ago, Andrea Franco said:

OnChangeValue event is not working too, it works only with changes from code, not from GUI, we can't continue to use build 1531 and all new versions until you solve the problem, we need to revert to build 1526.

Hello,

Could you send a test app?

[Andrea Franco]

48 minutes ago, Sherzod said:

Hello,

Could you send a test app?

Hi,

you can simply use an empty mobile project with only a TUnimDatePicker component inside the main form.

[Sherzod]

8 minutes ago, Andrea Franco said:

you can simply use an empty mobile project with only a TUnimDatePicker component inside the main form.

OK.

[Sherzod]

20 hours ago, Andrea Franco said:

you can simply use an empty mobile project with only a TUnimDatePicker component inside the main form.

Hello,

Can you test with this approach?:

UnimDatePicker.ClientEvents.UniEvents ->

function afterCreate(sender)
{
    sender.originalValue=null;
}

 

[Andrea Franco]

Thanks, it works fine, next buid will solve this problem without the need for this workaround?

[Sherzod]

21 minutes ago, Andrea Franco said:

next buid will solve this problem without the need for this workaround?

When committed, this will be indicated in changelog.