Activating a form brings it to the front if this is the active application, or it flashes the window caption if this is not the active application. The form must be visible for this method to have any effect. To determine the active form in an application, use the ActiveForm property or the ActiveMdiChild property if your forms are in a Multiple-document interface (MDI) application.

Activating a form brings it to the front if this is the active application, or it flashes the window caption if this is not the active application. The form must be visible for this method to have any effect. To determine the active form in an application, use the ActiveForm property or the ActiveMdiChild property if your forms are in a Multiple-document interface (MDI) application.

This reminds me of state machine I develop at university for Master's thesis. Activeate call to be change state and new Activeate can be diferent funtionality.

Friends, real Nagesh's funning to stop. Have you wondering why he not has posted some time? This is very sad situation: He take long struggle with dysentery and died of much diarrhea food poisioning. He has wife and 16 childs who are missing his provision and in bear feet on the streets.

I do a lot of WPF development, and I love the framework. However, progress bars, and updates to the UI in general are handled a little bit differently than your standard windows form.

There's not really a simple "Refresh the UI" call you can make. If you're going to perform a task substantial enough for a progress bar, you're expected to run it an another thread. Trying to perform a task and update the UI at the same time, on the UI thread, is very frustrating (because you're not supposed to).

I respect that this guy had the patience and clarity to deliver a compilable "'eff you" to the framework, instead of just smashing his keyboard.

I think this code could be cited as justification for an established peer review process. It doesn't have to be formal; it could just be a handful of programmers sitting down at lunch to glance through the code, discuss important methods, offer suggestions, and generally make sure it's not doing anything completely idiotic in plain sight.

I can't imagine this code surviving a peer review unless all the reviewers are total nitwits like the author.

I've seen stuff like this happen with TFS automatic merges. You merge from a dev / feature branch to Main then back to a dev branch at some later date. Sometimes TFS freaks out and duplicates the change.