我怎么...在c＃中调用构造函数... [英] How do I... recall constructor in c#...

问题描述

如果我更新一些数据，那么我希望他们通过回忆形式

if i update some data then i want them to show immidietly by recalling constructor of the form

推荐答案

的构造函数来显示，并想想构造函数这个词 - 它意味着建筑我们创建的项目，您只对任何项目执行一次。如果你正在制作一个三明治，你可以构建一次，并且每次咬一次重复使用。

如果你每次想要咬一口就制作三明治，你就可以通过整个马上加载！



所以忘记构造函数，并通过将新信息传递给它并让它显示新数据来重用现有表单。

看看这个：在两个表格之间传递信息，第1部分：父母与孩子 [ ^ ]它应该有帮助。

Think about the word 'constructor' - it implies the building our creation of an item, which you only do once for any item. If you are making a sandwich, you 'construct' it once, and 'use' it repeatedly for each bite.
If you constructed the sandwich each time you wanted a bite, you would get through a whole load in no time!

So forget constructors, and reuse the existing form by passing the new information to it and getting it to display you new data.
Have a look at this: Transferring information between two forms, Part 1: Parent to Child[^] it should help.

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



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



另请参阅：

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

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

-SA

Please see my comments to the question. It could be just 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

这篇关于我怎么...在c＃中调用构造函数...的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！