Loop not behaving as expected

S

StrandElectric

Making good progress with my UDT app, but loops are not behaving as
expected. Here's the code of my test program. Any SIMPLE comment on what I'm
doing wrong?

(Incidentally, I wonder why my copied and pasted code finishes up double
spaced?)



Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load

TestLabel.Text = "starting"

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click

For x = 1 To 500

Debug.Print(x) ' the iterations of the loop are shown correctly in the
immediate window

TestLabel.Text = x 'but the label is not updated and no number appears until
the end

Next x

End Sub

End Class
 
S

StrandElectric

Dennis said:
Follow this with...

TestLabel.Refresh()
Click to expand...

Thank you Dennis! That did it. Perfect simple answer. Funny, I had tried
that but instictively had put the Refresh *before*!
 
D

Dennis

I had tried
that but instictively had put the Refresh *before*!
Click to expand...

If it was still in the loop, that should have worked also. It just would
have been behind by one iteration.
 
A

Armin Zingler

Am 12.01.2011 20:26, schrieb StrandElectric:
Thank you Dennis! That did it. Perfect simple answer. Funny, I had tried
that but instictively had put the Refresh *before*!
Click to expand...


Be aware that this works, but only for short loops. If Windows considers the
thread to be hung-up, refreshing stops even if you call Refresh. The solution
is putting the work in another thread, but this is an advanced technique.

This behavior is described in the following link in the 3rd paragraph:
http://msdn.microsoft.com/en-us/library/ms644927(VS.85).aspx
 
S

StrandElectric

Armin Zingler said:
Am 12.01.2011 20:26, schrieb StrandElectric:


Be aware that this works, but only for short loops. If Windows considers
the
thread to be hung-up, refreshing stops even if you call Refresh. The
solution
is putting the work in another thread, but this is an advanced technique.

This behavior is described in the following link in the 3rd paragraph:
http://msdn.microsoft.com/en-us/library/ms644927(VS.85).aspx
Click to expand...

My loop (through a random file) is under 8,500 iterations. I have printed
out that MSDN stuff but it is way too complicated for me!
 
A

Armin Zingler

Am 12.01.2011 23:10, schrieb StrandElectric:
My loop (through a random file) is under 8,500 iterations. I have printed
out that MSDN stuff but it is way too complicated for me!
Click to expand...

Don't print it out. Read only one single paragraph. It says that your
window is hidden and replaced by a "ghost window". There is no output
in the ghost window. What's the complicated part?
 
S

StrandElectric

Armin Zingler said:
Am 12.01.2011 23:10, schrieb StrandElectric:

Don't print it out. Read only one single paragraph. It says that your
window is hidden and replaced by a "ghost window". There is no output
in the ghost window. What's the complicated part?
Click to expand...

Well, as you gave me the URL I thought it was all to be read!
 
C

Cor

Strand,

Everybody can have his own opinion in my idea.

I have read mome times currently in this newsgroup to refresh,

One of those opinions from me is that refresh is solving something with a
bandage.

There should be a reason for the problem.

Be aware as a loop is running in a method your UI freezes, it is like that.

An solution is the do events, which gives always in newsgroups and forums a
bunch of comment, because it is known not to do that.
"And then I see a bunch of argumentations from the time even before VB6 and
never one for modern CPU's and OS systems"

However, to solve a non wanted situation with an even worse instruction for
time consumption, than do events is in my idea no solution.

Be aware that while you are debugging everything goes billions time slower
(because of breaks) than in the actual situation of your program without
debugging.

imo

Cor



"StrandElectric" wrote in message
Making good progress with my UDT app, but loops are not behaving as
expected. Here's the code of my test program. Any SIMPLE comment on what I'm
doing wrong?

(Incidentally, I wonder why my copied and pasted code finishes up double
spaced?)



Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load

TestLabel.Text = "starting"

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click

For x = 1 To 500

Debug.Print(x) ' the iterations of the loop are shown correctly in the
immediate window

TestLabel.Text = x 'but the label is not updated and no number appears until
the end

Next x

End Sub

End Class
 
S

StrandElectric

Cor said:
Strand,

Everybody can have his own opinion in my idea.

I have read mome times currently in this newsgroup to refresh,

One of those opinions from me is that refresh is solving something with a
bandage.

There should be a reason for the problem.

Be aware as a loop is running in a method your UI freezes, it is like
that.

An solution is the do events, which gives always in newsgroups and forums
a bunch of comment, because it is known not to do that.
"And then I see a bunch of argumentations from the time even before VB6
and never one for modern CPU's and OS systems"

However, to solve a non wanted situation with an even worse instruction
for time consumption, than do events is in my idea no solution.

Be aware that while you are debugging everything goes billions time slower
(because of breaks) than in the actual situation of your program without
debugging.

imo

Cor



"StrandElectric" wrote in message
Making good progress with my UDT app, but loops are not behaving as
expected. Here's the code of my test program. Any SIMPLE comment on what
I'm
doing wrong?

(Incidentally, I wonder why my copied and pasted code finishes up double
spaced?)



Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load

TestLabel.Text = "starting"

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click

For x = 1 To 500

Debug.Print(x) ' the iterations of the loop are shown correctly in the
immediate window

TestLabel.Text = x 'but the label is not updated and no number appears
until
the end

Next x

End Sub

End Class
Click to expand...

??!!
 
C

Cor

Strand,

I never use the immediate window, I always use the quick watch, I also don't
use compile and continue, maybe is that the reason for that.

So don't expect an good answer from me on questions around the immediate
window.

Cor

"StrandElectric" wrote in message

Cor said:
Strand,

Everybody can have his own opinion in my idea.

I have read mome times currently in this newsgroup to refresh,

One of those opinions from me is that refresh is solving something with a
bandage.

There should be a reason for the problem.

Be aware as a loop is running in a method your UI freezes, it is like
that.

An solution is the do events, which gives always in newsgroups and forums
a bunch of comment, because it is known not to do that.
"And then I see a bunch of argumentations from the time even before VB6
and never one for modern CPU's and OS systems"

However, to solve a non wanted situation with an even worse instruction
for time consumption, than do events is in my idea no solution.

Be aware that while you are debugging everything goes billions time slower
(because of breaks) than in the actual situation of your program without
debugging.

imo

Cor



"StrandElectric" wrote in message
Making good progress with my UDT app, but loops are not behaving as
expected. Here's the code of my test program. Any SIMPLE comment on what
I'm
doing wrong?

(Incidentally, I wonder why my copied and pasted code finishes up double
spaced?)



Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load

TestLabel.Text = "starting"

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click

For x = 1 To 500

Debug.Print(x) ' the iterations of the loop are shown correctly in the
immediate window

TestLabel.Text = x 'but the label is not updated and no number appears
until
the end

Next x

End Sub

End Class
Click to expand...

??!!
 
A

Armin Zingler

Cor,

Mr. Strand's efforts in his age of 70 (or 71?) are highly respected
and appreciated! What I've learned from him for my life is that it's
not always the _perfect_ way that you can walk slower or faster because
an individual way is an option, too.

Just some thoughts.

:)
 
C

Cor

Armin,

It was not Strand who was writing about refresh.

Who did it did it with his own opinion, like I did that with my opinion.

:)

Cor

"Armin Zingler" wrote in message
Cor,

Mr. Strand's efforts in his age of 70 (or 71?) are highly respected
and appreciated! What I've learned from him for my life is that it's
not always the _perfect_ way that you can walk slower or faster because
an individual way is an option, too.

Just some thoughts.

:)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Debugging Error 1
Aligment works but... 21
Bindingsource problem 3
strange behavior , has someone an explanation for this ?? 9
Help With Custom Paging in DataGridView - VB.Net 2008 0
Tutorial, what have I missed ? 6
Latebound Exception? 3
Finding IP from vb.net 1

Top