We are using XamDateTimeInput control in our project.
Below is the mentioned issue:
Whenever user selects datetime control the cursor position by default set to 2nd index (This is because of the property named “SelectionStart” set to “2”).
Now if user change cursor position and looses focus from current datetime input control and come back to current Datetime input control then it remembers previous cursor position and by default cursor sets to old index position.
We need expected behavior as below:
We need a way where, user clicks on any position in datetime control and cursor should started blinking at that position only.
I.e. If user clicks on 8th position then cursor should cursor should start blinking at “8” position only instead of 2nd position or last remembered.
Kindly requesting you to help us with DateTime control Selection issue.
Hi cfosterj,
You are definitely welcome. The case that I mentioned is linked directly to your account and while there isn’t a link per se, you will be able to access it by first logging into your account for the Infragistics website and selecting the tab on the left pane for support activity; from the next page, you will be able to view both the case associated with this issue, other active cases and a full history of previous cases.
If you have any further questions, please let me know.
Sincerely,Chris KDeveloper Support EngineerInfragistics, Inc.www.infragistics.com/support
Thanks for your quick response.
Kindly requesting you to provide me Link for the case : CAS-115804-Q0C0X7.
Regards,
Chris F.
I have created case CAS-115804-Q0C0X7 to facilitate further investigation of this issue.
I have observed the behavior that you have expressed interest in, but only with the generic Silverlight TextBox. The behavior of resuming from the most recent cursor position is consistent across all four of the Xam-Input editor controls and this appears to be the expected behavior for this scenario.
I do have an idea for one possible approach which would achieve the behavior that you are interested in, with the XamDateTimeInput control, but developing this approach would be quite involved and would require the submission of a product idea.
Just in case, I am placing an inquiry to my development team to verify that this behavior was intended and for any suggested approaches they might recommended, where feasible.
I will be following up with you via the above mentioned case regarding this inquiry and I will also be updating this forum thread for any other interested parties.
If you have any further questions in the meantime, please let me know.
I am currently investigating this behavior and I will be following up with you via this forum thread regarding my findings.
If you have any further questions that I may assist you with in the meantime, please let me know.