Hello,
We have a XamGrid whose Editor Template is a TextBox. When the user clicks a cell in the XamGrid, it shows the TextBox. However, the user has to click again within the TextBox to start typing. Thus two clicks are needed for each TextBox cell. This behavior is annoying our users.
Is there anyway to automatically enable the keyboard focus on the TextBox that is used as the XamGrid Cell editor ?
[Additional Details]
I noticed that in the default implementation of XamGrid without an EditorTemplate, it behaves correctly. On the first click the cell gets activated and the user is able to start typing. It is only when the XamGrid uses EditorTemplate that two clicks are needed.
Hello Koshy,
Thank you for your post. I have been looking into it and I created a sample project for you following your scenario and everything seems to work ok on my side. If the sample doesn’t satisfies all your needs feel free to modify it, so it reproduces your behavior and send it back to me for further investigation.
Looking forward for your reply.
Hello Stefan,
Thanks very much for the quick response and sample project. I have modified your sample project and reproduced the issue I described earlier. The modified sample project is attached.
Thanks,
Koshy
I have tested the modified sample and I was able to reproduce your behavior with the RTM of version 12.1. I also tested it against the latest Service release of 12.1 (2169) and there the issue has been fixed, so I can suggest you download it by logging to our web site and going to Account \Keys & Downloads. Please let me now if this helps you or you need further assistance on this matter.
Hi Stefan,
Actually, I got the idea for the workaround solution after looking at your sample code. So I would like to thank you for the great support and providing the sample code.
regards,
Thank you for your feedback. I am glad that you resolved your issue and I believe that other community members may benefit from this as well.
Thanks again.
Thanks for the clarification. I found a simple workaround to fix this issue without having to upgrade our existing Infragistics version. I have attached the updated sample.