> It' not soo easy. There are more places, e.g. the preview windows, the > image panel, and so on. > The image loading and scaling is done with an image cache. So if you > want to use severals thread for this task you have to check if the > image cache is thread safe and implement the image cache as > multithreaded code, the gui is only the last step.
Yep, if this multithreadning is "too easy" then it could be already done... I say it is easy as there is no need for realtime processing! Current solution seems to be done nearly in single process (from user view point everything else stops when images are loaded and scaled). I thinkt that later image loading can "stop" everything else and just load images with all CPU resources that are available. It might be good to make image cache thread safe as later it is easier to use and less debugging problems??? Still I need to understand old image cache functionality before doing any new functions. Has there been work for this before, is there anything that I can continue. /Juha -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
