WPF/C# - 以编程方式创建和创建的示例使用单选按钮
有人可以举一个如何以编程方式创建和创建的示例吗?在 C# WPF 中使用单选按钮?
所以基本上如何(a)以编程方式创建它们,以及(b)如何在值更改时捕获触发器,(c)如何在给定时间获取结果。
我们也有兴趣看看答案是否也基于使用绑定方法。如果数据绑定是最简单的方法,那么这个例子就很好了。否则,如果数据绑定不是最好/最简单的方法,那么基于非数据绑定的示例会很好。
注意:
注意我的父节点 目前是StackPanel,所以一个方面 问题是如何添加 多个RadioButtons到一个 StackPanel我猜。
应该指出,我不知道在编译时会有多少个单选按钮,也不知道文本是什么,这将在运行时发现。
它是一个WPF应用程序(即桌面,而不是Web应用程序)
Can someone point to an example of how to programmatically create & use Radio Buttons in C# WPF?
So basically how to (a) create them programmatically, and (b) how to catch triggers when the value changes, (c) how to pick up results at a given time.
Will be interested to see too if the answer will be based on use of a Binding approach too. If data binding is the easiest way to go then an example of this would be great. Else if data binding isn't necessary the best/easiest way to go then a non-data-binding based example would be good.
Notes:
Note that the parent node I have
currently is StackPanel, so an aspect
of the question is how to add
multiple RadioButtons to a
StackPanelI guess.Should point out that I won't know how many radio buttons there will be at compile time, nor what the text will be this will be discovered at run time.
It is a WPF application (i.e. desktop, not a web app)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
通常,我们使用 RadioButtons 向用户呈现 Enum 数据类型。我们通常做的是使用 ItemsControl 来呈现一组 RadioButton,每个 RadioButton 都绑定到一个 ViewModel。
下面是我刚刚编写的一个示例应用程序,它演示了如何以两种方式使用 RadioButtons:第一种是直接方法(这可能会回答您上面的问题),第二种使用 MVVM 方法。
顺便说一句,这只是我很快写的东西(是的,我有很多时间)所以我不会说这里的一切都是完美的做事方式。但我希望您发现这有帮助:
XAML:
隐藏代码:
Normally, we use RadioButtons to present an Enum data type to the user. And what we usually do is use an ItemsControl to present a group of RadioButtons, with each one bound to a ViewModel.
Below is a sample application I just wrote that demonstrates how RadioButtons could be used in two ways: the first is somewhat of a direct approach (and this may answer your questions above), and the second one uses an MVVM approach.
BTW, this is just something I wrote quickly (yeah, I got a lot of time in my hands) so I won't say that everything in here is the perfect way of doing things. But I hope you find this helpful:
XAML:
Code-behind: