Frans,

The progress windows that appear after the start generator button is clicked, is not a child of the main windows, then if during the generation you click outside the progress windows then the progress goes backward and you think that something was wrong. May be the progress windows could be a child of the main window. This happens in previous version too.

I'll see if that can be fixed, but the progress window is created on another thread, so I think it's not possible to make a form a child of a form which is owned of another thread, but I'll check it out

I'm not sure if you can do that from a seperate thread either...

One thought is to set the progress forms TopMost property = true and, although it can lose focus, it will not get hidden.

Rob

Otis wrote:

I'll see if that can be fixed, but the progress window is created on another thread, so I think it's not possible to make a form a child of a form which is owned of another thread, but I'll check it out

I got an exception thrown at one point whilst the progress window was open(ing), I can't remember the exception but I think it was to do with a Control handle being used before being created - possibly thread related??

I've not been able to reproduce it however - will let you know if it happens again. (Didn't crash the app - managed to recover gracefully)

Cheers Simon

The exception viewer being blocked by the progress viewer is one reason why I didn't use top-most. I'll check out topmost again though

Ok, making it owned by the main form is working OK. All code accessing it is doing it through delegates/invoke anyway, so it works without a problem. Fixed in next build

Frans,

Tested with the last build, it is ok now.