@sgospodarenko and @alex while testing potential “issues” with the ‘S’ icon I ran into a problem where PL5 completely missed a series of changes made to the ‘Rating’!
-
Clear down database.
-
Reset test data ‘Ratings’ using PL5, i.e. all to ‘Ratings’ = 5 (could have copied baseline but this way seemed easier!?) AS(ON)
-
Set AS(OFF) in ‘Preferences’
-
Used Bridge to change every other Image to ‘Rating’ = 1
Outcome:-
-
PL5 trapped the first change and set the icon, I paused in the changes at that point to make sure everything was O.K.
-
Every other change was missed by PL5 and the ‘S’ is missing in the display and in the database, except for item 9.
-
The final entry, item 10, is a mystery because it should never have been set to 1. Except that it is a hangover from a previous test .
Please note that I “fumbled” parts of this test but while I believe that the “fumble” may give a clue to the developers of where the faults might, the fault is still a fault.
So what do I think might have happened.
-
Image 10 might have been set to one in a previous test and not set back to 5 in PL5.
-
When I set Image 3 onwards to ‘Rating’=1 I didn’t do it properly, i.e. I was touching the ‘Rating’ in Bridge but not correctly selecting the first ‘star’ until I realised the problem on image 9 and did the job properly.
-
It is possible that at that point (when making the successful change to Image 9) I realised that Image 10 had the wrong ‘Rating’ and set ‘Rating’=5.
-
I then went back and set Image 3, 5 and 7 correctly to ‘Rating’ = 1.
At step 3 and step 4 the mismatch should have been recognised, the database updated and the ‘S’ icon set but that did not happen!
Please consider the ‘Compare’ option that I keep pushing for very seriously and also use the database flag to incorporate the three ‘Out of Sync’ scenarios of 1 = Image > PL5, 2 = PL5 > Image and 3 = Both (1 + 2) and set the pointers on the ‘S’ appropriately.
The fact that those pointers exist almost indicates that had been thought about before limiting the product to only scenario 1.
I have managed to “wrong foot” PL5 on a number of occasions. I would also respectfully request that DxO review the detection process and how it might be defeated by the “fumbled” operator actions I described!