Current filter:
                                You should refresh the page.
                                  • This means that I cannot use Caliburn.Micro (MVVM framework) when using DevExpress/Ribbon for WPF, since it is using triggers which does not work with FrameworkContentElement. My understanding is that FrameworkContentElement should be used within a flow document.

                                    Any comments on this?

                                    Regards,
                                    Magnus Haggren

                                Hi Magnus,

                                In fact, the BarItem is a non-visual element which is used to define how an item should look and which actions it should perform. Since it shouldn't be rendered, we decided that it is more appropriate to inherit it from a light-weight FrameworkContentElement, rather than use a FrameworkElement as its ancestor.

                                However, I'm afraid from your post we do not quite understand what difficulties this causes for you. Can you please describe the problem in as much detail as possible, so that we can look for a solution?

                                Thanks,
                                Vito

                                Say that I have created a storyboard where I do some sort of animation in my UI. If I want to trigger the storyboard I can use an EventTrigger like this:

                                <Window.Triggers>
                                     <EventTrigger RoutedEvent="ButtonBase.Click" SourceName="button">
                                          <BeginStoryboard Storyboard="{StaticResource OnClick1}"/>
                                     </EventTrigger>
                                </Window.Triggers>

                                Since BarItem descends from FrameworkContentElement I cannot use this control in an EventTrigger.

                                Caliburn.Micro is a MVVM framework and has a powerful way of triggering methods on my ViewModel using triggers, which fails if I try to use a BarItemButton.

                                When I looked at your Silverlight version of BarItem, it does descend from FrameworkElement which is different from WPF. What's the reason for this?

                                Regards,
                                Magnus Haggren

                                Just to clarify the point above with EventTrigger, this is not possible and will generate an error:

                                <Window.Triggers>
                                     <EventTrigger RoutedEvent="dxb:BarButtonItem.ItemClick" SourceName="button">
                                          <BeginStoryboard Storyboard="{StaticResource OnClick1}"/>
                                     </EventTrigger>
                                </Window.Triggers>

                                The error when I try to run is this:

                                "'itemCopy' is not a type derived from FrameworkElement."

                                Regards,
                                Magnus Haggren

                                Hello Magnus,

                                After some discussion, we decided to descend our bar item from the FrameworkElement. We'll implement this feature in the v10.2 version to prevent a breaking change in the v10.1 version. Please track the following suggestion: Descend the BarItem from FrameworkElement for event triggers' support

                                Thank you, Marina

                                Did this make it to the 2010.2 version? I can not see that the issue S35747 has changed status to implemented yet.

                                Regards,
                                Magnus Haggren

                                Hello Magnus,

                                The suggestion status is planned. We will implement it in one of minor releases of the v10.2 version. Please bear with us. You will be notified when the issue status will be changed.

                                Thank you, Marina

                                Hello Magnus,

                                The suggestion status is set to planned. We will implement it in one of minor releases of version v10.2. Please bear with us. You will be notified when the issue status is changed.

                                Thank you, Marina