Seth Yastrov wrote:
I propose we have an interface, iSaverFile, which stores information about the files that the saver should write to. The loader would create an instance of an iSaverFile and add each object it loads to the iSaverFile. This would be an optional behaviour so as not to slow down loading and waste memory when you do not need the saver.
I just realized a major flaw in this. When an object is removed, then the iSaverFile would keep a reference. Also, the reference is useless since the current saver loops through each engine object anyway.
So I am changing the logic: The loader attaches an iSaverFile object to each engine object it loads.
The saver would then scfQueryInterface on each object it tries to save in order to respect saving to files.
Regards, Seth ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
