I won't question this. But I am interested in why. But I can assume you have a good reason so there's no need to explain if it takes too much effort...
> Most of you have probably noticed that you can get at a bunch of > internal framework functions via the 'gCallResolver' variable in > PluginMain.cpp. While handy and interesting, it was never meant to be > used for anything not listed in PluginMain.cpp. > > In 2012r1, we intend to change how the runtime works internally and > this giant global list will be going away. It will be replaced by a > list of only the functions in the plugins SDK. Since doing this would > realistically break a lot of plugins, we'd like to know what private > functions your plugins are relying on and the reasons for that (so > those functions can be added to the list). While we can't promise to > make public every function given, we will do our best to be > accommodating. I'm using these. I THINK I added them? Not sure. RuntimeRaiseException REALGetControlFocus RuntimeMsgBox And these that seem like tthey are meant to be there, I'm not sure if it's part of the RB plugin SDK because I modified it so heavily I don't know what is mine or yours anymore. REALLoadObjectMethod (my favourite! very important!) pluginObjectType RegisterPluginVersion REALLockObject REALUnlockObject memoryBlockGetPtr memoryBlockGetSize CreateInstance REALBuildString REALUnlockString PluginRegisterInterface PluginRegisterClass PluginRegisterClassExtension PluginRegisterMethod REALYieldToRB GetEventInstance _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
