X3Photo Gallery Forums

daniel wrote: Hello, I can't find how to switch from render/resize w1024 to w1600 for all my images that are currently on /content in 2560x2560? In which file, which UI parameter? thank you

I can't make sense of this question. When X3 loads images, it will make an image request that is perfectly suited for the exact size it's displaying in browser, also taking the device's screen pixel ratio into consideration. If it loads w1024, it means that will sufficiently cover the area where the image is loaded. If you load larger sizes, it will take longer time to load, consume more memory, and the additional pixels will be wasted. When the visitor clicks an image to open in popup, another size will open, most likely the original. This is the point of multiple resizes and the logic is hardcoded into the X3 javascript application.

Perhaps you can explain why you want to modify this behavior? Perhaps you have a link?

daniel wrote: Thank you, ok if I understand correctly then, it is "X3" that determines this parameter based on the size of the "client" screen.

Well, X3 does determine the parameter based on the screen, but not on the size of the screen. We are speaking about images in a layout here, so the loaded size should be calculated based on the display size of the image. Not the full screen. Examples:

• An image in the layout consumes around 320px (on the screen).
• We then load /w320/ px image, because any larger is a waste of pixels.
• If the "pixel ratio" of the screen is 2:1 (or higher, like most modern screens and mobile devices), we multiply the requested image by 2x. In this case, we would load /w640/ which would be more than sufficient.

Loading anything larger than than the image area can support, is a waste of pixels, memory and bandwidth.

So in your case, you mention w1024. I don't know what specific layout this is, but the javascript has determined that w1024 is sufficient for the area/size that the image will display within. If you have a link to this specific scenario, I can explain it.

daniel wrote:If a visitor has a screen, for example 5K, this wXXXX parameter will automatically change to a value defined here: /var/www/html/app/parsers/slir/index.php.

If the screen is 5K and the image loads into a 320px area of the screen, it's irrelevant if the screen is 5k or 2k. The image pixel dimensions should be proportionate with the area where the image is displaying.

daniel wrote:I only have a 2K screen which therefore apparently uses this setting at w1024.

How do you know this, and what layout is it? For POPUP images, also take this into consideration.

If your screen is 2K, screen height is likely 1080 pixel. Then the browser likely consumes perhaps 80 px, so that means your available viewport height is only 1000px. So let's pretend we want to load a 2:3 PORTRAIT ASPECT image into your viewport (max 1080 px height). The largest possible pixels height that your screen can support, would be 1000px. Agreed? and if the image is 2:3, the largest dimension that this screen could support is 666 x 1000 px. Agreed? Anything larger than this, is superficial size that the screen can't support. Does this make any sense?

Just because you have a 2K screen, doesn't mean it should load "2k images". Screens and images have different aspects, and even in popup mode, the images need to be contained within the browser viewport.

X3 already managed this logic.