This means that Thread A, performing operation [2], wil l post a message to Thread B which is the owner of the GUI Window, and can then c ontinue to handle another task.

It seems that looking at the Stack-Trace as the state of the application is a huge mistake. When we write a Procedural C code the operation is inside the function – this is why it is called a Procedure. We can see the different Phases by looking at the lines of code (see my pr evious post for more information). When we break this association we can start managing our application better.

The Application State is a cross-section of all states of running elements. cpp is the test application with main() and the other threads. aspx? This adds these new States to the picture object: No-Data, Updating, Data-Ready./MTnPDirEnum. The hardware accelerated Stack is no longer sufficient for us and the Stack-Trace is no longer the state of the application. On a serial application this can be the state of the Stack (or Stack-Trace). This time again, there can be suspended operations even though all threads are working. These States are kept to manage resources and avoid resource leaks. There are also suspended operations. I have elaborated on this on a previous post called Stateful Programming – A Case Study. In Procedural programming every branch is commonly an execution state