On 12-Jul-10, at 1:13 PM, Björn Eiríksson wrote:
Obviously a timer subclass is no solution since, one would not want to expose to REALbasic a internal class that has no meaning to the REALbasic developer.
In RB itself you can mark it private in such a way that the developer never sees it (trust me we have such things in the framework which is partially written in RB) I'm assuming you could do the same in a plugin - but I'm certainly not expert enough in writing plugins any more to know for sure
Making a whole subclass in a plugin like that would seriously defeat the purpose of using the REALbasic framework.
Not really since there are only a few sanctioned ways of doing things whether you're a plugin or pure RB code
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
