Photo Supreme

The script from the repository brought up a tab containing all my problematic images. THANK YOU!!! Lucky I'm down to only 13, so the process of checking and deleting files is manageable.


Make sure your online so as to be able to pickup items from the repository then as below;
Screenshot 2024-04 ...

Ever since upgrading to 2024, I've been getting startup messages "Continuing the thumbnail building for NN files". I am now down to 13 files but I have no way of identifying which 13.

When I first upgraded, I had over 600 files with missing thumbnails but, slowly, I've fixed most of them bit by bit ...

Now that we can schedule Verify Folder, I wonder if it's easy/possible to add a new item to the Catalog menu. Just below "Compact Current Catalog", add "Schedule Compact Catalog". With luck and a tailwind, we'd all be able to suppress start-up warnings about the need to compact the catalog!

The ...

Hert, I am unable to enter any script from the repository into my thumbnail information. For example, if I edit the custom thumbnail info to add a line by selecting "From Repository - Functional Rating Bar" I see "Access violation" in the thumbnail display.


I am not sure what is going on here ...

This is fixed in a quickly released update. Thanks for the rapid support.

Hert, I am unable to enter any script from the repository into my thumbnail information. For example, if I edit the custom thumbnail info to add a line by selecting "From Repository - Functional Rating Bar" I see "Access violation" in the thumbnail display.

Gah! This is a terrible regression. [Fixed almost immediately! Thanks.]

I have this quirky behavior that comes from being old and shooting hand-held with a big lens. I tend to allow the camera to shift downward during bursts. This causes the subject of the photos to move within the frame. I use the ...

I just upgraded (?) to 2024 and have Access Violations on two of four lines in each thumbnail.

Line 1:
%code

var
i, s: Integer;
ASideFiles: TTntStringList;
ASideFile: WideString;
begin
result := '';
if ImageItem.MediumAvailable and ImageItem.MediumLoaded then
begin
for i := 0 to ...

For completeness, I destroyed the two stacks, removed all images from the database, scanned the folder for new files, refreshed the screen to get rid of weird partial duplicate stacks, and got this perfect result.

This is related to issues I've been raising in a separate post where it is difficult to control assignment of Stack Markers through Custom File Masks. Now I am documenting issues related to assigning the Top Item to a stack programmatically. This image shows a screen shot where two images, both ...

Last post of the day! I am getting better results. My modification of your script does seem to correctly tag the original JPG sidecar. I am still having trouble programmatically selecting the top item but I just noticed something. For some stacks, I am getting red out-of-sync indicators while ...

First jpeg found picks the first jpg from the collected stack.


In what order? It is not clear. The JPG sidecar is the first JPG in the stack when it is first imported into the catalog. That is clearly the 1st JPG Found because it is the only JPG in the stack.

If I edit an image and export two ...

I'm trying to make head or tail out of your suggestion. FIrst I noted that it only deals with files containing "-edited" so I added additional NewGUIDs when the file contains any of "-email", "-instagram", et al. I think this logic is correct and it is a simple way to deal with all the additional ...

Note that choosing "First JPEG Found" works as the rule for identifying JPG sidecars *only* works when the JPG sidecar is the displayed member of the stack. When I select an edited file as the displayed stack member, remove all stack markers, and perform stack detection, the edited file is assigned ...

Could you explain what the file mask "First JPEG Found" is meant to return?

I'm cleaning up past work by removing all stack markers and re-assigning them. I am getting decent results with "First JPEG Found" though I had rejected that solution a long time ago. I could have committed a "user error ...