On Aug 20, 2006, at 9:21 AM, Christian Schmitz wrote:
Maybe RB gives you different classes depending on what Binarystream
you
use.
No this is not true. It always worked and additional tests show that
the pointer to a dynamic access api is always the same.
So the pointer to the write function of the memory binarystream
can't be
used in the file binarystream class.
It turns out that:
On Aug 20, 2006, at 9:18 AM, Alfred Van Hoek wrote:
We use the new Plugin SDK, without defining FLAT_C_PLUGIN_HEADERS
or other macros (we do not believe that it relates to the plugin
SDK, but may need investigation).
it is the new SDK, and that we knew it already when the new SDK was
just published. it relates to:
REALGetPropValue((REALobject)fItem, "Directory", &isdirectory);
which has a different accessor. We need to define
FLAT_C_PLUGIN_HEADERS 1, then rewrite REALGetPropValue to
REALGetPropValueBoolean in our code, then make sure it is defined in
PluginMain. Release 3 and earlier require REALGetPropValueBoolean,
while Release 4 requires the new REALGetPropValue(..., unsighned
char*, which has a different accessor.
We were simply accessing a non existing file and by always calling
REALLoadObjectMethod on the folderitem, we did not crash..
Alfred
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
