Hmm ... But this still needs a main application that actually controls / starts them (I assume you use UDP as communication layer between the apps? Pipe is nice but is a "on hold" communcation), which is perhaps why I don't see why the TProcess approach won't work.
The other app won't finish until it codes makes it to do so (ie you wanted it codewise to do so) or you finish the process in the "main application".
The user can be gotten out of way if you own MaxGUI and create the window through with window hidden flag ;-)
But a nice idea in general :)
I use a similar approach so far to do virtual multi threading by spawning different sub applications I can use to do calculations asyncronous and that communicate to each other through UDP. This sadly has its restrictions, but for basic things it works quite good.
The other app won't finish until it codes makes it to do so (ie you wanted it codewise to do so) or you finish the process in the "main application".
The user can be gotten out of way if you own MaxGUI and create the window through with window hidden flag ;-)
But a nice idea in general :)
I use a similar approach so far to do virtual multi threading by spawning different sub applications I can use to do calculations asyncronous and that communicate to each other through UDP. This sadly has its restrictions, but for basic things it works quite good.