Question

I wrote some C# code and in it I initiate a class by placing it in its own thread so it doesnt freeze up my GUI from where I initiate it:

This is from my Form Class:

    Execute_Recipe execute;
    execute = new Execute_Recipe(XCoordinatesList, YCoordinatesList, Zref, Voltref,
              widget, record, filename);
    Thread executethread = new Thread(new ThreadStart(execute.RunRecipe));

And then in my Execute Class I create a new class to record the data. This is from my execute class:

    record1 = new Record_Recipe(XCoordinateList1, YCoordinateList1, Zref1, Voltref1, filename1);

And finally in my record class I send the data to a new form. To be displayd. So in the end all of the sub classes I initiate are all created within this thread. I know the structure is absolutley crazy right now, the software is deep in its development stage, but here is my question:

How can I keep BOTH Form Classes in their own threads while having all the execution and recording of my procedure in its own thread?

Do I create 1 thread for my execution, 1 thread for my recording, and a backgrounworker for my displaying? and then talk between threads? (from what I understand talking between threads is not easy)

I am only an intermediate programmer at best and I thank you in advance if you able / willing to help with this problem.

Answer 1

Talking between threads is very easy in C#

            yourform.BeginInvoke((MethodInvoker)delegate()
            {
                yourform.button.Text = "new label";
                //More stuff here
            });

kind of construct can be used from a worker thread to updated the UI thread. If you are creating lot of non UI threads that have smaller lifetime consider using a ThreadPool instead.

For simple ui updates also look at INotifyPropertyChanged that lets you updated data bound controls easily.