G'day John
When embedded graphics are used in a running app the app's real
memory usage (as displayed in Activity Monitor) goes up each time a
new graphic is displayed and does not come back down until the app
is closed. ...
Keeping all the graphics in a file or files and then reading those
in to a single graphic variable as needed (rather than embedding
all the graphics) solves the problem
I believe you may be able to include your graphics as arbitrary
binary data in the project by using a different file suffix, see this
thread in the RB forum
http://forums.realsoftware.com/viewtopic.php?t=10087
If so, you may be able to load from that memory block and thus avoid
the automatic reference that causes the leak.
On 07/01/2007, at 2:44 PM, John Jobe wrote:
Andy Dent BSc MACS http://www.oofile.com.au/
OOFILE - Database, Reports, Graphs, GUI for c++ on multiple platforms
REALbasic, C++, Python, Mac and Windows development and porting
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
