Laurent Veilleux wrote: > Well i tried you code with canvasSim and its slow :/ is it fast on > canvaq with big image (4000*4000) ?
When the whole huge image is visible in total, it is slow, which i understand. The more i zoom in the faster it gets. So it all comes down to the size of the image which need to be converted into a bitmap. Which is done pixel by pixel in wxWidgets. I experience that if the image is around the size of the resolution of the screen (1024*782), it is not problem. However if you display an big image (8000*4000 pixels) on the screen at a size of 1024*782, things are indeed slow. But also it does not make sence to display an image with such detail on a display with much less pixels, all those details are lost anyway. Therefore i think to make it really work for large image sizes, one needs to cache some images size vesrions, and choose the right one depending on the zoom factor in use. Like if zoomed in much, the full size detail is needed, and the subimage of the hwol image which is visible in taht case is small, and fast. If zoomout enough, and the full size image becomes visible, one should use a prescaled version which has no more detail then the screen resolution. If this optimization is still not enough e.g. one has a huge image 786 high but 10000 pixels width, there will/may be a need to tile the image upfront too. So i think it can be doen with some optimizing. But if your other trick with wxDC scaling works for you, why not. Klaas -- Unclassified ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Wxart2d-users_dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
