I'm having a problem with stacked WAIT-FOR 's. First of all, our 'classic' code (procedures with frames) are all embedded in a class extending from Progress.Windows.WindowContainer. (these in return are embedded in a Windows Form!)
If I have two WAIT-FOR 's and I am trying to close them in code (last in first out) next thing happens:
Let's say procedure A first executes a WAIT-FOR and then procedure B executes a WAIT-FOR.
Now, in code, I first do an APPLY "CLOSE" to Procedure B and then an APPLY "CLOSE" to Procedure A.
What happens if I put some logs after the WAIT-FOR's is that only after all code has been executed, the APPLY "CLOSE" to Procedure B is triggered. The APPLY "CLOSE" to Procedure 1 is never triggered.
Next is my log with some explanation: