Quick Question

[Aaron1]

I'm new to VB.Net programming (and programming in general) so this is probably a really simple question.

What is the simplest way to make a piece of code wait for x amount of milliseconds before moving to the next piece of code? Thanks to whoever can help.

[Half]

The CurrentThread can do this.

System.Threading.Thread.CurrentThread.Sleep(7000)

[Atheist]

hello and welcome to the forums
Well you can either make the thread "go to sleep" using this code:

Threading.Thread.Sleep(20) 'Sleep 20 miliseconds

But I guess since you say youre new to VB you probably havnt multithreaded your application, so that line would freeze your application during the "sleep".

Another thing is to place a timer on your form and setting its interval to the amount of miliseconds to wait. Then you'd just have to set its property Enabled to True when you want to wait. In the tick event of the timer you would place timer1.enabled = false and the other code that you wanted to execute.

[jmcilhinney]

The CurrentThread can do this.

System.Threading.Thread.CurrentThread.Sleep(7000)

I just wanted to point out that this code is incorrect. It will work but only because the IDE fixes it for you when compiling. Thread.Sleep is a Shared method that pauses the current thread. It is supposed to be called on the Thread class itself, NOT on an instance of the Thread class. You don't specify the current thread because the Thread.Sleep method specifically pauses the current thread. It's not possible to pause any thread other than the current. Multi-threading is error-prone enough without allowing threads to halt each other.

[Half]

It has no choice but to work since the intellisense suggested it. Thanks for correcting me.

[jmcilhinney]

It has no choice but to work since the intellisense suggested it. Thanks for correcting me.

VS 2005 is smarter than VS.NET 2003 in that regard. 2005 would still let you write that code but it would produce a compilation warning telling you that you were accessing a Shared member incorrectly via an instance. That said, you should never call any Shared member on an instance under any circumstances.

[RobDog888]

It has no choice but to work since the intellisense suggested it. Thanks for correcting me.

But if you went this route you would have found .Sleep also. Same in 2003/2005

System.Threading.Thread.Sleep(20)