So in terms of garbage collection...the deletion of those arrays are the only part. <div class="gmail_quote">On Thu, Jul 22, 2010 at 9:27 PM, Robby Findler <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Thu, Jul 22, 2010 at 8:21 PM, Mathew Kurian <<a href="mailto:bluejamesbond@gmail.com">bluejamesbond@gmail.com</a>> wrote: > If someone has a bit of spare time, can he/she explain how these images are > loaded (time, allocation, garbage collection, etc) and then reproduced again > during the redraws, it would be extremely useful. </div>That particular aspect of the system is unlikely to be able to be improved (altho there may be some windows-specific strangeness I suppose; if you try on a mac and see the same behavior that would confirm my opinion). Instead, the question will be how to avoid doing the drawing that often. But to answer your question, the images are loaded by reading the file, interpreting the data stored there and creating a bitmap% object that records an flat array of the colors. Then, during drawing that data is (efficiently) copied onto the screen. Robby </blockquote></div>