MVallevand wrote: > Tom Metro wrote: >> Your observation of the problem correlating with image file sizes does >> seem to suggest that. Please file a bug report in the bug tracker at >> Sourceforge with these details > > There is absolutely a memory limit, it is not a bug.
Wouldn't you say that still qualifies as a bug? If it can't display an image, it should provide some feedback to that effect. It's not clear to me exactly what is going on. Is it just skipping over images that decompress to take up too much memory? Is the act of decompressing an oversized image causing corruption in the file list? > Longer term users of mvpmc probably remember that before Terrence's > patch, jpeg view was impossible. What did the patch do? Maybe we can use a setting in the JPEG library to specify the resulting DPI we want, so pixels get thrown away as the image gets decompressed, rather than decoding it, and then mapping it to the screen resolution. (Maybe that's what the patch does?) -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
