Page 2 of 2
Posted: Sun Mar 11, 2007 10:36 pm
by SFSxOI
OK, stupid question here,,,,but i want to make sure i'm doing something right before I go any further with trying to locate a small problem;
If I do this:
Code: Select all
DefineGUID(BlurEffectGuid, $633C80A4, $1843, $482b, $9E, $F2, $BE, $28, $34, $C5, $FD, $D4)
When I call this, is it:
Code: Select all
_?GUID_BlurEffectGuid
or...
GUID_BlurEffectGuid
or
?GUID_BlurEffectGuid
Posted: Sun Mar 11, 2007 10:52 pm
by freak
The name you provide becomes a label in the datasection as it is, so it is:
This gives you the pointer to the guid, which is usually needed.
So if you want the name to be GUID_... you have to include that in the name.
Posted: Sun Mar 11, 2007 11:28 pm
by SFSxOI
OK, got it. Ya know when you stare at this stuff long enough you start to forget...or maybe its just old age
What the problem realy turned out to be was a spelling error - I did BlurEffcctGuid instead of BlurEffectGuid - had a 'c' instead of an 'e'.
Thanks freak
Posted: Thu Mar 15, 2007 1:41 pm
by SFSxOI
freak,
This is weird. Using your example code from the first page of this thread, the first time i run it it works, however, any more tries to run the example you provided in your post gives this error:
XIncludeFile #PB_Compiler_Home+"COMFramework\BaseInclude.pb"
__COM_Class(StatusObject) is not a valid operator
works the very first time i run the sample, but will not work after that.
Posted: Mon Nov 19, 2007 8:04 pm
by freak
I extended the number of interfaces that can be implemented in an object to 20, as it was requested by somebody via email.
It is available from the above location.
Let me know if there are any troubles.
Posted: Sun Jun 28, 2009 9:39 am
by lexvictory
@Freak: I know this is a rather old topic, but is there any chance you can update the debugging code for x64? (i got the other bits to work, but converting the asm is throwing up linker errors)
If you don't have time / can't I guess I'll just do the debug needy work in the x86 IDE...