XnView Software

Hello again,

In XnView and XnView MP support is needed for 256x256 and 512x512 page viewing of MacOS .icns icons.

The biggest .icns page that can be currently viewed is 128x128.

.. as you can see the same icon in that XnMP 0.26 screenshot is this one too which clearly shows the 256x256 and 512x512 pages


This issue is related to the recent 'Icon Snapshot' request-support for .icns written in related topic, here; http://newsgroup.xnview.com/viewtopic.p ... =15#p83601

This is how it would look in a windowed view of MP if this feature was supported:


please add 256x and 512x .icns support for all Windows, Mac and Linux MP users

Could you post a .icns?

Here we go sir:
http://www.sendspace.com/file/vzx1fc

budz45 wrote:Here we go sir:
http://www.sendspace.com/file/vzx1fc

Ok, the 256x256 & 512x512 are in a specific format, i'll check...

Such a kind, hard worker you are.... The Mac users would value the 256x and 512x support the most. Look forward to using it myself in Xnview MP (win).

Please check XnViewMP 0.31

Thank you for adding 256x and 512x .icns support.

I must notify you that .ICNS snapshots that contain 256x and 512x take a little longer to open. - Is that speed issue something that can be resolvd in the next beta release or is it to do with .icns pages requiring more wait because of 512x size. Let me know.

All over sudden I have a lot files named x_<n>.tmp in my temporary folder. Are these 32-bit JPEG2000-compressed 256² & 512² pixel frames extracted from ICNS files?

Oh yeah I just noticed my Temp folder has it too. Thanks for bringing that up.

Ok, maybe this feature needs a little final clean up in that 256x and 512x should use memory only, snapshot or not.

XnTriq wrote:All over sudden I have a lot files named x_<n>.tmp in my temporary folder. Are these 32-bit JPEG2000-compressed 256² & 512² pixel frames extracted from ICNS files?

With beta 0.32, those .tmp files are no longer left behind

Yes XnTriq, Pierre reply emailed me last month to tell me that the temp file issue will be fixed in the next MP beta (0.32)

Currently I cannot test 0.32 as I'm not at home.... When I get home later I will test the latest beta

Resolved