image quality is reduced with new zoomify code -- why?

One trial fix, which doesn't seem to help...

I've made a couple adjustments to the code to help with this issue.

First, if a higher definition tile has already been loaded, it will be displayed. So if you zoom in, and zoom back out, the higher def tiles will still be visible.

Second, I added an option . If you set this to true in config.xml, an additional zoom level of tiles will be loaded. The downside to this is that it will load a lot more tiles than normally, so experiment and see if that option works for you.

Download the latest from http://worldkit.org/download/latest/worldkit.swf. It's version number "3.3-20070820"

AND

a possible improvement...

I think the changes required are going to be similar to this, it may just take some tweaking and refinement of what's there. Options would be to fine tune more precisely when the next layer of tiles is loaded (this is all set in processZoomifyConfig in worldkitConfig.as), or perhaps to only load those tiles in the center of the screen (this takes more work, changes in worldkitImages as well).

from markgaver...

Here is the problem I have: Some of the zoomed in images are with smooth appearance, and some are jagged. It depends on the relation of the size of the original picture and the size of the scaled down picture - if the width of the scaled down picture is exactly the width of the original divided by a power of 2 - the appearance is smooth. If it is a different size - it is jagged. Example: if the original is 1024px times 1024px the scaled down version 512x512 and 256x256 are smooth (these are produced by Zoomify), but 378x378 and 768x768 are jagged (because it is an approximation?).

At the same time - the ZoomifyView? smooths out even the 378x378 and 768x768 versions - there are 3 levels of pictures but 5 levels of zoom.

On a related note - the <zoomc> tag seems to be inactive when <zoomifydir> is used.

and then look at this line: http://worldkit.org/trac/browser/worldkit/com/brainoff/worldkitImages.as#L451 could that 256 be the reason? i dont know anything about zoomify, so that may be way off.