The
easiest way to handle this is with the producer-consumer architecture. Mike showed you an implementation of this. The premise is that the event handler is the producer, and the other loop handles the events. You do not want the event case to get bogged down in handling the events. You can use the Application->Command Line Arguments property to get the list of arguments and add these elements to the queue,
as if they had been menu selections. The attached example shows a way of doing this. I don't have 7.0 so I back-saved from 7.1 to 7.0. I included the build file for the app. It's a standard build app with one addition: In the Application Settings you want to the check the box "Pass all command line arguments to application".
Aside: Mike, your examples are much appreciated, but seeing as most folks on this board speak English, it's sometimes difficult to know what your code is actually doing because the text is in German. In the example you provided, for instance, what's the event case label? Someone who is not familiar with it would have no way of knowing.