C# Discussion Boards - CodeProject

Steve Messer14-Dec-05 9:33

14-Dec-05 9:33

This seems to be what I am looking for.

The snipit you provided doesn't compile, but I can look up the syntax.

Judah Gabriel Himango14-Dec-05 9:38

14-Dec-05 9:38

It should compile under .NET 2.0 syntax (where delegates can be inferred from the method passed). If you're not using a C# 2.0 compiler, you'll need to explicitly create the delegates:

ThreadStart method1 = new ThreadStart(GetData1);
AsyncCallback callback = new AsyncCallback(myCallbackFunction);
method1.BeginInvoke(callback, null);

...

void MyCallbackFunction(IAsyncResult result)
{
   // GetData1 is done!
}

Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Bought a House!
Judah Himango

-- modified at 15:40 Wednesday 14th December, 2005

Steve Messer14-Dec-05 9:51

14-Dec-05 9:51

Thanks that did the trick.

Sorry, but I am still in the stone ages using .net 1.1 and Visual Studio 2003 Smile | :)

Thanks again

Steve Messer14-Dec-05 11:09

14-Dec-05 11:09

Well, it compiles but it doesn't ever call the callback function

Here is my callback function

void MyCallbackFunction(IAsyncResult result)
{   
    // GetData1 is done!}
    if( result.IsCompleted )
       MessageBox.Show( "Callback triggered");
}

Here is how I am calling it

ThreadStart method1 = new ThreadStart(RequestVehicles);
AsyncCallback callback = new AsyncCallback(MyCallbackFunction);
method1.BeginInvoke(callback, null);

Thread tThread = new Thread( method1 );
tThread.IsBackground = true;
tThread.Start();

Have I done something wrong?

-- modified at 17:19 Wednesday 14th December, 2005

Judah Gabriel Himango14-Dec-05 11:58

14-Dec-05 11:58

In that code snippet, you're calling RequestVehicles 2 times: once when you call method1.BeginInvoke method, and again when you explicitly create your Thread and call .Start on the thread. Just remove that explicit thread creation, it's redundant. Your code should look like:

ThreadStart method1 = new ThreadStart(RequestVehicles);
AsyncCallback callback = new AsyncCallback(MyCallbackFunction);
method1.BeginInvoke(callback, null);

void MyCallbackFunction(IAsyncResult result)
{   
    // GetData1 is done!}
    if( result.IsCompleted )
       MessageBox.Show( "Callback triggered");
}

Note that if you used

Thread t = ...
t.Start()

it will not call any callback method. Only BeginInvoke does that.

Steve Messer14-Dec-05 12:02

14-Dec-05 12:02

Thanks I will try that directly

WillemM14-Dec-05 9:20

WillemM

14-Dec-05 9:20

Sounds rather complex, let me think:

Every process should have some kind of semaphore. GetData2 should call wait on the semaphore of GetData1. GetData1 should call signal on the semaphore it has, so that GetData2 continues. GetData3 should call wait on the semaphore of GetData2 and GetData2 should call signal on the semaphore it has, to let GetData3 continue.

This should work just fine and you dont have to worry about a lot of the synchronisation here Smile | :)

There are other ways to do this, but this is by far the simplest solution I can think of.

WM.

What about weapons of mass-construction?

-- modified at 15:21 Wednesday 14th December, 2005 (Fixed some minor spelling issues Poke tongue | ;-P

)

Robert Rohde14-Dec-05 10:43

Robert Rohde

14-Dec-05 10:43

Although it seems you already found a solution just another question:
If those three threads get executed sequentially (one after the other) why don't you just call all three methods in a single thread?

Steve Messer14-Dec-05 11:17

14-Dec-05 11:17

Worth a look, thanks

Steve Messer14-Dec-05 16:40

Displaying a message while executing a function

14-Dec-05 16:40

I used a combination of both tips

ThreadStart method1 = new ThreadStart(DoRequests); 
AsyncCallback callback = new AsyncCallback(MyCallbackFunction);
method1.BeginInvoke(callback, null);

