C#

Globals.ThisDocument.CheckSpelling(
    ref missing, ref ignoreUppercase, ref missing, ref missing, ref missing, ref missing,
    ref missing, ref missing, ref missing, ref missing, ref missing, ref missing);

Foothill wrote:

all objects are passed by reference

Richard Deeming wrote:

I believe it's equivalent to passing either a * (by value) or a ** (by ref) parameter.

void func(const object* obj)

void func(object* const obj)

void func(const object* const obj)

public Form1()
{
    InitializeComponent();

    var d = new List<Tuple<string, int>>() {
        new Tuple<string, int>("test1", 12),
        new Tuple<string, int>("test2", 16),
        new Tuple<string, int>("test3", 20)
    };
    dataGridView1.AutoGenerateColumns = true;
    dataGridView1.EditMode = DataGridViewEditMode.EditOnKeystrokeOrF2;
    dataGridView1.DataSource = d;
    dataGridView1.CellValidating += dataGridView1_CellValidating;
}

void dataGridView1_CellValidating(object sender, DataGridViewCellValidatingEventArgs e)
{
    e.Cancel = false;
    MessageBox.Show(string.Format("CellValidating {0}, {1}", e.RowIndex, e.ColumnIndex));
}

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

if (this.ActiveControl.Equals(sender)) return;  //prevent the validation begin unexpectedly.

Member 13070736 wrote:

that seems like way too much effort just to slot an array into textboxes.

Quote:

The need for a collection of TextBox Controls functioning as a kind of logical unit for inputting/validating a set of data is very common. I prefer to implement this in a UserControl (or Panel) that implements validation, provides options for either sequential entry, random entry, etc. ... or, in a Form shown as a Dialog.

using System;
using System.Collections.Specialized;
using System.Windows.Forms;
using System.Collections.ObjectModel;

namespace YourNameSpace
{
    public class MapIntsToTextBoxes : ObservableCollection<int>
    {
        public MapIntsToTextBoxes(params int[] ints)
        {
            // initialize the collection
            foreach (int i in ints)
            {
                this.Add(i);
            } 
        }
    }
}

using System;
using System.Collections.Specialized;
using System.Windows.Forms;
using YourNameSpace;

namespace YourWinFormProject
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
        }

        private List<TextBox> TBoxes = new List<TBoxes>{
            textBox10,
            textBox11,
            textBox12,
            textBox13,
            textBox14
        };

        // construct and initialize
        private MapIntsToTextBoxes mapper = new MapIntsToTextBoxes(1,2,3,4,5);

        private void Form1_Load(object sender, System.EventArgs e)
        {
            mapper.CollectionChanged += MapperOnCollectionChanged;

            // change a vakue
            mapper[3] = 1000;
        }

        private void MapperOnCollectionChanged(object sender, NotifyCollectionChangedEventArgs e)
        {
            switch (e.Action)
            {
                case NotifyCollectionChangedAction.Replace:
                    TBoxes[e.OldStartingIndex].Text = e.NewItems[0].ToString();
                    break;
                case NotifyCollectionChangedAction.Add:
                    break;
                case NotifyCollectionChangedAction.Remove:
                    break;
                case NotifyCollectionChangedAction.Move:
                    break;
                case NotifyCollectionChangedAction.Reset:
                    break;
            }
        }
    }
}

Member 13070736 wrote:

that seems like way too much effort just to slot an array into textboxes.

Luc Pattyn wrote:

When your user interface requires a large number of Controls you probably should rethink your design

Luc Pattyn wrote:

Of course having several TextBoxes isn't automatically wrong, or bad design; it may even be the right choice. Showing code for five, plus ellipsis, made me produce a warning.