Posted 10 years ago by Bill Boland - Software Engineer, CME, Inc for Thomson Elite
Version: 9.1.0503
Platform: .NET 3.5
Environment: Windows 7 (32-bit)
Avatar
We're using WPF Studio 9.1.503.0 and noticed when using a DateTimePicker with IsEditable="True" and a TabIndex assigned, the DateTimePicker is skipped and treated as if there was no TabIndex assign.

        <StackPanel>
                <TextBox Height="23" Name="textBox0" Width="120"/>
                <TextBox Height="23" Name="textBox1" Width="120" TabIndex="1"/>
                <TextBox Height="23" Name="textBox2" Width="120" TabIndex="2"/>
                <TextBox Height="23" Name="textBox3" Width="120" TabIndex="3"/>
                <shared:DateTimePicker Height="21.96" Name="dateTimePicker1" 
                                       IsEditable="True" Width="200" TabIndex="4"/>
                <TextBox Height="23" Name="textBox4" Width="120" TabIndex="5"/>
                <TextBox Height="23" Name="textBox5" Width="120"/>
            </StackPanel>
If the IsTabStop="True" is assigned to the DateTimePicker, it starts to go in the correct order and navigates to the DateTimePicker but tabbing out of the DateTimePicker does not go to the next TabIndex control but instead continues with elements that have no TabIndex assigned.

        <StackPanel>
                <TextBox Height="23" Name="textBox0" Width="120"/>
                <TextBox Height="23" Name="textBox1" Width="120" TabIndex="1"/>
                <TextBox Height="23" Name="textBox2" Width="120" TabIndex="2"/>
                <TextBox Height="23" Name="textBox3" Width="120" TabIndex="3"/>
                <shared:DateTimePicker Height="21.96" Name="dateTimePicker1" 
                                       IsEditable="True" Width="200" TabIndex="4" IsTabStop="True"/>
                <TextBox Height="23" Name="textBox4" Width="120" TabIndex="5"/>
                <TextBox Height="23" Name="textBox5" Width="120"/>
            </StackPanel>
If IsEditable="False" then the expected tab navigation is observed.



[Modified at 02/09/2010 12:39 PM]

Comments (2)

Posted 10 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Bill,

Thanks for reporting this issue. The DateTimePicker used the default value for KeyboardNavigation.TabNavigation, which is Continue. We've updated the code to use the value "Local" as the default, which mimics the ComboBox.

In the meantime, you can add KeyboardNavigation.TabNavigation="Local" to your DateTimePicker definition to fix the issue.


Actipro Software Support

Posted 10 years ago by Bill Boland - Software Engineer, CME, Inc for Thomson Elite
Avatar
Thank you. That seemed to do the trick to resolve our issue. We had already subclassed the DateTimePicker to a custom component so the change, in our situation, was to override the DP metadata with this default so it did not require XAML changes for our custom component and subclasses.
The latest build of this product (v2019.1 build 0683) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.