Main Menu

Recent posts

#71
General / Re: External Icon File Glitchy...
Last post by Mario - April 13, 2024, 06:49:32 PM
Ribbons are my code.

I even went as far as installing IMatch 2023.8.6 on a fresh Windows 11 installation in a VM.
Added two favorites with external icons (one in the "Pictures" folder, on in "c:\data\icons") and added both icons to the toolbar/ribbon. It works flawlessly with either toolbar or ribbon. Closing and re-opening IMatch restores the icons. No problems at all.

Image1.jpg
External icons used for favorites for a fresh IMatch 2023.8.6 installation on a clean Windows 11.

No repro case.
#72
General / Re: External Icon File Glitchy...
Last post by Darius1968 - April 13, 2024, 05:36:08 PM
I should add that this problem is not about that specific database - I created a brand new database, wherein (I) can demonstrate this same problem.  Is there anything third-party about the new file window toolbar?  I'm just trying to determine if there is something that a third-party app might not like about a certain installation. 
#73
General / Re: External Icon File Glitchy...
Last post by Mario - April 13, 2024, 04:46:08 PM
I have no idea and no repro case to analyze this further. All this is very simple and the only log entry happens when the attempt to load an external icon fails. I suggest you use one of the standard icons available for favorites.
#74
General / Re: External Icon File Glitchy...
Last post by Darius1968 - April 13, 2024, 04:43:57 PM
I didn't mean that it was strange that it took a few seconds for the icon to be rendered; I thought it strange that I had to 'reinstate' it after I reopened the database. 

What could be going on that I'm able to 'jump start' things by my copy/paste operation?  Maybe, the log shows no errors, but something must be interfering in the process of opening the database, and that something isn't present whenever I paste the new copy? 
#75
General Discussion and Questions / Re: Something seriously wrong ...
Last post by eyemack - April 13, 2024, 04:27:52 PM
Firstly, I'm not on the trial version.  I was so impressed by IMatch that I bought a licence a few days ago! I'm on 2023.8.6.
Anyway, we are making progress. The 19 image database is now working OK.  With the Metadata 2 optin set and a force update all is looking good. No IPTC metadata showing in a MDA run.
I'm going to try it now on my full database. Fingers crossed!
I'll report back.
Thanks again.
#76
General Discussion and Questions / Re: Something seriously wrong ...
Last post by Mario - April 13, 2024, 04:14:59 PM
I've sent you the two images back.
The one with the house had no legacy IPTC data, but I've added a keyword and a description.
The pool image had legacy IPTC data removed by ECP, then I've added a keyword and a description.
Both files still have no IPTC data.

I did this twice, once with my regular database and again with a fresh database created only for this purpose. In both cases it worked as described above (remove legacy IPTC data, force rescan, legacy IPTC data gone).

Just to be extra sure, I've installed a fresh copy of Windows 11 in a virtual machine, installed IMatch 2023..8.5 (current trial version) trial, created a database and indexed the folder with your original files. Just in case something really weird is going on.

After indexing the images, I verified that the pool image has legacy IPTC data and the house image has none. Both with the MDA and ECP.

1. Removed the legacy IPTC data from the pool image.

2. Did a forced rescan.

3. Pool image shows pen and wants to write back IPTC:keywords

4. Disabled metadata protection for unwritten metadata (Edit > Preferences > Metadata 2)
If this is on, IMatch will not wipe IPTC:Keywords since it is marked as modified.

5. Forced a rescan of the file again.
Legacy IPTC data is now gone from the database and the file shows no pending write-back.

In all three tests, I get the same and expected results.
Did you do a forced rescan after disabling protection?

Now I've also tried to reproduce your original problem with the file.
Restored the original pool image from backup. With legacy IPTC data.
Added the keyword IMatch in IMatch.
Write back the file.

The pen vanished.
The file contains a consistent set of keywords in XMP and IPTC:

[IPTC]          Keywords                       : Holidays, Holidays|Cyprus, IMatch
[XMP-dc]        Subject                        : Holidays, Holidays|Cyprus, IMatch
[XMP-lr]        Hierarchical Subject           : Holidays, Holidays|Cyprus, IMatch

so removing the legacy IPTC data is actually not required at all.
At least not for the sample image I have here.

It may be needed if your other files contain unresolvable differences in keywords between legacy IPTC and XMP.

#77
General Discussion and Questions / Re: Something seriously wrong ...
Last post by eyemack - April 13, 2024, 03:40:37 PM
Nope, still the same pencil with IPTC::Application Record/Keywords message. Just in a loop here and not getting anywhere!
As I said above, if you could spare a few minutes to share my screen to see what's going on, that would be great.
I'm trying to make this work, but at the monent, IM isn't usable for me.  Let's hope we can resolve this.
I have seen another few posts with the same issue in a search for 'exiftools not deleting IPTC metdata'.
#78
Solved Bug Reports (for next version) / Re: VIEWER: a display quirk?
Last post by Mario - April 13, 2024, 03:24:35 PM
I could not reproduce the "ghost" image panel using your description.
I've started with 5 selected files (also tried 7) and selected the images using <Shift> as you describe. selecting from the first to the last, or the last to the first, or randomly selecting files in the film strip using <Ctrl>+click.
When I select 6 images and then deselect one of the images, an empty image panel shows instead of the 6. image.

Played with that for a couple of minutes, trying all variations I could come up with. Also tried on my laptop, which has a Intel graphic card and a separate NVidia card. Same result, no problems. 

I have also seen no similar reports, so this might be a very specific issue on your PC. Maybe it is some sort of DirectX / graphic card artifact?

I could reproduce the second effect. When switching from 1 to 4 images side-by-side, 3 new image panels are created. They start with an origin of 0/0, but the retained image panel kept its origin. I have fixed this for the next release.

If you click an image and release, the origins of all images are synchronized, which is why this solved the issue.
#79
Feature Requests / Re: Friendly Names for Categor...
Last post by Tveloso - April 13, 2024, 02:04:00 PM
I'll be sad to see the Category Bookmarks feature removed, but I understand if it's something you must do.

In my case, the few Category Bookmarks I have created, are for Data Driven Categories (which I understand we cannot create Favorites for).  So it's just a quick way to go to the category, without having to navigate the Tree.

Perhaps IMatch could allow Category Favorites to be created for DD Categories?...(which would provide only that Go-To Functionality?)...
#80
General Discussion and Questions / Re: Categories: show parent di...
Last post by Mario - April 13, 2024, 01:33:49 PM
Quote from: hamishr on April 13, 2024, 10:38:56 AMIn the Category view, if I select a child and another child (with same or different parents) it behaves correctly and I see the associated records for both. However, if I select a child and the parent of the child, only the parent records show. So this doesn't work the way I need it to do. 
When I select the children A,B,C of parent category P, I see the files in A,B,C combined (3 files, one in each category).
When I now also select P, I see 4 files. The 3 files in A,B,C and the one file I have assigned to P for this test.
This is the same result I get when I only select P, since P implicitly contains all files in its child categories (unless you set the direct files only option for P).

PS.: the year 1601 limit is not caused by IMatch (IMatch can store dates like 1407:01:01 in XMP data), but the formatting and output routines in Windows for parsing and displaying dates only handle dates with years >= 1601.
Replacing all date and time formatting routines Windows offers with my own that deal with larger time ranges would be a major task, for a probably minute number of users.