> Hi group,
>
> I have been doing some reading on threading and updating the ui from a
> worker thread and I made this sample which works but I was wondering if it's
> the ok way to do it? Can I improve something? What's the best practise for
> updating multiple controls on my form for example 5 labels or so, just keep
> passing them to the constructor?
>
> Greetz, Peter
>
> On my Form:
>
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
>         Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
>         oMyUpd.Start()
>
> End Sub
>
> 'The worker thread
>
> Imports System.Threading
>
> '======================================================================
> Public Class MyUpdater
>     Delegate Sub UpdateStarter()
>     Delegate Sub FeedBack(ByVal myValue As Integer)
>
>     Private oThread As Thread
>     Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
>
>     Private progy As ProgressBar
>     Private infoLbl As Label
>
>     Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
>         progy = myProg
>         infoLbl = myLabel
>     End Sub
>
>     Public Sub [Start]()
>         oMyUpdate.BeginInvoke(Nothing, Nothing)
>     End Sub
>
>     Public Sub StartUpdating()
>         Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
>         oThread = Thread.CurrentThread
>         For i As Integer = 0 To 15
>             progy.BeginInvoke(giveFeedBack, New Object() {i})
>             Thread.Sleep(200)
>         Next

"Patrick Steele" <patr***@mvps.org> schreef in bericht
news:MPG.1f8ecef516a550f6989689@msnews.microsoft.com...
> In article <uJLtO2F6GHA.4***@TK2MSFTNGP02.phx.gbl>,
> pproost@nospam.hotmail.com says...
> > Hi group,
> >
> > I have been doing some reading on threading and updating the ui from a
> > worker thread and I made this sample which works but I was wondering if
it's
> > the ok way to do it? Can I improve something? What's the best practise
for
> > updating multiple controls on my form for example 5 labels or so, just
keep
> > passing them to the constructor?
> >
> > Greetz, Peter
> >
> > On my Form:
> >
> > Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> > System.EventArgs) Handles Button1.Click
> >         Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
> >         oMyUpd.Start()
> >
> > End Sub
> >
> > 'The worker thread
> >
> > Imports System.Threading
> >
> > '======================================================================
> > Public Class MyUpdater
> >     Delegate Sub UpdateStarter()
> >     Delegate Sub FeedBack(ByVal myValue As Integer)
> >
> >     Private oThread As Thread
> >     Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
> >
> >     Private progy As ProgressBar
> >     Private infoLbl As Label
> >
> >     Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
> >         progy = myProg
> >         infoLbl = myLabel
> >     End Sub
> >
> >     Public Sub [Start]()
> >         oMyUpdate.BeginInvoke(Nothing, Nothing)
> >     End Sub
> >
> >     Public Sub StartUpdating()
> >         Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
> >         oThread = Thread.CurrentThread
> >         For i As Integer = 0 To 15
> >             progy.BeginInvoke(giveFeedBack, New Object() {i})
> >             Thread.Sleep(200)
> >         Next
>
> I like to keep the logic of marshalling between threads local to the
> method that is accessing the UI.  Like this (haven't coded in VB.NET in
> a while so I might be little rusty on the syntax):
>
> Public Sub IncreaseValue(ByVal myVal As Integer)
> If progy.InvokeRequired Then
> progy.Invoke(New Feedback(AddressOf IncreaseValue), _
> new Object() {i})
> return
> end if
>
> progy.Value = myVal
> infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
> end sub
>
> Now you just need to call IncreaseValue directly in your
> "StartUpdating" method -- you don't need the multithreading stuff in
> your loop code.
>
> This also has the benefit that if you ever move this method into the UI
> thread, the "progy.InvokeRequired" will return false and you'll update
> the control right away -- no need to use Invoke.  While it's not a huge
> expense to call Invoke, why call it when you don't have to?  :)
>
> --
> Patrick Steele
> http://weblogs.asp.net/psteele

"Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
news:eE57sNI6GHA.3508@TK2MSFTNGP06.phx.gbl...
> Hi,
>
> Thanks for the explanation
>
> Greetz Peter
>
> --
> Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>
> "Patrick Steele" <patr***@mvps.org> schreef in bericht
> news:MPG.1f8ecef516a550f6989689@msnews.microsoft.com...
> > In article <uJLtO2F6GHA.4***@TK2MSFTNGP02.phx.gbl>,
> > pproost@nospam.hotmail.com says...
> > > Hi group,
> > >
> > > I have been doing some reading on threading and updating the ui from a
> > > worker thread and I made this sample which works but I was wondering
if
> it's
> > > the ok way to do it? Can I improve something? What's the best practise
> for
> > > updating multiple controls on my form for example 5 labels or so, just
> keep
> > > passing them to the constructor?
> > >
> > > Greetz, Peter
> > >
> > > On my Form:
> > >
> > > Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> > > System.EventArgs) Handles Button1.Click
> > >         Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
> > >         oMyUpd.Start()
> > >
> > > End Sub
> > >
> > > 'The worker thread
> > >
> > > Imports System.Threading
> > >
> > >
'======================================================================
> > > Public Class MyUpdater
> > >     Delegate Sub UpdateStarter()
> > >     Delegate Sub FeedBack(ByVal myValue As Integer)
> > >
> > >     Private oThread As Thread
> > >     Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
> > >
> > >     Private progy As ProgressBar
> > >     Private infoLbl As Label
> > >
> > >     Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As
Label)
> > >         progy = myProg
> > >         infoLbl = myLabel
> > >     End Sub
> > >
> > >     Public Sub [Start]()
> > >         oMyUpdate.BeginInvoke(Nothing, Nothing)
> > >     End Sub
> > >
> > >     Public Sub StartUpdating()
> > >         Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
> > >         oThread = Thread.CurrentThread
> > >         For i As Integer = 0 To 15
> > >             progy.BeginInvoke(giveFeedBack, New Object() {i})
> > >             Thread.Sleep(200)
> > >         Next
> >
> > I like to keep the logic of marshalling between threads local to the
> > method that is accessing the UI.  Like this (haven't coded in VB.NET in
> > a while so I might be little rusty on the syntax):
> >
> > Public Sub IncreaseValue(ByVal myVal As Integer)
> > If progy.InvokeRequired Then
> > progy.Invoke(New Feedback(AddressOf IncreaseValue), _
> > new Object() {i})
> > return
> > end if
> >
> > progy.Value = myVal
> > infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
> > end sub
> >
> > Now you just need to call IncreaseValue directly in your
> > "StartUpdating" method -- you don't need the multithreading stuff in
> > your loop code.
> >
> > This also has the benefit that if you ever move this method into the UI
> > thread, the "progy.InvokeRequired" will return false and you'll update
> > the control right away -- no need to use Invoke.  While it's not a huge
> > expense to call Invoke, why call it when you don't have to?  :)
> >
> > --
> > Patrick Steele
> > http://weblogs.asp.net/psteele
>
>

> Just to make sure, is this what you mean?
>
> Public Sub StartUpdating()
>         Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
>         oThread = Thread.CurrentThread
>         For i As Integer = 0 To 15
>             IncreaseValue(i)
>             Thread.Sleep(200)
>         Next
>
>     End Sub
>
>     Public Sub IncreaseValue(ByVal myVal As Integer)
>         If progy.InvokeRequired Then
>             progy.Invoke(New FeedBack(AddressOf IncreaseValue), New Object()
> {myVal})
>             Return
>         End If
>
>         progy.Value = myVal
>         infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
>     End Sub
>
> Greetz Peter

