On Sunday, January 23, 2022 at 8:36:58 AM UTC-5 [email protected] wrote:
> Do we really have to magnify all of the image if afterwards only a small > portion of the magnified image fits on the screen? For me that feels like > an use of something similar to wxScrolled: wxScrolled tells you what part > of the image to render, you render that part and the rest happens by some > magic the operating system offers. > > Unfortunately wxScroleld itself chokes on too big virtual areas to scroll > in as GTK3 does do so when volunteering the magic that on scrolling moves > all parts of the displayed area that can be re-used after scrolling, then > requests the areas that aren't cached, currently (only the pixels that are > visible on the screen are cached). Afterwards that magic copies the > resulting bitmap to the screen; if the wxScrolled is only updated when > wxWidgets issues an idle event that feels both speedy and allows real work > to be done in the background. > > If I were working on wxWidgets, rather than working on Hugin, I would certainly focus on the things you suggested. Inside wxWidgets, there are lots of places where it would be easy to only record what needs to be done for magnifying and clipping, rather than actually do it, then the next time data from the magnified and subsequently clipped image gets copied (such as by GTK) produce that data on demand. I tried to figure out ways to derive from wxImage (rather than simply use it) in order to add those features (that I think it should have had). But so far as I understand, the interactions with GTK etc. aren't coded in a way that would permit that. For the moment, I'm setting that whole issue aside and working on some easier things, (the things I originally intended to talk about in this thread). -- 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/026748df-bc37-421b-95be-d8f936fd0a33n%40googlegroups.com.
