Comments for valerio.net

Comment on ThreadPool.QueueUserWorkItem With Multiple Arguments by Shaun Bowe

Shaun Bowe — Wed, 01 Feb 2012 20:01:29 +0000

Nice work!

Comment on A Queued BackgroundWorker Using Generic Delegates by steve

steve — Mon, 19 Dec 2011 23:54:15 +0000

Thanks for this article. I have a question. I would like to pass a function that takes in parameter, but in the argument line it doesn’t allow you to pass parameter as it is a Action of T Implementation. I need my argument to be readily available so when the worker get to my item function it knows the object. How would i do that?

Comment on A Queued BackgroundWorker Using Generic Delegates by Nanda

Nanda — Wed, 07 Dec 2011 14:32:24 +0000

Hi,

Good article, I tried to reproduce this with ReportProgress too, but getting cross-thread exception (InvalidOperationException), can you update with a ReportProgress option too please?

Thanks,
Nanda

Comment on Use ThreadPool.QueueUserWorkItem With Anonymous Types by Iskren Ivanov

Iskren Ivanov — Fri, 25 Nov 2011 10:09:22 +0000

Instead your own InputData class, you can simply use arrays.

Comment on Recursion in F# and the Tail Recursion Police by Using a DataReader like a List in F#

Using a DataReader like a List in F# — Sat, 08 Oct 2011 00:21:23 +0000

[...] not making a tail call. F# uses a technique called Tail Call Optimization (TCO, explained here, here and here) to make code run more efficiently. Basically, what that does is take a recursive function [...]

Comment on Use ThreadPool.QueueUserWorkItem With Anonymous Types by flippster

flippster — Wed, 21 Sep 2011 14:09:42 +0000

This is a very nice article. I just wanted to point out that you could also use reflection to get at your type information from within the thread

var blah = new { One = “heheh”, Two= 1234 };

ThreadPool.QueueUserWorkItem(new WaitCallback(ThreadFire), blah);

static void ThreadFire(object objInput)
{
Lets use reflection
Type t = objInput.GetType();

// Get OPC Client property
PropertyInfo p1 = t.GetProperty(“One”);
var one_ = (string)p1.GetValue(objInput, null);

// Get Tag Name property
PropertyInfo p2 = t.GetProperty(“Two”);
var tagName = (int)p2.GetValue(objInput, null);
}

Comment on Use ThreadPool.QueueUserWorkItem With Anonymous Types by flippster

flippster — Wed, 21 Sep 2011 14:08:58 +0000

var blah = new { One = “heheh”, Two= 1234 };

ThreadPool.QueueUserWorkItem(new WaitCallback(ThreadFire), blah);

static void ThreadFire(object objInput)
{
Lets use reflection
Type t = objInput.GetType();

// Get OPC Client property
PropertyInfo p1 = t.GetProperty(“One”);
var one_ = (string)p1.GetValue(objInput, null);

// Get Tag Name property
PropertyInfo p2 = t.GetProperty(“Two”);
var tagName = (int)p2.GetValue(objInput, null);
}

Comment on A Queued BackgroundWorker Using Generic Delegates by Target-Tracking with the Kinect, Part 3 – Target Tracking Improved, and Speech Recognition « Mark Gilbert’s Blog

Sun, 11 Sep 2011 03:36:02 +0000

[...] What I found was an unbelievably perfect solution from Matt Valerio with his post titled "A Queued BackgroundWorker Using Generic Delegates". As the title suggests, he wrote a class called “QueuedBackgroundWorker” that would add [...]

Comment on Use ThreadPool.QueueUserWorkItem With Anonymous Types by pepepaco

pepepaco — Thu, 18 Aug 2011 23:21:38 +0000

the easiest way to notify the main thread is to pass an Action parmeter along with the data parameters besides the Action to be executed. for example:

ThreadPoolHelper.QueueUserWorkItem(
new { Name = “Matt”, Age = 26, CallbackWhendone = ExecWhendone },
(data) =>
{
string name = data.Name;
int age = data.Age;
// Long-running computation
data.CallbackWhendone();
});

//where ExecWhendone is the method to be called when the calculation is done.(I have not tested it)

Comment on ThreadPool.QueueUserWorkItem With Multiple Arguments by Khayralla

Khayralla — Tue, 10 May 2011 16:19:39 +0000

Greate job, but Action can take four parameters only.
How can you define QueueUserWorkItem with 5 parameters.
Thank you.