"Patrick Steele" <patr***@mvps.org> schreef in bericht
news:MPG.1f8edb7eed4df8ff989694@msnews.microsoft.com...
>
> Yup.  And you can get rid of the giveFeedback variable in StartUpdating
> since you're no longer using it.
>
> In article <OCjJ5PI6GHA.4***@TK2MSFTNGP04.phx.gbl>,
> pproost@nospam.hotmail.com says...
> > Just to make sure, is this what you mean?
> >
> > Public Sub StartUpdating()
> >         Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
> >         oThread = Thread.CurrentThread
> >         For i As Integer = 0 To 15
> >             IncreaseValue(i)
> >             Thread.Sleep(200)
> >         Next
> >
> >     End Sub
> >
> >     Public Sub IncreaseValue(ByVal myVal As Integer)
> >         If progy.InvokeRequired Then
> >             progy.Invoke(New FeedBack(AddressOf IncreaseValue), New
Object()
> > {myVal})
> >             Return
> >         End If
> >
> >         progy.Value = myVal
> >         infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
> >     End Sub
> >
> > Greetz Peter
>
> --
> Patrick Steele
> http://weblogs.asp.net/psteele

"Patrick Steele" <patr***@mvps.org> schreef in bericht
news:MPG.1f8f64d510f23690989699@msnews.microsoft.com...
> In article <#92NwtI6GHA.1***@TK2MSFTNGP03.phx.gbl>,
> pproost@nospam.hotmail.com says...
> > Thanks again, and one more question do you maybe have some good links
for
> > reading up some more on multi threading and ui or just multi threading.
>
> No, sorry.  Nothing bookmarked.
>
> --
> Patrick Steele
> http://weblogs.asp.net/psteele

"Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
news:uJLtO2F6GHA.4572@TK2MSFTNGP02.phx.gbl...
> Hi group,
>
> I have been doing some reading on threading and updating the ui from a
> worker thread and I made this sample which works but I was wondering if
> it's
> the ok way to do it? Can I improve something? What's the best practise for
> updating multiple controls on my form for example 5 labels or so, just
> keep
> passing them to the constructor?
>
> Greetz, Peter
>
> On my Form:
>
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
>        Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
>        oMyUpd.Start()
>
> End Sub
>
> 'The worker thread
>
> Imports System.Threading
>
> '======================================================================
> Public Class MyUpdater
>    Delegate Sub UpdateStarter()
>    Delegate Sub FeedBack(ByVal myValue As Integer)
>
>    Private oThread As Thread
>    Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
>
>    Private progy As ProgressBar
>    Private infoLbl As Label
>
>    Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
>        progy = myProg
>        infoLbl = myLabel
>    End Sub
>
>    Public Sub [Start]()
>        oMyUpdate.BeginInvoke(Nothing, Nothing)
>    End Sub
>
>    Public Sub StartUpdating()
>        Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
>        oThread = Thread.CurrentThread
>        For i As Integer = 0 To 15
>            progy.BeginInvoke(giveFeedBack, New Object() {i})
>            Thread.Sleep(200)
>        Next
>
>    End Sub
>
>    Public Sub IncreaseValue(ByVal myVal As Integer)
>        progy.Value = myVal
>        infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
>    End Sub
>
>
> End Class
>
> --
> Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>
>

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schreef in bericht
news:#UGgJ0P6GHA.4276@TK2MSFTNGP04.phx.gbl...
> Peter,
>
> I have no time to test your code, however the Queue class is in my idea
> greath to use for multithreading.
>
> You can use an thrown back event or just a timer in your mainthread to see
> if that is filled and empty it while using the synclock. Mostly you see a
> lot of in my eyes more dificult solutions.
>
> http://msdn2.microsoft.com/en-us/library/system.collections.queue.aspx
>
> http://msdn2.microsoft.com/en-us/library/3a86s51t.aspx
>
> Jon Skeet has written a complete page about Multithreading, however in my
> eyes he wants to use multithreading to often, there are very few
situations
> where there is no dependency or another reason that using multithreading
has
> sense (The only reason I see here often stated is to keep the X (end)
button
> alive. In my idea is that the horse behind the cart. You should make your
> application faster).
>
> (It has only sense as an offline supplier needs more time and you can
spread
> the proces. By instance if you are downloading and you have a speed of
64Kb
> and your supplier 20Gb, than multithreading is whithouth sense. In the
> oposite way it can make sense if you are downloading from suppliers which
> have all 64Kb lines and you have 20Gb. However in Belgium is the avarage
> speed of Internet lines so high that this makes probably as well no
sense).
>
> http://www.yoda.arachsys.com/csharp/
>
> I hope this gives some ideas,
>
> Cor
>
>
>
>
>
>
>
>
> "Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
> news:uJLtO2F6GHA.4572@TK2MSFTNGP02.phx.gbl...
> > Hi group,
> >
> > I have been doing some reading on threading and updating the ui from a
> > worker thread and I made this sample which works but I was wondering if
> > it's
> > the ok way to do it? Can I improve something? What's the best practise
for
> > updating multiple controls on my form for example 5 labels or so, just
> > keep
> > passing them to the constructor?
> >
> > Greetz, Peter
> >
> > On my Form:
> >
> > Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> > System.EventArgs) Handles Button1.Click
> >        Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
> >        oMyUpd.Start()
> >
> > End Sub
> >
> > 'The worker thread
> >
> > Imports System.Threading
> >
> > '======================================================================
> > Public Class MyUpdater
> >    Delegate Sub UpdateStarter()
> >    Delegate Sub FeedBack(ByVal myValue As Integer)
> >
> >    Private oThread As Thread
> >    Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
> >
> >    Private progy As ProgressBar
> >    Private infoLbl As Label
> >
> >    Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
> >        progy = myProg
> >        infoLbl = myLabel
> >    End Sub
> >
> >    Public Sub [Start]()
> >        oMyUpdate.BeginInvoke(Nothing, Nothing)
> >    End Sub
> >
> >    Public Sub StartUpdating()
> >        Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
> >        oThread = Thread.CurrentThread
> >        For i As Integer = 0 To 15
> >            progy.BeginInvoke(giveFeedBack, New Object() {i})
> >            Thread.Sleep(200)
> >        Next
> >
> >    End Sub
> >
> >    Public Sub IncreaseValue(ByVal myVal As Integer)
> >        progy.Value = myVal
> >        infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
> >    End Sub
> >
> >
> > End Class
> >
> > --
> > Programming today is a race between software engineers striving to build
> > bigger and better idiot-proof programs, and the Universe trying to
produce
> > bigger and better idiots. So far, the Universe is winning. (Rich Cook)
> >
> >
>
>

"Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
news:%235u2fbR6GHA.756@TK2MSFTNGP05.phx.gbl...
> Hi Cor, thanks for your explanation. What I'm doing is writing in import
> module from foxpro to vb.net, but I can't write entirely on the
> server-side
> because a lot of conversions and a bad table structure in foxpro (no
> primary
> keys), maybe it's possible to write it server-side but it's a lot easier
> to
> write it in vb.net. A user can start this import and it runs for 5 minutes
> or so for 20000 records. The problem ofcourse was the ui freezing, so I
> used
> Dim t As New Threading.Thread(AddressOf ImportModule)
> t.Start()
>
> and this got me interested in multithreading so I started reading up on
> it.
> I don't actualy plan on using it in this scenario as the method I now use
> seems ok to me. Do you see something wrong with it? Would you advise an
> other way?
>
> Greetz Peter
>
> --
> Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>
> "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schreef in bericht
> news:#UGgJ0P6GHA.4276@TK2MSFTNGP04.phx.gbl...
>> Peter,
>>
>> I have no time to test your code, however the Queue class is in my idea
>> greath to use for multithreading.
>>
>> You can use an thrown back event or just a timer in your mainthread to
>> see
>> if that is filled and empty it while using the synclock. Mostly you see a
>> lot of in my eyes more dificult solutions.
>>
>> http://msdn2.microsoft.com/en-us/library/system.collections.queue.aspx
>>
>> http://msdn2.microsoft.com/en-us/library/3a86s51t.aspx
>>
>> Jon Skeet has written a complete page about Multithreading, however in my
>> eyes he wants to use multithreading to often, there are very few
> situations
>> where there is no dependency or another reason that using multithreading
> has
>> sense (The only reason I see here often stated is to keep the X (end)
> button
>> alive. In my idea is that the horse behind the cart. You should make your
>> application faster).
>>
>> (It has only sense as an offline supplier needs more time and you can
> spread
>> the proces. By instance if you are downloading and you have a speed of
> 64Kb
>> and your supplier 20Gb, than multithreading is whithouth sense. In the
>> oposite way it can make sense if you are downloading from suppliers which
>> have all 64Kb lines and you have 20Gb. However in Belgium is the avarage
>> speed of Internet lines so high that this makes probably as well no
> sense).
>>
>> http://www.yoda.arachsys.com/csharp/
>>
>> I hope this gives some ideas,
>>
>> Cor
>>
>>
>>
>>
>>
>>
>>
>>
>> "Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
>> news:uJLtO2F6GHA.4572@TK2MSFTNGP02.phx.gbl...
>> > Hi group,
>> >
>> > I have been doing some reading on threading and updating the ui from a
>> > worker thread and I made this sample which works but I was wondering if
>> > it's
>> > the ok way to do it? Can I improve something? What's the best practise
> for
>> > updating multiple controls on my form for example 5 labels or so, just
>> > keep
>> > passing them to the constructor?
>> >
>> > Greetz, Peter
>> >
>> > On my Form:
>> >
>> > Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
>> > System.EventArgs) Handles Button1.Click
>> >        Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
>> >        oMyUpd.Start()
>> >
>> > End Sub
>> >
>> > 'The worker thread
>> >
>> > Imports System.Threading
>> >
>> > '======================================================================
>> > Public Class MyUpdater
>> >    Delegate Sub UpdateStarter()
>> >    Delegate Sub FeedBack(ByVal myValue As Integer)
>> >
>> >    Private oThread As Thread
>> >    Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
>> >
>> >    Private progy As ProgressBar
>> >    Private infoLbl As Label
>> >
>> >    Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
>> >        progy = myProg
>> >        infoLbl = myLabel
>> >    End Sub
>> >
>> >    Public Sub [Start]()
>> >        oMyUpdate.BeginInvoke(Nothing, Nothing)
>> >    End Sub
>> >
>> >    Public Sub StartUpdating()
>> >        Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
>> >        oThread = Thread.CurrentThread
>> >        For i As Integer = 0 To 15
>> >            progy.BeginInvoke(giveFeedBack, New Object() {i})
>> >            Thread.Sleep(200)
>> >        Next
>> >
>> >    End Sub
>> >
>> >    Public Sub IncreaseValue(ByVal myVal As Integer)
>> >        progy.Value = myVal
>> >        infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
>> >    End Sub
>> >
>> >
>> > End Class
>> >
>> > --
>> > Programming today is a race between software engineers striving to
>> > build
>> > bigger and better idiot-proof programs, and the Universe trying to
> produce
>> > bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>> >
>> >
>>
>>
>
>

"Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
news:%235u2fbR6GHA.756@TK2MSFTNGP05.phx.gbl...
> Hi Cor, thanks for your explanation. What I'm doing is writing in import
> module from foxpro to vb.net, but I can't write entirely on the
> server-side
> because a lot of conversions and a bad table structure in foxpro (no
> primary
> keys), maybe it's possible to write it server-side but it's a lot easier
> to
> write it in vb.net. A user can start this import and it runs for 5 minutes
> or so for 20000 records. The problem ofcourse was the ui freezing, so I
> used
> Dim t As New Threading.Thread(AddressOf ImportModule)
> t.Start()
>
> and this got me interested in multithreading so I started reading up on
> it.
> I don't actualy plan on using it in this scenario as the method I now use
> seems ok to me. Do you see something wrong with it? Would you advise an
> other way?
>
> Greetz Peter
>
> --
> Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>
> "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schreef in bericht
> news:#UGgJ0P6GHA.4276@TK2MSFTNGP04.phx.gbl...
>> Peter,
>>
>> I have no time to test your code, however the Queue class is in my idea
>> greath to use for multithreading.
>>
>> You can use an thrown back event or just a timer in your mainthread to
>> see
>> if that is filled and empty it while using the synclock. Mostly you see a
>> lot of in my eyes more dificult solutions.
>>
>> http://msdn2.microsoft.com/en-us/library/system.collections.queue.aspx
>>
>> http://msdn2.microsoft.com/en-us/library/3a86s51t.aspx
>>
>> Jon Skeet has written a complete page about Multithreading, however in my
>> eyes he wants to use multithreading to often, there are very few
> situations
>> where there is no dependency or another reason that using multithreading
> has
>> sense (The only reason I see here often stated is to keep the X (end)
> button
>> alive. In my idea is that the horse behind the cart. You should make your
>> application faster).
>>
>> (It has only sense as an offline supplier needs more time and you can
> spread
>> the proces. By instance if you are downloading and you have a speed of
> 64Kb
>> and your supplier 20Gb, than multithreading is whithouth sense. In the
>> oposite way it can make sense if you are downloading from suppliers which
>> have all 64Kb lines and you have 20Gb. However in Belgium is the avarage
>> speed of Internet lines so high that this makes probably as well no
> sense).
>>
>> http://www.yoda.arachsys.com/csharp/
>>
>> I hope this gives some ideas,
>>
>> Cor
>>
>>
>>
>>
>>
>>
>>
>>
>> "Peter Proost" <pproost@nospam.hotmail.com> schreef in bericht
>> news:uJLtO2F6GHA.4572@TK2MSFTNGP02.phx.gbl...
>> > Hi group,
>> >
>> > I have been doing some reading on threading and updating the ui from a
>> > worker thread and I made this sample which works but I was wondering if
>> > it's
>> > the ok way to do it? Can I improve something? What's the best practise
> for
>> > updating multiple controls on my form for example 5 labels or so, just
>> > keep
>> > passing them to the constructor?
>> >
>> > Greetz, Peter
>> >
>> > On my Form:
>> >
>> > Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
>> > System.EventArgs) Handles Button1.Click
>> >        Dim oMyUpd As New MyUpdater(ProgressBar1, lblPct)
>> >        oMyUpd.Start()
>> >
>> > End Sub
>> >
>> > 'The worker thread
>> >
>> > Imports System.Threading
>> >
>> > '======================================================================
>> > Public Class MyUpdater
>> >    Delegate Sub UpdateStarter()
>> >    Delegate Sub FeedBack(ByVal myValue As Integer)
>> >
>> >    Private oThread As Thread
>> >    Private oMyUpdate As New UpdateStarter(AddressOf StartUpdating)
>> >
>> >    Private progy As ProgressBar
>> >    Private infoLbl As Label
>> >
>> >    Public Sub New(ByVal myProg As ProgressBar, ByVal myLabel As Label)
>> >        progy = myProg
>> >        infoLbl = myLabel
>> >    End Sub
>> >
>> >    Public Sub [Start]()
>> >        oMyUpdate.BeginInvoke(Nothing, Nothing)
>> >    End Sub
>> >
>> >    Public Sub StartUpdating()
>> >        Dim giveFeedBack As New FeedBack(AddressOf IncreaseValue)
>> >        oThread = Thread.CurrentThread
>> >        For i As Integer = 0 To 15
>> >            progy.BeginInvoke(giveFeedBack, New Object() {i})
>> >            Thread.Sleep(200)
>> >        Next
>> >
>> >    End Sub
>> >
>> >    Public Sub IncreaseValue(ByVal myVal As Integer)
>> >        progy.Value = myVal
>> >        infoLbl.Text = CStr(Math.Round(myVal / progy.Maximum * 100, 2))
>> >    End Sub
>> >
>> >
>> > End Class
>> >
>> > --
>> > Programming today is a race between software engineers striving to
>> > build
>> > bigger and better idiot-proof programs, and the Universe trying to
> produce
>> > bigger and better idiots. So far, the Universe is winning. (Rich Cook)
>> >
>> >
>>
>>
>
>