[vsemwal]

Here Code how to access window main form control from child thread

Let we have label in main form and we want to update this label by next thread not by current thread

code here
declare delegate

delegate void Setlabel(string label);

call method

private void SetTextlabel(string label)
        {
            if (this.textBox1.InvokeRequired)
            {
                Setlabel d = new Setlabel(SetTextlabel);
                this.Invoke(d, new object[] { label });
            }
            else
            {
                this.lb_text.Text = label;
            }
        }

now pass test to label by calling
setTextlable("Vinay Bhaskar Semwal");

Vijay Bhaskar Semwal
Visiting faculty
Madhaya Pradesh Technical University

MOD EDIT: When posting code...USE CODE TAGS!!!

This post has been edited by JackOfAllTrades: 03 February 2011 - 05:46 AM

[JackOfAllTrades]

We have a tutorial if you'd bothered to search. You'd think someone on a university's FACULTY would know how to do this. Explains a lot I guess.

[vsemwal]

How to Update control of main window form in another thread

using System;
using System.Collections.Generic;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Tcp;
using System.Threading;
using Utility;
using Common;


namespace TwoExe
{
public delegate Setlabel;
    public partial class bhaskar : Form
    {
               
        Marshal m;
        public string url = "tcp://localhost:4444/Marshal";
        string res;
        
        public bhaskar()
        {
            InitializeComponent(); 
        }

