Hi,
We cannot use the shift tabulation with your combobox component. The standard tabulation work fine, but not the shift tabulation to return to the previous control.
Is there an option to use this functionnality ?
Regards,
Alban
Steps to Reproduce:
You can use the project in attachment.
With the devExpress combox, the shift tab doesn't work, but with the standard wpf button, the shift tab works correctly.
Bug Report
B205403
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi,
When do you think this issue will be fix ? It's not a critical bug but it's strange for our customer :)
Thanks,
Alban
Hi Alban,
We have not yet managed to fix this problem. Our developers are still working on this issue.
I assure you that they will do their best to fix this issue as soon as possible. But, I cannot provide you with the exact time frame for the fix.
Thanks,
Vito
Hi Alban,
We have found out that the issue occurs because the IsTabStop property is set to True in your code. As you probably know, our editors are composite controls, containing the standard TextBox control inside. To support keyboard navigation, we set the IsTabStop property for the "outer" control to False once the editor receives keyboard focus, to move focus to the "inner" control (TextBox). The following trigger is used for this purpose:
<Style TargetType="{x:Type dxe:BaseEdit}"> <Trigger Property="IsKeyboardFocusWithin" Value="True"> <Setter Property="IsTabStop" Value="False"/> </Trigger> </Style>Since the local value has a higher priority than a style trigger, the code above cannot change the IsTabStop property value. So, when you press the "Shift+Tab", focus is moved to the "outer" control (a previously focused element), which, in its turn, moves focus back to the "inner" TextBox control.
We have not found an acceptable way to fix this at the level of our controls. It appears that the only solution we can suggest is not to set the IsTabStop property value to True (it is True by default). I am attaching a modified project, containing the necessary changes. Please try it on your side and let us know how it works for you.
Thanks,
Vito
This solution is acceptable and work fine.
We don't need to specify this property, the tabulation works fine now.
Thanks for your help.
Hi Alban,
We are glad to hear that this solution works as expected. Thank you for letting us know of your results.
Thanks,
Vito
I am trying to resolve this issue in our code also. Does this apply to CheckEdit also? And what about DateEdit?
I mean, should I remove IsTabStop from CheckEdits and/or DateEdits also?
Hello Ashar,
All our editors have the same architecture. So, this specificity is applied to the DateEdit and CheckEdit controls as well.
To address the problem, do not set the IsTabStop property value in XAML code. This way, tab navigation should work as expected. I have just checked this with the latest version of our WPF products and can confirm that both DateEdit and CheckEdit work correctly in this situation. I am attaching a modified sample project for your reference.