Categories will not stick

jthorsson · November 09, 2018, 05:54:49 PM

I have a problem with just one of my categories. Suddenly I can only apply it to one single image at a time, if I select more than one file then only the last file selected is assigned the category. Has anyone experienced this?

I have run "database diagnostics" and "repair and optimize" but that did not help.

Mario · November 09, 2018, 06:35:45 PM

Check the properties of the category in the Category View. Any unusual settings?
Do you use Versioning and category propagation perhaps?

photokal · November 09, 2018, 07:59:57 PM

Hi, Mario.
I've just starting seeing this as well, with the release of 2018.11.2. I have some categories for which Assignment Action is set to Un-assign from siblings. It is these categories that are not being set when applying to multiple images at one time. When the category is assigned, I can see the it being applied to all but then the selected category goes grey (as when only applied to one item) and it is applied to only the first selected file. If the category's Assignment Action is set to None, I can apply to multiple files.
Let me know what logs/tests you would like to see, if any. Hope this helps track down the issue.

ColinIM · November 09, 2018, 10:04:24 PM

Yes, I'm seeing this too.

As mentioned above, I see this behaviour on sets of sibling Categories where each sibling's Assignment Action is to 'unassign from siblings'.

I'll add a Bug Report (a few minutes after finishing this post) and I can include a Debug-level LOG file.

In my experience today it seemed that the only file that 'gets' the assignment is the one that IMatch indicates was the 'last Added' to the folder, regardless of the current File Window Sort profile.

(I ran my tests on multiple selected files in a single folder. I did not try using Search Result Windows as my source of selected files.)

As a test - I freshly-modified one of files in the set and did a Write Back to see whether the Last Modified file would become the 'lucky' one to get the intended Category assignment, but no ... it seemed (in my case) again that only the 'last Added' file from a multiple selection would keep the intended assignment.

Mario · November 10, 2018, 08:08:45 AM

This has already been reported as a bug: https://www.photools.com/community/index.php?topic=8508.msg59880#msg59880
I will look into this at the nearest opportunity and report my findings in the bug report thread linked above.

jthorsson · November 10, 2018, 11:39:41 AM

Thank you for your prompt response!

sinus · November 21, 2018, 10:15:33 AM

That's a pretty bad bug in my eyes.
If you don't pay attention and select a lot of pictures (like you did before) and then add several categories to them, then you might end up with a "category chaos" with these pictures.
If you're not careful and just use your favorite categories as usual, and work with multiple categories, you may discover this much later.

That's how it happened to me, because I noticed it late - and it takes a lot of time to put everything back in order.
If you also have a category structure like the thread creator and others, then be careful at the moment.

My 2-cents.

Mario · November 21, 2018, 10:25:57 AM

This bug has already been reported and fixed for the next release.

Please see the release notes for the next release for up-to-date information about the bugs found and fixed for each release:

https://www.photools.com/release-notes/

Keeping an eye on the bug report board in this community (subscribe to it so you get emails) and the release notes for the upcoming version allows you to tell if a bug as been identified that may affect you.

Only a small fraction of users (as per initial telemetry data) is affected by this problem - because only a few % (< 2) of users work with automatic unassignment categories.

The next IMatch release is scheduled for December.

sinus · November 21, 2018, 10:38:53 AM

Quote from: Mario on November 21, 2018, 10:25:57 AM
This bug has already been reported and fixed for the next release.

Please see the release notes for the next release for up-to-date information about the bugs found and fixed for each release:

https://www.photools.com/release-notes/

Keeping an eye on the bug report board in this community (subscribe to it so you get emails) and the release notes for the upcoming version allows you to tell if a bug as been identified that may affect you.

Only a small fraction of users (as per initial telemetry data) is affected by this problem - because only a few % (< 2) of users work with automatic unassignment categories.

The next IMatch release is scheduled for December.

Thanks,
Yes, I know about the release notes and the bug-report.
I wanted only stress this again. Even if you are one of these <2% of persons, this can have quite some troubles for your DB, if you do not look exactly, what you do.
It's almost like that when only 5 people out of 1000 are injured in a bad event, one is inclined to say that only 5 people are injured ... but for the 5 it can still be very unpleasant.

But of course, super, that you have fixed this bug. Very good.

Mario · November 21, 2018, 10:46:54 AM

Bugs can happen. All software has bugs. Some bugs, even in prominent software produced by large software vendors, stay for years.

This bug has already been reported, analyzed, fixed, published and explained in the release notes.
Please understand that I cannot stop everything I'm doing and rushing out a new IMatch update all the time. I may be knee-deep in other projects. And, sometimes, even Mario needs a break.
The bug fix will be included in the next regular release. It's not critical for the majority of users, and users have been informed about the bug last week already.

sinus · November 21, 2018, 10:59:10 AM

Quote from: Mario on November 21, 2018, 10:46:54 AM
Bugs can happen. All software has bugs. Some bugs, even in prominent software produced by large software vendors, stay for years.

This bug has already been reported, analyzed, fixed, published and explained in the release notes.
Please understand that I cannot stop everything I'm doing and rushing out a new IMatch update all the time. I may be knee-deep in other projects. And, sometimes, even Mario needs a break.
The bug fix will be included in the next regular release. It's not critical for the majority of users, and users have been informed about the bug last week already.

Of course I understand that and of course every software has bugs.
Maybe I wrote it badly understandable, sorry in this case.

I didn't ask anything of you either. I just wanted to draw your attention to this bug again. If it helps nobody here of the forum, ok, then it makes nothing.

If it only helps a single user, who hasn't noticed that before, then it has already been a help for this single user.
And that's what this forum is for, I think.

And I think, btw, this here is a very good forum.

Mario · November 21, 2018, 11:17:04 AM

QuoteI didn't ask anything of you either. I just wanted to draw your attention to this bug again.

This is unnecessary.
The bug has already been reported, discussed, explained, fixed and added to the release notes.

sinus · November 21, 2018, 12:50:51 PM

Quote from: Mario on November 21, 2018, 11:17:04 AM
QuoteI didn't ask anything of you either. I just wanted to draw your attention to this bug again.

This is unnecessary.
The bug has already been reported, discussed, explained, fixed and added to the release notes.

Ahhhhhhhh, sorry stupid me and (in this case) DeepL-translator.
As you can see in my second sentence, I meant not your attention, but the attention of the users (otherwise my second sentence would not make sense):

quote:
"I just wanted to draw your attention to this bug again. If it helps nobody here of the forum, ok, then it makes nothing."

Lesson for me: read again, what translators does translate.

Ok, this is my last post in this thread.