Eric Nepean wrote:NN635395415190452258UL wrote:Hi,
it seems that when requesting "images" or "variants" from either the "application" or the "current document" it's always returning the images or variants for the currently selected collection. It should return all images/variants for covered by currently opened catalogues when asking the "application" or the currently front most catalogue when requesting them from the applications "current document".
Yes, this is the way it is supposed to work;
I respectfully disagree b/c in an object oriented world, it is not logical, it's not what the user or developer would expect. There are objects representing the application, documents (Catalogues) and collections. Asking the "application" or the "document" object for it's images and getting the images in the currently selected collection is not making any sense.
Put another way:
In case we had a "CookingReceipts" object for "Sauce Bolognese", which contained "ingredients" objects, which in turn contained "spices" objects, and we ask the "CookingReceipts" object for it's ingredients just to get "salt", "pepper", "thyme" and "basil". The minced meat, onions tomatoes etc would be missing. It would not be all ingredients, just a subset.
Sure, in our case with C1 one could try checking all collections and other workarounds, but that doesn't make the initial bug more right.
The purpose of a collection is to define a group or groups of images. If a collection is selected, it means you intend to work with that group of images. If you ignore this, then you have no way of working with only a group of images.
I'm not asking a collection for it's images, I'm asking the (current) document (i.e., Catalogue) or the application for it's images. That's why returning anything other than all the images contained in either of those wrong.
If you want to work with all images, then select the collection "All Images".
That's not a suitable approach for at least two reasons:
- Using the existence of a collection ("Catalogue"), which might or might not be always there with future versions.k about future versions)
- The naming of that collection/catalogue, which might not only change with different versions of Capture one, right now it is based on the users locale setting, so the collections name can't be relied upon.
Best
-Torsten