Yesterday, while working on a package, I noticed that after compiling the package and clicking the main toolbar execute button the test window would go 'busy' for about a minute and then give the error about the existing state, yada, yada. Click the button again and it would go 'busy' for another minute and end as it should and my output was there.
I then tried compiling and then using the execute button in the test window and then the run button and did not get the error.
I see no real use to this behavior, was it intentional and if so, what is the benefit to it working this way?
------------------
------------
Scott Mattes