First, just remember:
+#ifdef HELIX_FEATURE_REALPLAYER
+DEFINE_GUID(CLSID_HXAUDIODEVICEHOOK, 0xb84b8d32, 0xa391, 0x4308, 0x93, 0x71,
0x7d, 0x51, 0xc9, 0xc6, 0x5b, 0x3);
+#else
DEFINE_GUID(CLSID_HXAUDIODEVICEHOOK, 0X2CFA30DA, 0X118B, 0X4CA3, 0XAA, 0XF3,
0XF4, 0X74, 0X16, 0X23, 0X2, 0XE5);
+#endif
+
that !HELIX_FEATURE_REALPLAYER != Rhapsody. That is, there can be lots of
applications that build this code that are not either one of those
apps.
I don't think any of them will cause problems like the one your are
trying to fix though.
Second, is this the only way to fix the problem? I really hate
the need to have different GUIDs for the same interface. Seems
like we can get ourselves into trouble that way.
--greg.
Bo Tian wrote:
Modified by: [EMAIL PROTECTED]
Reviewed by: [EMAIL PROTECTED]
Date: 6/16/2006
Project: audio
Synopsis: Currently, HXAudioDeviceHook.dll is shipped and registered by
Rhapsody; so if same class id (CLSID_HXAUDIODEVICEHOOK) is used by
RealPlayer, this DLL will be shared; thus we want a new class ID for this
DLL specific for RealPlayer.
Overview:
N/A
Files Modified:
Audio/device/platform/win/HXAudioDeviceHook/HXAudioDeviceHook.h
Image Size and Heap Use impact (Client-Only):
N/A
Platforms and Profiles Affected:
All
Distribution Libraries Affected:
N/A
Distribution library impact and planned action:
N/A
Platforms and Profiles Build Verified:
Windows
helix-client-all-defines
Platforms and Profiles Functionality verified:
Windows
helix-client-all-defines
Branch:
Thxclient_1_5_0_cayenne
------------------------------------------------------------------------
_______________________________________________
Audio-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/audio-dev
_______________________________________________
Audio-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/audio-dev
