C#

System.Threading.Thread.Sleep(5000);

using System.Threading;
Thread.Sleep(5000);

Metal76 wrote:

The main thread keeps a reference to the MyProtocol objects created, and uses the Data property to exchange data with the thread (with appropriate synchronization using lock to avoid race conditions). Is this ok? Is there any better approach?

Metal76 wrote:

Which is the correct way to shut down the connection threads?

volatile bool canContinue = true;
public void HandleClient(){
   while(canContinue){
      ......
   }
}

public void Stop(){
   canContinue = false;
}

MyProtocol protocol = new MyProtocol();
Thread thread = new Thread(new ThreadStart(protocol.HandleClient));
thread.IsBackground = true;
thread.Start();

void HandleClient()
{
   ... 

   // Block until data is available from socket or client disconnected
   while ((recvMsgSize = clntSock.Receive(rcvBuffer, 0, rcvBuffer.Length, SocketFlags.None)) > 0)
   {
       // Process received data 
       ...
   }

   // Client disconnected, return from function --> terminate thread
}

The DataGridViewComboBox must hold all possible values that it will display
in it's items collection. For example, when binding to the Customers table
and having the CompanyName field a combobox the combobox must contain all
possible values. If the grid attempts to set the cell's value where the
combobox cell doesn't have the value then we throw the dataError event.

To workaround this, handle the DataError event of the DataGridView. For
example:

void dataGridView1_DataError(object sender, DataGridViewDataErrorEventArgs
e)
{
// ignore the data error occurring under the territoryComboBoxColumn
if (e.ColumnIndex != territoryComboBoxColumn.Index)
{
MessageBox.Show("Data error occurs:" + e.Exception.Message);
}
} 

if (e.ColumnIndex != territoryComboBoxColumn.Index)
{
    MessageBox.Show("Data error occurs:" + e.Exception.Message);
    //Add user's typed input into ComboBox here
}