互斥的可检查菜单项?
给出以下代码:
<MenuItem x:Name="MenuItem_Root" Header="Root">
<MenuItem x:Name="MenuItem_Item1" IsCheckable="True" Header="item1" />
<MenuItem x:Name="MenuItem_Item2" IsCheckable="True" Header="item2"/>
<MenuItem x:Name="MenuItem_Item3" IsCheckable="True" Header="item3"/>
</MenuItem>
在 XAML 中,有没有办法创建互斥的可检查菜单项?当用户选中item2时,item 1和3会自动取消选中。
我可以通过监视菜单上的单击事件、确定选中哪个项目并取消选中其他菜单项,在后面的代码中完成此操作。我想有一个更简单的方法。
有什么想法吗?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(19)
这可能不是您想要的,但您可以为
MenuItem
类编写一个扩展,该扩展允许您使用的
类。我稍微修改了 这个 类似扩展的方便示例GroupName
属性之类的内容RadioButtonToggleButton
控件并根据您的情况对其进行了一些修改,并得出了以下结论:然后,在 XAML 中,您可以编写:
这有点痛苦,但它提供了不强迫您的好处编写任何附加的过程代码(当然,除了扩展类之外)来实现它。
感谢 Brad Cunningham,他是最初的 ToggleButton 解决方案的作者。
This may not be what you're looking for, but you could write an extension for the
MenuItem
class that allows you to use something like theGroupName
property of theRadioButton
class. I slightly modified this handy example for similarly extendingToggleButton
controls and reworked it a little for your situation and came up with this:Then, in the XAML, you'd write:
It's a bit of a pain, but it offers the perk of not forcing you to write any additional procedural code (aside from the extension class, of course) to implement it.
Credit goes to Brad Cunningham who authored the original ToggleButton solution.
由于我还没有声誉,因此将其添加到底部...
尽管帕特里克的答案很有帮助,但它并不能确保无法取消选中项目。为此,应将 Checked 处理程序更改为 Click 处理程序,并更改为以下内容:
Adding this at the bottom since I don't have the reputation yet...
As helpful as Patrick's answer is, it doesn't ensure that items cannot be unchecked. In order to do that, the Checked handler should be changed to a Click handler, and changed to the following:
您还可以使用行为。就像这个:
You can also use a Behavior. Like this one:
由于没有类似的答案,我在这里发布我的解决方案:
在 XAML 中,只需将其用作通常的 MenuItem:
非常简单和干净。当然,您可以通过一些额外的代码将
GroupName
设为依赖属性,这与其他代码相同。顺便说一句,如果您不喜欢复选标记,您可以将其更改为您喜欢的任何内容:
如果您在程序中使用了大量此
RadioMenuItem
,则还有另一个更有效的版本,如下所示。文字数据是从前面的代码片段中的e.GetFlattenedPathGeometry().ToString()
获取的。最后,如果您打算将其包装在项目中使用,则应该从基类中隐藏
IsCheckable
属性,因为MenuItem
类的自动检查机制将导致无线电检查状态标记错误行为。因此,如果新手尝试像这样编译 XAML,VS 将给出错误:
Since there is not a samilar answer, I post my solution here:
In XAML just use it as an usual MenuItem:
Quite simple and clean. And of course you can make the
GroupName
a dependency property by some additional codes, that's all the same as others.BTW, if you do not like the check mark, you can change it to whatever you like:
If you used plenty of this
RadioMenuItem
in your program, there is another more efficient version shown below. The literal data is aquired frome.GetFlattenedPathGeometry().ToString()
in previous code snippet.And at last, if you plan to wrap it for use in your project, you should hide
IsCheckable
property from the base class, since the auto check machenism ofMenuItem
class will lead the radio check state mark a wrong behavior.Thus VS will give an error if a newbie try to compile XAML like this:
是的,通过将每个 MenuItem 设为 RadioButton 可以轻松完成此操作。这可以通过编辑菜单项的模板来完成。
右键单击文档大纲左窗格中的菜单项>编辑模板>编辑复制。这将在 Window.Resources 下添加用于编辑的代码。
现在,您只需要做两处更改,非常简单。
a。添加带有一些资源的 RadioButton 以隐藏其圆圈部分。
b.更改 MenuItem 边框部分的 BorderThickness = 0。
这些更改作为注释显示在下面,生成的样式的其余部分应按原样使用:
应用样式,
Yes, this can be done easily by making every MenuItem a RadioButton. This can be done by Editing Template of MenuItem.
Right-Click the MenuItem in the Document-Outline left pane > EditTemplate > EditCopy. This will add the code for editing under Window.Resources.
Now, you have to do only two-changes which are very simple.
a. Add the RadioButton with some Resources to hide its circle portion.
b. Change BorderThickness = 0 for MenuItem Border part.
These changes are shown below as comments, rest of the generated style should be used as is :
Apply the Style ,
这是一个简单的、基于 MVVM 的解决方案,它利用每个 MenuItem 的简单 IValueConverter 和 CommandParameter。
无需将任何 MenuItem 重新设计为不同类型的控件。当绑定值与 CommandParameter 不匹配时,MenuItems 将自动取消选择。
绑定到 DataContext (ViewModel) 上的 int 属性 (MenuSelection)。
定义您的价值转换器。这将根据命令参数检查绑定值,反之亦然。
添加您的资源
祝你好运!
Here's a simple, MVVM-based solution that leverages a simple IValueConverter and CommandParameter per MenuItem.
No need to re-style any MenuItem as a different type of control. MenuItems will automatically be deselected when the bound value doesn't match the CommandParameter.
Bind to an int property (MenuSelection) on the DataContext (ViewModel).
Define your value converter. This will check the bound value against the command parameter and vice versa.
Add your resource
Good luck!
我只是想我会提出我的解决方案,因为没有一个答案满足我的需求。我的完整解决方案在这里...
WPF MenuItem as a RadioButton
但是,基本思想是使用 ItemContainerStyle。
并且应该添加以下事件 click ,以便在单击 MenuItem 时检查 RadioButton (否则您必须精确单击 RadioButton ):
I just thought I would throw in my solution, since none of the answers met my needs. My full solution is here...
WPF MenuItem as a RadioButton
However, the basic idea is to use ItemContainerStyle.
And the following event click should be added so that the RadioButton is checked when the MenuItem is clicked (otherwise you have to click exactly on the RadioButton):
XAML 中没有内置方法可以执行此操作,您需要推出自己的解决方案或获取现有解决方案(如果可用)。
There is not a built-in way to do this in XAML, you will need to roll your own solution or get an existing solution if available.
我使用几行代码实现了这一点:
首先声明一个变量:
当我们考虑一组菜单项时,有可能使用单个事件处理程序。在这种情况下我们可以使用这个逻辑:
I achieved this using a couple of lines of code:
First declare a variable:
When we are considering a group of menuitems, there is a probability of using a single event handler. In this case we can use this logic:
我发现将 MenuItem.IsChecked 绑定到变量时会得到互斥的菜单项。
但它有一个怪癖:如果单击选定的菜单项,它就会无效,如通常的红色矩形所示。我通过为 MenuItem.Click 添加一个处理程序来解决这个问题,该处理程序只需将 IsChecked 设置回 true 即可防止取消选择。
代码...我绑定到枚举类型,因此我使用枚举转换器,如果绑定属性等于提供的参数,则该转换器返回 true。这是 XAML:
这是背后的代码:
I find that I get mutually exclusive menu items when binding MenuItem.IsChecked to a variable.
But it has one quirk: If you click the selected menu item, it gets invalid, shown by the usual red rectangle. I solved it by adding a handler for MenuItem.Click that prevents unselecting by just setting IsChecked back to true.
The code... I'm binding to an enum type, so I use an enum converter that returns true if the bound property is equal to the supplied parameter. Here is the XAML:
And here is the code behind:
几年后,我看到这篇文章,其中包含我写的关键字...我认为在 wpf 中有一个简单的解决方案...也许是我,但我认为为这么小的东西拥有如此庞大的武器库有点特别作为公认的解决方案。我什至没有谈论 6likes 的解决方案,我不明白在哪里单击才能获得此选项。
所以也许它真的一点也不优雅......但这里有一个简单的解决方案。它的作用很简单......循环父级包含的所有元素,将其设置为 false。大多数时候人们将这部分与其他部分分开,当然只有在这种情况下才是正确的。
这很简单,xaml是一个经典的代码,绝对没有什么特别的
当然你可能需要click方法,这不是问题,你可以创建一个接受对象发送者的方法,并且每个click方法都将使用这个方法方法。它又旧又丑,但暂时还可以用。
我有一些问题,想象这么多代码行用于这么小的事情,可能是我对 xaml 有问题,但必须这样做才能只选择一个菜单项似乎令人难以置信。
Several years after i see this post with the keywords i wrote... i thought there was an easy solution, in wpf... Perhaps it's me, but i think it's a bit special to have a such massive arsenal for a so little thing as accepted solution. I don't even talk about the solution with 6likes i didn't understood where to click to have this options.
So perhaps it's really no elegant at all... But here a simple solution. What it do is simple.. a loop to all elements contained by the parent, to put it at false. The most of time people split this part from the others parts, of course it's only correct in this case.
that's all and easy, xaml is a classic code with absolutaly nothing particular
Of course you could have a need of the click method, it's not a problem, you can make a method that accept an object sender and each of your click method will use this method. It's old, it's ugly but for the while it works.
And i have some problems to imagine so much code line for a so little thing, it's probably me that have a problem with xaml, but it seems incredible to have to do this to obtains to just have only one menuitem selected.
对@Patrick 答案的一个小补充。
正如 @MK10 提到的,该解决方案允许用户取消选择组中的所有项目。但他建议的改变现在对我不起作用。也许,WPF 模型从那时起就发生了变化,但现在当取消选中某个项目时,不会触发
Checked
事件。为了避免这种情况,我建议处理
MenuItem
的Unchecked
事件。我更改了这些过程:
并添加了下一个处理程序:
现在,当用户第二次单击时,选中的项目仍保持选中状态。
A small addition to the @Patrick answer.
As @MK10 mentioned, this solution allows user to deselect all items in a group. But the changes he suggested doesn't work for me now. Maybe, the WPF model was changed since that time, but now
Checked
event doesn't fired when an item is unchecked.To avoid it, I would suggest to process the
Unchecked
event forMenuItem
.I changed these procedures:
and added the next handler:
Now the checked item remains checked when user clicks it second time.
这是另一种方法——无论如何都不容易,但它兼容 MVVM、可绑定且高度可单元测试。如果您可以自由地将转换器添加到项目中,并且不介意每次打开上下文菜单时以新项目列表的形式出现一些垃圾,那么这非常有效。它满足了如何在上下文菜单中提供一组互斥的选中项的原始问题。
我认为,如果您想将所有这些提取到用户控件中,您可以将其制作成可重用的库组件,以便在您的应用程序中重用。
使用的组件是 Type3.Xaml,带有一个简单的网格、一个文本块和上下文菜单。右键单击网格中的任意位置即可显示菜单。
名为 AllValuesEqualToBooleanConverter 的值转换器用于将每个菜单项的值与组的当前值进行比较,并在当前选定的菜单项旁边显示复选标记。
使用一个代表菜单选项的简单类进行说明。示例容器使用具有 String 和 Integer 属性的 Tuple,这使得很容易将紧密耦合的人类可读文本片段与机器友好的值配对。您可以单独使用字符串或字符串和枚举来跟踪值,以便对当前内容做出决策。
Type3VM.cs 是分配给 Type3.Xaml 的 DataContext 的 ViewModel。无论您如何在现有应用程序框架中分配数据上下文,请在此处使用相同的机制。所使用的应用程序框架依赖于 INotifyPropertyChanged 将更改的值传达给 WPF 及其绑定对象。如果您有依赖属性,您可能需要稍微调整代码。
除了转换器及其长度之外,此实现的缺点是每次打开上下文菜单时都会创建一个垃圾列表。对于单用户应用程序,这可能没问题,但您应该意识到这一点。
该应用程序使用 RelayCommand 的实现,该实现可以从 Haacked 网站轻松获得,或者可以在您使用的任何框架中使用任何其他 ICommand 兼容的帮助程序类。
Here is yet another way – not easy by any stretch but it is MVVM compatible, bindable and highly unit testable. If you have the freedom to add a Converter to your project and don’t mind a little garbage in the form of a new list of items every time the context menu opens, this works really well. It meets the original question of how to provide a mutually exclusive set of checked items in a context menu.
I think if you want to extract all of this into a user control you could make it into a reusable library component to reuse across your application.
Components used are Type3.Xaml with a simple grid, one text block and the context menu. Right-click anywhere in the grid to make the menu appear.
A value converter named AllValuesEqualToBooleanConverter is used to compare each menu item’s value to the current value of the group and show the checkmark next to the menu item that is currently selected.
A simple class that represent your menu choices is used for illustration. The sample container uses Tuple with String and Integer properties that make is fairly easy to have a tightly coupled human readable snippet of text paired with a machine-friendly value. You can use strings alone or String and an Enum to keep track of the Value for making decisions over what is current.
Type3VM.cs is the ViewModel that is assigned to the DataContext for Type3.Xaml. However you contrive to assign your data context in your existing application framework, use the same mechanism here. The application framework in use relies on INotifyPropertyChanged to communicate changed values to WPF and its binding goo. If you have dependency properties you may need to tweak the code a little bit.
The drawback to this implementation, aside from the converter and its length, is that a garbage list is created every time the context menu is opened. For single user applications this is probably ok but you should be aware of it.
The application uses an implementation of RelayCommand that is readily available from the Haacked website or any other ICommand-compatible helper class available in whatever framework you are using.
只需为 MenuItem 创建一个模板,其中将包含一个 RadioButton,其 GroupName 设置为某个值。
您还可以更改 RadioButtons 的模板,使其看起来像 MenuItem 的默认检查字形(可以使用 Expression Blend 轻松提取)。
就是这样!
Simply create a Template for MenuItem which will contain a RadioButton with a GroupName set to some value.
You can also change the template for the RadioButtons to look like the MenuItem's default check glyph (which can be easily extracted with Expression Blend).
That's it!
你可以这样做:
它在视觉上有一些奇怪的副作用(当你使用它时你会看到),但它仍然有效
You could do something like this:
It has some weird side effect visually (you'll see when you use it), but it works nonetheless
这是另一种使用 RoutedUICommands(公共枚举属性)和 DataTriggers 的方法。这是一个非常冗长的解决方案。不幸的是,我没有看到任何使 Style.Triggers 变小的方法,因为我不知道如何说 Binding Value 是唯一不同的东西? (顺便说一句,对于 MVVMers 来说,这是一个糟糕的例子。我将所有内容都放在 MainWindow 类中只是为了简单起见。)
MainWindow.xaml:
MainWindow.xaml.cs:
Here's another approach that uses RoutedUICommands, a public enum property, and DataTriggers. This is a pretty verbose solution. I unfortunately don't see any way of making the Style.Triggers smaller, because I don't know how to just say that the Binding Value is the only thing different? (BTW, for MVVMers this is a terrible example. I put everything in the MainWindow class just to keep things simple.)
MainWindow.xaml:
MainWindow.xaml.cs:
这是我为此目的创建的自定义控件。
它正确处理选中、取消选中、单击事件和组名称更改。
如果您愿意,可以覆盖菜单项的样式并将复选标记更改为单选标记,但这不是必需的:
示例:
Here is a custom control that i've created for this purpose.
It handles correctly checking, unchecking, clicks events and group name changes.
If you want you can override the style of the menu item and change the checkmark to a radiomark, but is not necessary:
Example:
实现互斥工具条菜单项的最佳且正确的方法是:
请将 NameofParentToolStripMenuItem 替换为您想要具有此属性的菜单项。
The best and correct way to implement mutually exclusive toolstrip menu item is;
Please replace NameofParentToolStripMenuItem with the menuitem where you want to have this property.