That was actually what I meant when I asked wheather the app was running in an Orbiter dialogue Window.And im excited at the thought of having something like this for use in orbiter.
As mentioned before, my whole Orbiter Galaxy project is currently running in a dialogue window inside orbiter (thanks to Face), accessible by ctrl+F4 (which I rarely use, because I can start it up by pushing a button on my MFD). It uses a completely different graphics engine than Orbiter, in its own thread, and is giving no trouble whatsoever.
So I think the only thing that would have to be changed in the code in order to implement the whole thing is the message handling, which in case of a complete implementation can be handled by a simple data type, since the MFD and the application would be sharing the same memory space...
However, the actual benefits vs. a complete external aplication would pretty much be limited to what I wrote in my last post above, except maybe for some added immersion (and some much easier coding to communicate between the planner and the MFD).
