Dear Friends,
I am the person that wrote about Regional.FarsiPersian bug on this component. The bug was the wrong behavior of this component when you set this property to Regional.FarsiPersian. After a few communication with Jorge, I accepted the component behavior and the Jalali calendar added to the IWCGJQSuite package.
For brief, our customers is Persian and works with Jalali calendar not Georgian, it is the main reason for me to be corrected the behavior of this useful component.
Now, I am evaluating whole package to buy and using in our web sector applications, then in my sample, I used this component with Regional.FarsiPersian property. But I see the wrong behavior of the component, but this time is different. I explain the details below:
As we know, This component is for displaying date fields to the user and get the value for them to store to the database related field(Date-Aware mode).
In my fields, the users must see the Jalali calendar and select a date value, but the key note is we works always with Georgian value, it means users only view the date value as Persian(Jalali) and could manipulate it. Finally, the new value selected by user stores in the field as Georgian date.
In the other words, JQDatePicker must use Georgian value ever(Date property) and when it want to show, the Jalali value will be shown. Now user see the Jalali value and select the new one, but when it want to write value to its Date property, it must convert it to Georgian.
If anyone want to store Jalali value in the database, I think this component must use a property for covering two mechanism, a property for example "ViewOnly". For me this property set to True.