Actually, it means to me :P I have to know if a process ist not answering for a good time, so my app will reset it. Now, how exactly can I know if a process has stopped or not with QProcess?if we ignore 'not answering' because it doesn't mean much, then QProcess can tell you if a process has stopped or not. And thats it.
hehe, I guess yes! xD Essentially: I must be able to have entire control over the software (as far as it allows me, of course) without having any dependency of that one over my app (so, e.g., if my app crashes and is closed, that software will continue working as if nothing happened since there must be no dependecies, only momentarely interventions).I am puzzled how you can expect to "be able to run it" without starting it with your application. Is this some unusual interpretation of "run it"?
Hmm, as I was figuring out.Anyway to control an entire machine full of foreign processes, which is what you are asking for, is inherently platform specific and intimately tied to security model of the operating system allowing you to do this. You will have to use the appropriate operating system API to do the vast majority of what you ask.
Actually, at least for the time being, it's not written in Qt. But I imagine that this app will be later transformed into one that should have no IDE limitations.Provided that the other application was written using Qt and provided that you are able to inject some code into the application, it might be possible to do most of what you want with Qt. However, as Chris mentioned, this is very platform specific.
-------
Conclusion, then:
It's better to forget using QProcess, because even if I use it I'll not be able to do everything I want with it, so I'll have to use the OS API anyway - so better write evertyhing using the API functions.
So now the only problem is to make that work (http://www.qtcentre.org/threads/4969...-quot?p=223231).
Well, thanks!
Momergil
Bookmarks