This example demonstrates how to implement WinForms DataNavigator in WPF via Behavior. For this, it's necessary to re-define the x:Key="{dxgt:TableViewThemeKey ResourceKey=ScrollViewerTemplate}" control template and create the DataNavigator behavior that loads a re-defined template at the moment of attaching.
If you are using themes, you need to re-define a control template for your theme and add it's name to the key - x:Key="{dxgt:TableViewThemeKey ResourceKey=ScrollViewerTemplate, ThemeName=DXStyle}"
Update
Starting with v15.1, GridControl provides the embedded DataNavigator out of the box. To learn more about this feature, refer to the Data Navigator topic in our documentation.
Question Comments
Added By: Corentin Fougeray at: 8/28/2014 6:09:13 AM
Hello,
I've been using this solution for our new project. It is satisfying as a workaround but not for production : what about the other themes you provide ? I don't know their innards (and I don't want to), so what about their templates for this ?
I've tested with DeepBlue for instance (replacing DXStyle by DeepBlue in Dictionary.xaml) and it doesn't work (no navigator displayed). With Office2010Blue it works but the First/Last buttons aren't coherent (not the same glyph, maybe a problem of this theme).
And what about the position of this embedded navigator ? It is above the total summary panel which is a very awkward place ! Not mentioning that your workaround doesn't display anything in design-mode which is not very convenient...
Anyway, you should provide an embedded navigator with your WPF grid (as you did with de WinForms one which is very satisfying and heavily used in our other projects), not a messy workaround which requires the developers to customize your component's innards in order to get such a basic feature !
Added By: Alexander Rus (DevExpress Support) at: 8/28/2014 9:01:32 AMHello Corentin,
To process your recent post more efficiently, I created a separate ticket on your behalf: T145168: Different themes support in E4347. This ticket is currently in our processing queue. Our team will address it as soon as we have any updates.
Thanks,
Alexander