CODEWITHSUNDEEP
c#arrayswinformstextbox
João Ferreira
João Ferreira

Reputation: 5

Grabbing input from dynamically created textboxes to another form

So, we have a way to dynamically create an array of x by y of texboxes to input values into it to later on do some matrix calculation, like determine the rank of the matrix.

To generate the array we use this:

protected void Form2_Load(object sender, EventArgs e)
        {

            for (int row = 0; row < LinhaText; row++)
            {
                List<TextBox> newLin = new List<TextBox>();
                textboxes.Add(newLin);
                for (int col = 0; col < ColunText; col++)
                {
                    TextBox newbox = new TextBox();
                    newbox.Width = textboxWidth;
                    newbox.Height = textboxHeight;
                    newbox.Top = (row * (textboxHeight + spacing)) + spacing + vOffset;
                    newbox.Left = (col * (textboxWidth + spacing)) + spacing + hOffset;
                    newLin.Add(newbox);
                    this.Controls.Add(newbox);

                }
            }
        }

This stands on the second form, as in the first one we input the dimensions of the array. When we input the values on the textboxes they should get sent to the third form to get used by the other calculations. We are wondering how we grab the values and send them to the other form to later on display the results. Any further information you need, just ask!

Upvotes: 0

Views: 69

Answers (2)

Olivier Jacot-Descombes
Olivier Jacot-Descombes

Reputation: 112269

I would not pass around textboxes, instead store the numbers in a 2-dimensional array (matrix). Also I would use binding to automatically bind the matrix values to the textboxes. To make binding work, you need a helper class containing your values, because binding needs to bind to a property.

private class Data // Can be a nested private class in Form2.
{
    public double Value { get; set; }
    public override string ToString() => Value.ToString(); // Not strictly necessary, but
                                                           // makes debugging easier.
}

We create a _matrix field as well as a property converting this Data[,] matrix to a double[,] matrix and returning it (in Form2):

private Data[,] _matrix;

public double[,] Matrix
{
    get {
        var m = new double[LinhaText, ColunText];
        for (int row = 0; row < LinhaText; row++) {
            for (int col = 0; col < ColunText; col++) {
                m[row, col] = _matrix[row, col].Value;
            }
        }
        return m;
    }
}

Now create the textboxes and bind them to a Data object (In Form2_Load or in the form constructor after InitializeComponent):

_matrix = new Data[LinhaText, ColunText];
for (int row = 0; row < LinhaText; row++) {
    for (int col = 0; col < ColunText; col++) {
        var newbox = new TextBox {
            Width = textboxWidth,
            Height = textboxHeight,
            Top = (row * (textboxHeight + spacing)) + spacing + vOffset,
            Left = (col * (textboxWidth + spacing)) + spacing + hOffset
        };

        // Create Data object, add it to the matrix and bind it to the TextBox.
        var data = new Data();
        _matrix[row, col] = data;
        newbox.DataBindings.Add(new Binding("Text", data, "Value", true));

        Controls.Add(newbox);
    }
}

Note that binding works two way. If you initialize the matrix with numbers, they will be displayed in the textboxes when opening the form. Numbers entered in textboxes will be stored in the matrix.

Now, on the other form, you need a reference to this form. Then you can get the matrix with

double[,] matrix = frmMartixInput.Matrix;

If you have difficulties passing around form references, then use a static property in a static class for the matrix, that can be referenced by all the forms.

public static class Globals
{
    public static double[,] Matrix { get; set; }
}

You can also pass data to a form through constructor parameters (either a reference to another form or the matrix itself).

Upvotes: 1

Ryan Pierce Williams
Ryan Pierce Williams

Reputation: 1004

I'm assuming that these are not modal windows and that the user can switch between them at any point? If that is the case then I would suggest using a design pattern like MVC or MVVM, separating your data, view, and control logic. By keeping the data layer distinct from the view, you can have all of your windows (views) share the same underlying data. Of course, you'll want to use events to notify the various windows of when the data is changed (see the INotifyPropertyChanged Interface).

Upvotes: 1

Related Questions