Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Code Talk] CLSIDs
#1
(21.11.2009, 21:40:34)DCoder Wrote: Thou shalt not argue with those who can read the disassembled code.

Im gonna start using this one Tongue

Just while we are here, does YR have the BallisticLocomotor? I noticed it in SUN.TLB the other day and its CLSID is present in the TS executable, would be interesting if D knows anything about this...

Reminds me, i gotta send you that IDB Wtf
Reply
#2
I think you'll find that CLSID belongs to the DropPodLocomotion, which is conspicuously absent from LOCOS.TLB Smile

Worth playing: 1 | 2 | 3
Reply
#3
Oh...

In TS, I have {4A582745-9839-11D1-B709-00A024DDAFD1} as the DropPodLocomotor and {4A582740-9839-11D1-B709-00A024DDAFD1} as the BallisticLocomotor, where the 8th in integer is the different. 0x006D0E98 (TS) is the CLSID in question, and indeed in the TLB it is the CLSID of the DropPodLocomotor...

Its a shame there is no reference to it, would be nice to know what it was.
Reply
#4
My TLB Viewer says
Code:
// Generated .IDL/C++ pseudo source equivalent of Win32 type library ..\<Unknown>
[
  uuid({4A582740-9839-11D1-B709-00A024DDAFD1}),
  version(1.0),
  helpstring("Locomotion Type Library")
]
library LocomotionLibrary


[
  uuid({4A582745-9839-11D1-B709-00A024DDAFD1}),
  version(1.0),
  helpstring("Ballistic locomotion")
]
<snip>
coclass BallisticLocomotion
{
    [default] interface ILocomotion;
    interface IPersistStream;
    interface IPiggyback;
};
And both those CLSIDs are present in YR just as in TS.

Worth playing: 1 | 2 | 3
Reply




Users browsing this thread: 1 Guest(s)