My event scripts do this:
- check image pixel dimensions and assign categories according to my criteria concerning aspect ratios
- automatically stack images from stitched pictures and HDRs (see https://www.photools.com/community/index.php?topic=5358.0) according to my naming convention (can't do this any other way, like automatic stacking, etc), propagating categories from the source images to the stitched/HDR image. In a next step I also planned to copy GPS info.
- automatically assign images to event categories
See attached Photos.bas file
It's not much code and I don't want to spend weeks learning new languages and tools just to convert this. I've never used javascript, JSON (?), Visual Studio Code (used Visual Basic and Visual C++ 10 years ago), don't know what a "promise" is, don't need a visual interface (no HTML), ... It's just too much. It feels like using a hypercomplex supercomputer as a desktop calculator.
If I get past the database error I now receive with the restored db and iMatch 5.8, I'll stick with that for as long as possible. It just worked.
Hi Carlo
I feel with you. I have also some scripts, what are really good for my workflow and they work not more with IMatch2017.
Hence I do work still with IMatch 5. There all is good.
Finally I do not need really something from the new 2017-version.
But the day will come, when it works not more, for example if a new windows-version comes out, or I do not know. But I think, that IMatch 5 will work for me still without problems this year and almost for sure also the next year, even without official support from Mario.
On the other hand new stuff comes out with IMatch2017, what I do not really need, but what is fancy. For example the speed is much better with IMatch2017, I have read. And some other things, what is not really essential for me, but nice to have.
And if Mario does for example enhance some other stuff (design & print or calculate attributes-fields or whatever), then I will be out also.
Hence my personal way is to use the "old" good IMatch 5.
In the mean time, parallel, as often as I have time, I do think about my workflow, if I can make it easier.
And I do lern for me some basic of JavaScript, what gives me some good possibilities, because I can JS also use on my website or personally.
And on my laptop I have the new IMatch2017 as trial (for now), and I have a look at the apps and JS and yes, it can be overhelming, all the stuff. But I will concentrate on that things, what I need, not the other (fancy) things, becasue it can be simply too much for me, finally I am a photographer and not a programmer.
In my case I do concentrate on how I can pull out attributes - fields, calculate them and put it into word-doc.
If I can get this (what can be end of the year or whenever), then I will change to 2017, not before.
In your case I do not know, if you could rethink about your workflow (data-driven-categories?) and try maybe an easy script in JS, that you can use your workflow, like you do now.
Check image pixels and add them to categories, I do not know (now), but I guess, this should not be a very difficult task for JS (but yes, what is easy for scripters, can be difficult for us "poor scripters").
I hope, you can find a way, now or later for your good old workflow or a new (better) one.
S
