More dummy questions, Jeff..

Trying to have both folder and image tn's at a 1:1 aspect ratio and I THOUGHT I had the settings correct for that but noticed tonight that is not the case for all. Here's an example page and if you scroll down, you'll see that 1) some portrait images are not cropped to 1:1 and 2) some smaller images are also not cropped. For the latter case, I presume that the code doesn't include upsampling smaller images to achieve the same tn size as those of larger images.

Attached is my corresponding settings page.

Yes, I sure do but the thing is, I inserted a link for the page in question, it just didn't take.

http://www.kilobravo.com/gallery-older/house/2020/index.html

Sorry, Jeff but my intentions were good. :=)

I guess it's the same problem we discussed lately: you change the thumbnail dimensions after the skin sets the optimal. Therefore, the album loads the slide images because the thumbnails are too small. In this case, the thumbnails are cropped, but the slide images are not, naturally.

The layout you chose needs 250x250px thumbnails. The skin calculates this when you change any setting that affects this. If you change it afterward, the first 20 will be oversized; the rest will be filled with slide images.

(Perhaps it wasn't you but another user with the same problem.)

You can enter any numbers you want for the various image bounds. You could type in "239x267," if the mood struck you. You're not restricted to the preset choices.

But this skin will constantly fight you. If you change anything else, like number of columns or page width, the skin will plug in its own notion of a proper size for the thumbnails. Why it's built this way is an enduring mystery.

To repeat, I am not the author of the Tiger skin. I would never have created the settings in the skin like this, because they're irrational.

It was designed this way because the skin's settings affected the optimal thumbnail dimensions. One could argue that the overall page width was a bad idea to include in the skin settings, but it's necessary for non-fixed-shape thumbnail layouts, such as the justified or vertical ones. You can't please everybody. It's particularly hard to impress other skin authors, as it seems . The idea was to provide an instant preview so users don't need to switch back and forth between the main tabs. In Lizard skin, I choose the other approach.

Yes, the skin should disable the thumbnail dimensions change. (If possible)

JAlbum was made in the pre-mobile era, and the transition to responsive design caused friction regarding the old model of pixel-sized elements. I hope that today, there are few users who can still think only in pixels.