阅读其他形式的价值观 [英] Reading values on other form

问题描述

我在从另一个表单读取值时遇到问题。



在我的frmMain Load中我有这个代码，后来在frmMain中，我尝试从frmSettings上的一些复选框中读取值，返回false。如果我打开frmSettings，我可以看到复选框中的值设置为（true）。如何读取frmSettings中的值？我假设已经触发了frmSettings上的Load。谢谢你的支持。

Hi,
I am having a problem reading values from another form.

In my frmMain Load I have this code and later in frmMain I try to read values from some checkboxes on frmSettings which returns false. If I open the frmSettings I can see that the values are set (true) in the checkboxes. How do I read the values from the frmSettings ? I presume the Load on frmSettings has been fired. Thank you in adcance.

Private Sub frmMain_Load(sender As System.Object, e As System.EventArgs) Handles MyBase.Load
        Dim fSet As New frmSettings()

        Try
            Me.Height = 600
            Me.Width = 1024
            fSet.Owner = Me

            fSet.Opacity = 0
            fSet.Show()
            fSet.Hide()

            If fSet.chkSaveFormPos.Checked Then
                RestorePosition(Me)
            End If
End Sub

Private Sub CheckValue()
      MsgBox(frmSettings.chkSaveFormPos.Checked)
End Sub

推荐答案

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



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



另请参阅：

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

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

-SA

It looks like 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屋！