I have just started to use the NetAdvantage 2011.2. When using the new Input controls (e.g. XamMaskedInput) I noticed that although pressing Tab moves focus correctly forward through the controls, using Shift+Tab (reverse tab navigation) seems to get 'stuck' in the input controls (does not occur in the equivalent editor controls). Is this problem due to the way I'm using them, or a limitation of the Input controls?
This can be easily seen in the xamFeatureBroswer app (xamInputs section examples).
Hello cassellm,
When hitting the Shift and Tab keys staying focus on the XamMaskedInput may be part of the design. In the help documentation contains information for the usage: http://help.infragistics.com/NetAdvantage/WPF/2011.2/CLR4.0/?page=xamMaskedInput.html. As for flexibility the control contains the KeyDown event. In this event handler you should be able to add a condition to check whether the shift + tab key has been pressed and then change it's focus.
Let me know if you have any questions with this matter. Thank you.
I am unable to see anything in the suggested document link that references this particular behaviour. As this standard keyboard navigation is supported by standard controls as well as your editor controls, do you expect this limitation/bug to be addressed in the near future?
For a WPF application (which would also be making use of the xamDataGrid) would you recomend the use of the editor controls rather than the new input controls?