I pushed the change discussed here to my branch. Hopefully someone else will try building and testing it.
With this change, higher zoom level no longer affects memory use: All levels other than 100% and "fit" have the same memory use as each other, and that memory use is lower than any of them had before. (100% and "fit" are no worse than before and might be better). I hope this can eliminate the objection to providing 400% and 800% zoom choices (which were already in this branch). With a large high res display, I depend on the higher zoom. I didn't find time for most of the pre-commit testing I hoped to do. I did do the simple version of reducing cpu time used by creating the magnifier subimage. I did test enough that I think it is appropriate for others to build/test. With a reasonable test sequence, I compared my branch against a build of the Feb-17 default branch. I compared at 150% so both would have a magnifier displayed. Mine was a tiny bit more responsive and used 15% less total CPU time (to open an existing project, switch to 150%, and review every CP without changing any). There should be a common base class for CPImageCtrl and MaskImageCtrl. The areas I changed would fit better there than they do in CPImageCtrl itself. Some might fit better in some util file. I wouldn't ask permission to merge any of this to default without first resolving that decision. But that only needs discussion if there is a possibility of such permission. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/1770ca26-a40e-4643-be61-f60025a6700an%40googlegroups.com.
