in 2.0beta4 you say:
[enh]-major image display improvement
Not with my database!, now, every picture has about one second-delay, before it is showed on screen.
In the 1.2 version, this was NOT the issue.
in 2.0beta4 you say:
[enh]-major image display improvement
Not with my database!, now, every picture has about one second-delay, before it is showed on screen.
In the 1.2 version, this was NOT the issue.
What kind of images are you talking about?
These improvements are only for image fields and they are much faster especiallylarge onces.
so in what case do you see a lag of 1 second?
i have tested it. And i see that with smaller images the old method is faster. Now i have made some more improvements that smaller images will do the old way and larger images the new way (which must be done or else you get out of mem exceptions)
Yes, I did used imagefield with small images.
I shall do some test with bigger images.
BTW: Is it possible to add the same properties to a mediafield as it is with a image in a button? I mean: crop, reduce, constrain property etc…
another question: what is a large image? is 3MB Large or is 15MB large?
Can you give us some tips, what will and will not work!
about mediafield: not in the planning at the moment. If you only want to display please use a label.
a big image is not really it size in diskspace but it’s size in pixels. But for now images smaller dan 150KB will be read in the fast (but memory expensive way) and larger in the bit slower (for smaller images but much much faster for really large images) way.