Hi folks,
Thank you for your comments.
So, I can see that we can test the following format.
Keep in mind that the main goal is to make it more obvious for the most average people
1 - No filter, no selection: 200 images
2 - No active filter but selection : 200 images | 2 selected
3 - Active filter and no selection: 155 of 200 images
4 - The big game: 155 of 200 images | 2 selected
And about the position of the image currently displayed in the main viewer #120
We understand the need. But we’ll probably do it in a second phase to make it even more obvious for everybody.
I’ll discuss about it with the dev team.
Your feedback are really interesting, we know the MarCom wanted the “image” word for several reasons for PL1. But as you said maybe it’s no longer relevant in the scope of the “PhotoLibrary”.
I’ll draw attention on that.
I agree with you generally, Pascal (see my comments above) - - but, in the context of PhotoLab where we are processing files generated from a camera, in the act of taking/making a photograph, I contend that “photo” is more appropriate.
But an image is also everything that has been drawn in windows paint or scanned through a scanner. Everything that is flat, does not move and can be presented to your eyes.
Photos are images taken by a camera. Or as Wikipedia formulates it: “A photograph (also known as a photo) is an image created by light falling on a photosensitive surface”. So photos are a subset of images.
Now one could say, that normally photos are processed in PhotoLab, but on the other hand it is not prohibited to put a jpeg or tiff into the library, that has not been taken by a camera.
However, the only thing I would expect is, that a PhotoLibrary contains photos, and that an ImageLibrary contains images. It is always bad, if a software uses different terms for the same thing.
OK, but keep in mind that PhotoLab uses “Image” in other places as well. For example we have “SEARCH FOR IMAGES”, “image properties” and the menu Image