Yeah, but what if the plugin only defines a module? When defining a
dummy class in this plugin and a call is made to REALGetClassRef on
that classname in PluginEntry, it won't load. And if you go further,
calling REALnewInstanceWithClass in pluginentry, and implementing the
REALMessageBox on whether or not the instance of the dummy class was
created, then it shows the creation when RB is launched, but the debug
build fails with the runtime error. Only if you create the dummy class
using the IDE, the module does not get stripped.
So you appear to have success, even with cross-referencing? I guess
you are calling REALGetClassRef in pluginentry as well?
Alfred
On Oct 11, 2009, at 12:41 PM, Björn Eiríksson wrote:
If your cross referencing then you, in the plugin entry of Plugin A
that uses something from Plugin B you get a class reference to the
class in Plugin B, this tells REALbasic that you will be using
Plugin B from Plugin A. Same goes for some of REALbasic internal
objects you may need to tell like this in the plugin that your gonna
use them to prevent them from getting smart linked out.
Björn
On 11.10.2009, at 14:15, Alfred Van Hoek wrote:
Rb appears to throw a runtime error when only a module from a
plugin is called. It reports a Failure Condition at
ObjectDefinitionConverter.cpp:163. It says that item-
>mPropertyTableIndex == propertyCount, and the message is "Manifest
file outdated? ScrolBar".
How to prevent this, other then instantiating a class from the
plugin to make sure the plugin is loaded?
Alfred
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
