Home/ Questions/Q 512151
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T07:17:25+00:00

I am building a C++ (Qt) based application for controlling a flash based UI.

  • 0

I am building a C++ (Qt) based application for controlling a flash based UI. Because the flash runtime leaks spectatular amounts of memory, we execute the UI as a .swf loaded in the standalone flash player separate from the command-and-control app written i C++.

The C++ starts the flash player as an external process with appropriate parameters, and communicates with it over a TCP socket connected to localhost.

The application runs primarily on Windows XP and above.

The unfortunate side effect of running the flash player standalone is that two applications are shown in the Alt+tab list as well as in the task bar on windows (one being our application, the other being the flash player). Additionally, as the application runs full screen, flash must manage the entire screen. Allowing the C++ app to draw parts of the screen would be a massive improvement.

We would like to somehow merge the two, while leaving our own application in control. I am thinking something along the lines of Google Chrome, which appears to be running each browser tab in a separate process while displaying all output in a single window.

I’ve been reading up in the Win32 API (and google) in order to determine if accomplishing this is even possible. Althogh so far I’ve come up with dll injection as the only semi-viable solution, but I would very much like to consider that plan B.

Any suggestions would be appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The Alt+Tab list shows top-level (no parent) windows that are visible and don’t have the WS_EX_TOOLWINDOW extended style. So if you have two windows from two processes but you only want to see one in the Alt-Tab list (and on the task bar), then you have a few options:

    1. Add the WS_EX_TOOLWINDOW to one of the windows.

    2. Re-parent one of the windows to a hidden top-level window.

    3. Re-parent one of the windows (probably the Flash player) to the other window. This is tricky, but it’s probably how Chrome and many other multi-process single-window apps work. What makes it tricky is handling the lifetimes of the windows and inadvertently serializing the message queues.

    • 0