        private void Form1_Load(object sender, EventArgs e)
        {
/* run another thread child thread 
            Thread serverRun = new Thread(new ThreadStart(server));
            serverRun.Start();
            //server();
            
        }
        public void server()
        {
/...using >net remoting
            TcpChannel channel = new TcpChannel(3331);
            if (ChannelServices.GetChannel(channel.ChannelName) == null)
                ChannelServices.RegisterChannel(channel);
             m = new Marshal();
            RemotingServices.Marshal(m, "Marshal");
            res = m.result();

//..now updating lable of main form
            SetTextlabel(res);
        }
        public void SetTextlabel(string label)
        {
            if (this.label1.InvokeRequired)
            {
                Setlabel d = new Setlabel(SetTextlabel);
                this.Invoke(d, new object[] { label });
            }
            else
            {
                this.label1.Text = label;
            }
        }
}

Vijay Bhaskar Semwal
B.tech.+M.tech.
Software Engineer
Visiting Faculty
Madhaya Pradesh Technical University

[CodingSup3rnatur@l-360]

Have a look at this code snippet also:

http://www.dreaminco...snippet3288.htm

This question has been asked at least 2 billion times across the Internet. Have a look around and see what you find . Your on the right lines though...

This post has been edited by CodingSup3rnatur@l-360: 03 February 2011 - 07:35 AM

[eclipsed4utoo]

Change this..

this.Invoke(d, new object[] { label });

to this....

label1.BeginInvoke(d, new object[] { label });

[tlhIn`toq]

JackOfAllTrades, on 03 February 2011 - 05:47 AM, said:

.... You'd think someone on a university's FACULTY would know how to do this. Explains a lot I guess.

If I could +25 you for that I would

[Curtis Rutland]

I'm not sure these were questions. I think these were attempted tutorials.

[tlhIn`toq]

insertAlias, on 03 February 2011 - 10:03 AM, said:

I'm not sure these were questions. I think these were attempted tutorials.

Really? You think this was meant to be a tutorial and not a cry for help?
Given how many problems were fixed for the OP ... I just don't know what to think.
Let's see... we already have good tutorials for the topic. This 'tutorial' was riddled with errors. Wasn't in the right section. Didn't use code tags. Was barely in English. Didn't make it's purpose clear.

vsemwal: If this was meant to be a tutorial and not a question needing help...

• Hold off on future tutorials until you get some more experience.
  
• After that, check to see if there is even an need (Read as "See if there is already a tutorial for the topic")
  
• Check that your code actually works.
  
• Explain your intent a LOT better.

[JackOfAllTrades]

You may be right, but without further input from the OP, how are we to know?

I can't even tell what this is supposed to do. Is it incomplete? Why are there unnecessary member variables? It has unknown usings. Marshal seems to be an abstract class, unless that's part of the ancillary assemblies that aren't included, which may be because System.Runtime.InteropServices is not part of the equation.

WTH?

[Curtis Rutland]

The reason I think it's an attempted tutorial is that there's never any attempt to actually ask a question. Just a statement, code, and signature. I never said it wasn't a really crappy attempt though.

@Eclipsed, why change Invoke to BeginInvoke? The only difference is sync vs. async. Neither should actually be an issue.

[tlhIn`toq]

insertAlias, on 03 February 2011 - 10:31 AM, said:

The reason I think it's an attempted tutorial is that there's never any attempt to actually ask a question. Just a statement, code, and signature. I never said it wasn't a really crappy attempt though.

@Eclipsed, why change Invoke to BeginInvoke? The only difference is sync vs. async. Neither should actually be an issue.

The more I re-read it, the more I think you're right.

Quote

Here Code how to access window main form control from child thread

Let we have label in main form and we want to update this label by next thread not by current thread

code here
declare delegate

delegate void Setlabel(string label);

call method

now pass test to label by calling
setTextlable("Vinay Bhaskar Semwal");

It does sound like a set of steps to follow - in REALLY bad English

[eclipsed4utoo]

insertAlias, on 03 February 2011 - 01:31 PM, said:

The reason I think it's an attempted tutorial is that there's never any attempt to actually ask a question. Just a statement, code, and signature. I never said it wasn't a really crappy attempt though.

@Eclipsed, why change Invoke to BeginInvoke? The only difference is sync vs. async. Neither should actually be an issue.

I actually ran into an issue using Invoke. My application was throwing an exception(can't remember what it was), and when I looked it up, it was directly connected to using Invoke. After moving it to BeginInvoke, I never had the issue again.

[tlhIn`toq]

eclipsed4utoo, on 03 February 2011 - 10:50 AM, said:

insertAlias, on 03 February 2011 - 01:31 PM, said:

The reason I think it's an attempted tutorial is that there's never any attempt to actually ask a question. Just a statement, code, and signature. I never said it wasn't a really crappy attempt though.

@Eclipsed, why change Invoke to BeginInvoke? The only difference is sync vs. async. Neither should actually be an issue.

I actually ran into an issue using Invoke. My application was throwing an exception(can't remember what it was), and when I looked it up, it was directly connected to using Invoke. After moving it to BeginInvoke, I never had the issue again.

Personally I don't like doing the Invoke thing at all. It still means that thread B has to know about the controls on form A and try to directly affect them. That's just not right. Thread B should raise an event saying "I've done x" and any subscribed threads or forms should do their own response internally. I just don't see why someone would tightly bind two threads/controls like that.

[eclipsed4utoo]

tlhIn, on 03 February 2011 - 02:00 PM, said:

eclipsed4utoo, on 03 February 2011 - 10:50 AM, said:

insertAlias, on 03 February 2011 - 01:31 PM, said:

The reason I think it's an attempted tutorial is that there's never any attempt to actually ask a question. Just a statement, code, and signature. I never said it wasn't a really crappy attempt though.

@Eclipsed, why change Invoke to BeginInvoke? The only difference is sync vs. async. Neither should actually be an issue.

I actually ran into an issue using Invoke. My application was throwing an exception(can't remember what it was), and when I looked it up, it was directly connected to using Invoke. After moving it to BeginInvoke, I never had the issue again.

Personally I don't like doing the Invoke thing at all. It still means that thread B has to know about the controls on form A and try to directly affect them. That's just not right. Thread B should raise an event saying "I've done x" and any subscribed threads or forms should do their own response internally. I just don't see why someone would tightly bind two threads/controls like that.

And I would do that now, but this app was written over 3 years ago(VS2005 and .Net 2.0), so back then, I had just learned about threading(and knew nothing about events).

[Curtis Rutland]

tlhIn, on 03 February 2011 - 12:00 PM, said:

Personally I don't like doing the Invoke thing at all. It still means that thread B has to know about the controls on form A and try to directly affect them. That's just not right. Thread B should raise an event saying "I've done x" and any subscribed threads or forms should do their own response internally. I just don't see why someone would tightly bind two threads/controls like that.

Well, for the most part, you're right. Except when the event comes from another thread, the call still has to be invoked on the main thread.

But the way to do it properly is not to have the side thread do the invoking, but to have the control do the invoke itself if required. So the outside event is raised, triggering the handler on the current form, but on a different thread. The control that is being updated checks to see if an invoke is required, and if so, invokes. Otherwise, it just sets its value.