x2.47 can't quick view image > 1MB

sgp · Post by **sgp** » 2003 Oct 24, 11:15

Win2k SP4, x2 alpha 47, the quick viewer displays hex instead of an image when an image file greater than 1MB is select. I'm guessing it's a limitation of the control that Niko's using, but 1MB+ pictures are very common these days, so I don't think this limitation is acceptable. Also, the quick viewer is very slow on pics. Niko, any chance that you'll add a plugin architecture, a la total commander, so other people could develop viewers?

sgp · Post by **sgp** » 2003 Oct 24, 11:37

I thought this might be subject to the same size limitation of the thumbnail generator, so I increased the nMaxFileSizeThumb value in the [MainFrame Settings] registry key, but images >1MB still get displayed as hex.

Post by **nikos** » 2003 Oct 24, 12:34

nMaxFileSizeThumb is the right value, but it is under the main key, not mainframe settings. Also check that you are changing the registry key you are using (if you have multiple "main" keys)

i don't think that the previewer is slow. It just waits for around 1sec before it kicks in, just in case you change your mind and move the focus to another file

sgp · Post by **sgp** » 2003 Oct 24, 15:14

Cut & paste from my registry
[HKEY_CURRENT_USER\Software\ZabaraKatranemia Plc\xplorer2]
"nMaxFileSizeThumb"=dword:000f4240
but still no change even after restarting x2.

Also, I think that the key affecting the behavior of quick preview should be different from the key affecting thumbnail view. I may want to be able to preview larger pictures, but not bother for thumbnails to keep x2 swift.

sgp · Post by **sgp** » 2003 Oct 24, 15:15

Can the delay before the previewer kicks in be adjusted?

Post by **nikos** » 2003 Oct 24, 16:39

000f4240 is just 1MB
to change it make sure you quit all x2 instances first and then edit the registry (make it 0 to have it unconstrained)

the timeout cannot be adjusted at present but it will be eventually

Post by **nikos** » 2003 Oct 26, 16:51

the timeout is controlled in build 48 from nFocusTimeoutMS

sgp · Post by **sgp** » 2003 Oct 26, 22:56

I'm assuming it's in milliseconds, right?
If set to 0 does it mean "no delay"?
Dowloaded build 48 and added nFocusTimeoutMS as DWORD under the main key. With x2 running, changing nFocusTimeoutMS has no effect. And when I exit x2, nFocusTimeoutMS always gets reset to 500.

JRz · Post by **JRz** » 2003 Oct 27, 06:39

sgp wrote:I'm assuming it's in milliseconds, right?
If set to 0 does it mean "no delay"?
Dowloaded build 48 and added nFocusTimeoutMS as DWORD under the main key. With x2 running, changing nFocusTimeoutMS has no effect. And when I exit x2, nFocusTimeoutMS always gets reset to 500.

You should obey the following sequence:

1. close all instances of X2
2. edit registry to change to the desired value(s) for registry keys
3. (re) start X2

This should get things done properly. X2 saves its state when closed, so if you edit the registry while X2 is running, everything gets reset to whatever X2 thinks it should be from its running copy. That's the reason why it seems you can't get the value changed.

P.S. There should have been no need to create the reg-key. X2.48 should have created the reg-key by itself. Didn't it do that with you??

Enjoy!

Post by **nikos** » 2003 Oct 27, 07:42

BTW, the minimum allowable value is 100, 1/10 of a second