On 30/3/07 10:49 PM, "Jonathan Johnson" <[EMAIL PROTECTED]> wrote:
>> Wow?! :-( >> >> This is somehow not smart IMHO. >> Valentina have few hundreds of methods... > > We understand, and we have quite a few ourselves. It was a large > undertaking internally as well. However, when individual classes, > such as FolderItem, have methods that return things only allowed in > GUI applications (such as OpenAsPicture) this level of granularity is > wonderful in its flexibility. But can be something as with EXPORT pragma in C++: * If I declare EXPORT for class - then all its methods are exported * if I have problematic class as you mention, I not set EXPORT for the whole class, but set it for only methods that must be exported. Easy? Flexible? >> What is the correct step to do this? >> Going to check again RB SDK examples and docs ... > > REALmethodDefinition has a flags field, which should be set to > REALconsoleSafe for console safe methods. If you know every method is > console safe (be careful about Pictures), you could always make a > loop to loop over all of the method arrays and set them. Okay, thank you for this tip, Jonathan. :-) -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
