从表格主要调用子代表的功能由委托 [英] From Form Main call Function in child form by Delegate

问题描述

大家好！

我遇到一些关于代表的问题，请帮助我。

我已经成为主要和形式孩子。在表格中，孩子有一个标签anh funcSettext来改变标签中的文字。在表单主要有一个按钮，当我点击按钮将创建一个新的表单子（我可以创建n表单子）。并且表单主要有文本框，我想更改文本框中的文本，然后子表单中的所有文本都已更改。请帮我。警告使用委托。谢谢

Hi All!
i meet some problem about delegate, Please help me.
I have form main and form child. In form child have a label anh func "Settext" to change text in lable. In form main have a button, when i click button will create a new form child ( i can create n form child). And form main have textbox, I want to change the text in the textbox, then all text in child forms have changed over. Please help me. Warning use delegate. Thanks

推荐答案

请参阅我对该问题的评论。这个问题并没有真正制定出来。好吧，你想做点什么，那又怎样？为什么不按照你想要的方式去做呢？



但是，这可能与关于表单协作的流行问题有关。最强大的解决方案是在表单类中实现适当的接口，并传递接口引用而不是引用Form的整个实例。有关更多详细信息，请参阅我以前的解决方案：如何以两种形式复制列表框之间的所有项目 [ ^ ]。



另请参阅此处的其他解决方案讨论。如果应用程序足够简单，解决方案就像在一个表单中声明一些 internal 属性并将对一个表单的实例的引用传递给另一个表单的实例一样简单形成。对于更复杂的项目，这种违反严格封装的样式和松散耦合可能会增加代码的意外复杂性并引发错误，因此封装良好的解决方案将是优惠。



另请参阅：

http://en.wikipedia.org/wiki/Accidental_complexity [ ^ ]，

http://en.wikipedia.org/wiki/Loose_coupling [ ^ ]。

-SA

Please see my comment to the question. The problem is not really formulated. Well, you want to do something, so what? why not doing it the way you want?

However, this could be related to the popular question about form collaboration. The most robust solution is implementation of an appropriate interface in form class and passing the interface reference instead of reference to a "whole instance" of a Form. Please see my past solution for more detail: How to copy all the items between listboxes in two forms[^].

Please also see other solutions in this discussion. If the application is simple enough, the solution could be as simple as declaring of some internal property in one form and passing a reference to the instance of one form to the instance of another form. For more complex projects, such violation of strictly encapsulated style and loose coupling could add up the the accidental complexity of the code and invite mistakes, so the well-encapsulated solution would be preferable.

Please see also:
http://en.wikipedia.org/wiki/Accidental_complexity[^],
http://en.wikipedia.org/wiki/Loose_coupling[^].

—SA

这篇关于从表格主要调用子代表的功能由委托的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！