Image area too large to preview / Preview Now (button)

[Zardoz2293]

Updated to v13.30.01015 and for the first time I'm getting "Image area too large to preview" and having to press a button to display the image. Can't find the configuration setting to return this behavior to the prior setting (display image).

29KB sized image?

Thanks

[admin]

1) What is the pixel dimensions of the image?
2) What is PreviewMaxArea set to in XYplorer.ini?

[Zardoz2293]

1) What is the pixel dimensions of the image?
2) What is PreviewMaxArea set to in XYplorer.ini?

267 x 400
PreviewMaxArea=2; changed it to 0

What I don't understand is that it was working for years before, now on this update something changed. In every case the image could be displayed within the preview area, and they are all zoomed larger than the image size. Like I said, I've changed nothing in XY, did update Nvidia driver, but XY (previous version I was using worked correctly).

The above PreviewMaxArea=0 changed nothing, still displays message and button.

I have a dual monitor system. Doesn't make any difference if you use one monitor over the other, or Zoom on/off.
------------
Downgraded back to 13.20.0017 --> Works perfectly / As expected.
Can't provide feedback as to what version it was introduced as there is no way to download from 13.20.0017 between 13.30.0105 anymore.

[RalphM]

First I don't understand how any of your images could be previewed before. With PreviewMaxArea=2 you actually told XY not to preview any image file with more than "2" square pixels and I assume most of your pics are bigger than 1x2 pixels.

If you're really up to check which beta was responsible for the change you encounter, there's the archive with all the builds. (since collection started)
See following thread: http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=9679

Edit: Actually there was a recent change with this, see: http://www.xyplorer.com/xyfc/viewtopic.php?f=5&t=10676

[Zardoz2293]

First I don't understand how any of your images could be previewed before. With PreviewMaxArea=2 you actually told XY not to preview any image file with more than "2" square pixels and I assume most of your pics are bigger than 1x2 pixels.

If you're really up to check which beta was responsible for the change you encounter, there's the archive with all the builds. (since collection started)
See following thread: http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=9679

Edit: Actually there was a recent change with this, see: http://www.xyplorer.com/xyfc/viewtopic.php?f=5&t=10676

What's your point? Did you to read my post? I said it worked previously for YEARS with nothing changed in the XY.ini configuration relative to previewing images. I haven't changed anything except moving from one build specified below, to the current, about two weeks of development/changes. What "archive" are you referencing? The Freezer? or the work in progress? If so, have you taken the time to review either/both of them for the "individual" builds?

[admin]

That PreviewMaxArea=2 worked for you before v13.30.0103 is due to a bug that I fixed in v13.30.0103. You did not get the real native preview but a shell preview of the image. So the shell kind of bypassed the PreviewMaxArea limit. These times are over now. You won't find many images that will pass the PreviewMaxArea=2 limit.

[Zardoz2293]

That PreviewMaxArea=2 worked for you before v13.30.0103 is due to a bug that I fixed in v13.30.0103. You did not get the real native preview but a shell preview of the image. So the shell kind of bypassed the PreviewMaxArea limit. These times are over now. You won't find many images that will pass the PreviewMaxArea=2 limit.

Thanks Don. I now understand. Concern resolved.

[RalphM]

What's your point? Did you to read my post? I said it worked previously for YEARS with nothing changed in the XY.ini configuration relative to previewing images. I haven't changed anything except moving from one build specified below, to the current, about two weeks of development/changes. What "archive" are you referencing? The Freezer? or the work in progress? If so, have you taken the time to review either/both of them for the "individual" builds?

Yes I read your post and was practically saying the same as Don did later in other words.
I put links to the corresponding threads in my post, so you could easily find out yourself what I was referring to and no, I didn't check whether those builds are in the archive
but thought you could do that bit of research yourself if you were eager to.

I try to help but I'm not doing your work here.
And for the record, I took your reply as an offence.

[Zardoz2293]

I took your reply as an offence.

RalphM, thanks for the assistance, seriously. However, your reply, came off as an attempt to tell me I'm wrong in what behavior I was experiencing with XY. Then you berate me by your extra comment. I reviewed the XY build changes from the version I had to the most current and didn't recognize anything that might be the source. Then I tried to download each build thereafter and install in an attempt to find where the behavior change occurred, so I could take a harder look at the change log and pinpoint where 'it', the behavior change actually occurred. Knowing that answer would provide me a better method to understanding any specific XY technical terms, scope changes, etc. so I could search the XY forum. However, since the last time I downloaded prior builds to problem hunt in XY, the prior builds are not available via the "bug" thread. Okay, check out the Freezer. Okay, only significant changes. I reviewed all of the configuration properties via F9. I searched via "Jump to Setting..." and couldn't located anything that might effect the image preview (from my perspective) -- I'm a power user, but I also set and forget once I have the behavior I expect. I did all that before I posted. Over the years I've had thousands of posting to technical questions and have unfortunately, like everyone, experienced those who post just to post, or for some reason feel the need to backhand me by stating the obvious -- your reply appeared to fit that criteria. My apology. (you might want to review what you said in response to my inquiry; I don't think I was being overly sensitive.) In closing, please accept my apology if I was curt, for offending.

[armsys]

Hi RalphM & Zardoz2293,
I read RalphM's post. I honestly believe RalphM's utmost sincerity in helping Zaradoz2292's issue, though not necessarily resolving it.
Bear in mind, RalphM did spend time and won't gain tangible benefit by helping Zardoz2293.
To be fair, we should give RalphM due credit and respect, IMHO.
I am not the thread starter but I learn a great deal from you both gentlemen's posts.
Most XY users here likewise benefit from your contribution as well.
Wish you both gentlemen shake hands. Let us remain focused on the issues at hand.
Thanks your kind understanding.
Just my 0.002 cents.

[RalphM]

No hard feelings here, I just felt "Huh, what happened here" when I read the reply.

Yep, shake hands and forget about it.
Whatever you prefer /