The controls.dat viewer already has prelimenary support for such options. It currently can watch for a changed text file and reload itself accordingly (buggy though, it still needs work). Dk has various alternatives to "broadcasting" that I think minwah should look into instead because:
A. They don't require activeX plugins
B. They don't require changing the caption (which is good for you particular app but VERY bad for other apps that might be looking for mamewah via it's caption.)
C. They are just are more acceptable standards.
I use (or should say use in theory, they are broken as of this build) both methods of winsock communication, which are great because they can broadcast over a lan or wan for that matter. These are great methods because winsock is built into windows, so everyone has it and there are apis designed to call it, so no plugins are necessary.
I also use a simple "write to a text file the current game's data" method. This one is great because all the companion app has to do is open a text file every few seconds and react to any changes. This makes programming a breeze.
I only bring these otehr methods up because determining things via the caption is very unreliable. Trust me on this, as my wrappers used to use this method to get some of their data (they don't now, thank god!). It seems to be working in your case though, but I've actually seen windows and screen managment programs change captions before. It's highly unlikey, but when it happens it can be a huge pain.
Hope that helps your problem some. And remember "broadcasting" is bad ummk. The prime example of this is the fact that the mame32 devs like it.
