doevents

On a different question I suggested to use private void Form1_FormClosing(object sender, FormClosingEventArgs e) { while (processingLock) Application.DoEvents(); } in the FormClosing event (with processingLock becoming false immediately after a lengthy calculation was done). It should serve the purpose to have the application close down in an orderly manner and the original poster didn't use threads. On my suggested answer somebody commented that DoEvents is never good, providing this link: Use of Application.DoEvents() I read and (I think) understood the issue. In my opinion (which is still

I have a set of code that contains: Application.Wait (Now + TimeValue("4:00:00")) This is essentially pausing the macro for a four hour window from 3 AM (when it finishs running the code) till 7 AM (when it should resume). The code is on an endless loop essentially. I want the user to be able to have control during that time to edit certain cells. I have tried DoEvents but have not found the way to keep the macro running, yet provide control to the user during that time when the macro is doing nothing but waiting. Any insight would be appreciated. Thanks! EDIT: One more followup question. I

Is Application.DoEvents() just for forms? I thought that this command was used to ensure that all of the commands before are processed but now after reading the documentation , I'm not sure anymore. Yes, it's really aimed at Windows Forms. However, in my view it should be avoided where possible. It's usually used as a hack by developers who don't want to be bothered with putting long-running operations on a different thread... but that means they're introducing re-entrancy issues which can be very hard to track down, as well as still blocking the UI thread for some of the time (and if that

I am developing a messaging system based on webBrowser controls so that I can format the text however I please. When the user is offline and is sent messages, the messages are stored and an event is sent for every message when they log back in. When I set the default html and such for the website, I normally use: while (this.webBrowser1.ReadyState != WebBrowserReadyState.Complete) Application.DoEvents(); This works when the program is running normally. When the user is receiving message sent when they are offline, this triggers the next message event and so on, with each message until the last

A lot of good programmers (including a lot of good members of Stackoverflow) are against using Application.DoEvents() whatever the circumstances are. Actually it is even supported with plenty of articles in the net, like this one , this famous debate on SO , ... Though, I'm stuck in a case, where (I) think DoEvents() is the unique exit (lack of experience). That's enough as introduction, let's see some coding. I have a 'serialPort' component to connect with a controller through serial communication, send command and wait for its response, that's all. string response = ""; bool respFlag;