MMcM
October 13th, 2002, 12:55 PM
I apologize for not responding to your PM right away. My time has been almost totally occupied elsewhere.
If you know C++ and have access to Visual C++ in particular, there is a document in DVDSpy-src.zip that outlines step-by-step how to add support for a new application. To summarize, there are two ways to interface:
with the cooperation of the application. If the application has some kind of API or plug-ins, you can program one of them to send messages to DVDSpy that will be turned into Girder events. This is how Winamp and Windows Media Player work. No changes to DVDSpy itself are needed.
without the cooperating of the application. This where the -spy name comes from. The DVDSpy code proper does this. The code has a number of macros to simplify common techniques for this. It is hard to make it 100% data-driven, such as from the registry or a configuration file, because every application is a little different. This is how WinDVD works. It is particularly easy to get much of the information out of applications that use DirectX. This is how TheaterTek and the ATI Player work.
The two are not mutually exclusive. ZoomPlayer does both.
I do not know whether RadLight has any API, so I cannot be more specific.
Ordinarily, I would try to set aside a few minutes to download the program, assess the possibilities and at least give some recommendation on how to proceed. RadLight is an unusual case, though, because of the spyware disagreement. I am not qualified to judge whether the outbound communication from RadLight is benign or pernicious or in between. Nor do I want to get in the middle of an argument on the point. The truth remains that I use AdAware to weed out things that are indisputably spyware. So, installing something that actively works to remove AdAware is a problem. I will have to backup the machine before installing to get things back together after any experimentation. That just makes the whole process longer. So, if you want to have a try, it may get done sooner.
If you know C++ and have access to Visual C++ in particular, there is a document in DVDSpy-src.zip that outlines step-by-step how to add support for a new application. To summarize, there are two ways to interface:
with the cooperation of the application. If the application has some kind of API or plug-ins, you can program one of them to send messages to DVDSpy that will be turned into Girder events. This is how Winamp and Windows Media Player work. No changes to DVDSpy itself are needed.
without the cooperating of the application. This where the -spy name comes from. The DVDSpy code proper does this. The code has a number of macros to simplify common techniques for this. It is hard to make it 100% data-driven, such as from the registry or a configuration file, because every application is a little different. This is how WinDVD works. It is particularly easy to get much of the information out of applications that use DirectX. This is how TheaterTek and the ATI Player work.
The two are not mutually exclusive. ZoomPlayer does both.
I do not know whether RadLight has any API, so I cannot be more specific.
Ordinarily, I would try to set aside a few minutes to download the program, assess the possibilities and at least give some recommendation on how to proceed. RadLight is an unusual case, though, because of the spyware disagreement. I am not qualified to judge whether the outbound communication from RadLight is benign or pernicious or in between. Nor do I want to get in the middle of an argument on the point. The truth remains that I use AdAware to weed out things that are indisputably spyware. So, installing something that actively works to remove AdAware is a problem. I will have to backup the machine before installing to get things back together after any experimentation. That just makes the whole process longer. So, if you want to have a try, it may get done sooner.