void DoRequests()
{
   RequestVehicles();
   RequestCustomers();
   RequestServiceSales();
}

void MyCallbackFunction(IAsyncResult result)
{
   if( result.IsCompleted )
   {
      // All data received add to database or whatever
   }
}

Thanks All

apoc50314-Dec-05 9:00

Re: Displaying a message while executing a function

14-Dec-05 9:00

I made a windows form app that executes a query to an Oracle database. It takes about 5 seconds for the query to execute. If a user presses the button and it takes 5 seconds, they might think its not working.

I want to display a message while it executes the query. The whole query is wrapped up in a function called “ConnectToOracle()”. Obviously it is of type void. I tried to make a while loop that did this…

ConnectToOracle();<br />
<br />
While (ConnectToOracle)<br />
<br />
{<br />
<br />
            Label1.visible = true;      <br />
<br />
}

It gave me an error that said cannot implicitly convert type ‘void’ to ‘bool’.

Is there anyway I can do this??

Thank you!

Apoc

Dan Neely14-Dec-05 9:08

Dan Neely

14-Dec-05 9:08

Alternately put the label display calls inside ConnectToOracle() on either side of the db operations. You should consider doing this in a seperate thread though so it doesn't lock the GUI.

<br />
void ConnectAndShowWait()<br />
{<br />
Label1.visible = true;<br />
<br />
ConnectToOracle();<br />
<br />
Label1.visible = false;<br />
}

Re: Displaying a message while executing a function

Judah Gabriel Himango14-Dec-05 9:09

Re: Displaying a message while executing a function

14-Dec-05 9:09

A while clause expects a boolean value. while(somethingIsTrueOrFalse). Since ConnectToOracle is returning void, while won't work.

What you need is a seperate thread of execution to connect to the database, keeping your UI thread alive and functional. To do this:

using System.Threading;

// Right now we're on the UI thread. Let's start another thread of execution that goes over to Oracle and reads the data.
ThreadStart methodToExecute = new ThreadStart(ConnectToOracle);
Thread oracleReaderThread = new Thread(methodToExecute);
oracleReaderThread.Start();

This will keep your UI thread responsive because it's not actually doing anything. The background oracleReaderThread will begin executing in the background.

Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Bought a House!
Judah Himango

apoc50314-Dec-05 10:24

Re: Displaying a message while executing a function

14-Dec-05 10:24

Wow! That made a huge difference! Thanks so much!

Apoc

Judah Gabriel Himango14-Dec-05 10:43

Re: Displaying a message while executing a function

14-Dec-05 10:43

Don't be fooled about speed difference. It will still take just as long (in fact, probably longer on a single-processor machine) to read the data from the database. It's just that the reading won't block your UI thread, which makes everything appear responsive & fast. Users like this. Just beware that multithreading can get very hairy; threads sharing states, threads accessing the same resource, locking & deadlocks, doing UI stuff on background threads, all are difficulties you'll run into if you use threads. I suggest you do some reading[^] on the subject.

Robert Rohde14-Dec-05 10:46

Robert Rohde

14-Dec-05 10:46

You could also display a wait cursor:

try {
Cursor.Current = Cursor.Wait;
ConnectToOracle();
} finally {
Cursor.Current = Cursor.Default;
}

Re: Displaying a message while executing a function

apoc50314-Dec-05 11:09

Re: Displaying a message while executing a function

14-Dec-05 11:09

I tried that and it said it did not recognize Wait and Default. Am I using an old version of .net? Is this only for 2.0?

Apoc

Robert Rohde14-Dec-05 11:47

Robert Rohde

14-Dec-05 11:47

No i was a just a bit too quick:

try  {
   Cursor.Current = Cursors.WaitCursor;
   ConnectToOracle();
} 
finally {
   Cursor.Current = Cursors.Default;
}

Now it should compile Smile | :)

Re: Displaying a message while executing a function

apoc50314-Dec-05 11:50