Main Menu

Recent posts

#51
Thanks for the support
#52
General Discussion and Questions / Re: Searching in the Map Panel...
Last post by Mario - July 20, 2024, 09:38:21 AM
Probably your credit card was expired and you did not receive the notice from Google.

Delete the hamburg entry to see the purpose of this input field. Also, the tooltip of the button at the end gives a hint as 
well as the corresponding section in the IMatch help: Searching Coordinates
You probably have typed into the wrong input field at some time. IMatch remembers your last inputs.
#53
Hello,
after a few nights of trying and searching for a solution, I have found the answer!
I don't know why yet, but the problem seems to have been with the google maps api key.
I created a new api key, entered it in IM, and everything works again.
Now I'm noticing something that I can't yet explain.
When I click on "Find Location" in the map, the search window appears. In this window (see attachment) there is a line that says "Hamburg". I had entered "Hamburg" several times as a search criterion during the troubleshooting.
If I delete "Hamburg", close the window and restart IM, I still find "Hamburg" in the search window.
How do I get rid of this?

Frank
#54
General Discussion and Questions / Re: how did you change your Li...
Last post by RobiWan - July 19, 2024, 02:29:04 PM
You can automate a lot of things very well with Imatch. Nevertheless, using one program is always easier than using two.
#55
Any info to share? I'm not sure I understand the problem.
I've had a look at the code, and the PersonInImage seems to be only written when there is an actual change.
Maybe the order or persons has changed by your quite particular workflow with re-import from XMP and that's why the tag was updated and marked for write-back? Can you check that and let me know?
If a face is not detected, PersonInImage may differ. Or the face recognition runs, which means that PersonInImage will be updated multiple times. The order in which faces detection also plays a role, since PersonInImage is ordered by face order. Many variables at play here.
#56
Solved Bug Reports (for next version) / Re: [WF] CSV Import
Last post by sinus - July 19, 2024, 09:00:42 AM
Quote from: cg on July 19, 2024, 04:41:11 AM@Tveloso
Yes! That worked! Before posting, I had previously tried escaping the ~ with \ and /, to no avail. But apparently the ~ is itself the escape character in this context. Thanks!

@Mario
Thanks for checking into this. I now have two options, either escape the ~ or rename the files to remove it. Perhaps the help files could be updated to mention escaping it, instead.

Thank you both!

Edit: and thanks to @thrinn too!




I would clearly change the filename. Using the special character ~ in a filename, is not a good idea. From my point of view.
#57
Solved Bug Reports (for next version) / Re: [WF] CSV Import
Last post by Mario - July 19, 2024, 08:24:10 AM
QuotePerhaps the help files could be updated to mention escaping it, instead.
Using ~ in file names is really not something that should be done. Windows used (and still uses) the ~ when it transforms a long file name (> 8 characters) into a short file name (8.3). And the ~ is used to indicate such shortened file names.

I don't know why you use ~ in your file names, or why escaping ~ with ~~ is better than just removing the ~.
I've added a not that file names should not use ~ to the CSV help.

I can extend that to also mention the ~~ escape trick in the CSV file. But given that ~ should not be used and since 2016 when the CSV import was added to IMatch you're the first user ever that ran into this problem, I don't think that there is a real need.
#58
Solved Bug Reports (for next version) / Re: [WF] CSV Import
Last post by cg - July 19, 2024, 04:41:11 AM
@Tveloso
Yes! That worked! Before posting, I had previously tried escaping the ~ with \ and /, to no avail. But apparently the ~ is itself the escape character in this context. Thanks!

@Mario
Thanks for checking into this. I now have two options, either escape the ~ or rename the files to remove it. Perhaps the help files could be updated to mention escaping it, instead.

Thank you both!

Edit: and thanks to @thrinn too!


#59
Solved Bug Reports (for next version) / Re: [WF] CSV Import
Last post by Tveloso - July 19, 2024, 03:28:23 AM
Could the tilde itself also be escaped, in the same manner as the comma?...(so "~," for paths containing a comma, and "~~" for paths containing a tilde)?...
#60
Solved Bug Reports (for next version) / Re: CSV Import
Last post by Mario - July 18, 2024, 08:00:37 PM
I see what the problem is.
The ~ is used as the escape parameter to tokenize string parameters in post and form data.
This is why the path cannot work.

This is a "Won't fix", sorry.

From the IMWS documentation of the path parameter (used by the Attribute import):

One or more Fully qualified paths for the files to retrieve. Separated by comma.
If path contains a comma, it must be escaped with a tilde ~ => ~, . It neither id nor path are given, all files in the database are returned.

To fix "your" bug I would have to change all that. Sorry, not worth the time and money.
Change the affected file names  in the database (easy to do with a replace step in the Renamer) and do a replace also in your CSV fiile.

I have added a "File names must not contain ~" to the CSV Import help tropic for the next release.

~ is a dangerous character to use in file names (because of the 8.3 feature in Windows) and hence ~ was chosen as the path separator in IMWS.