Copy link to clipboard
Copied
Hi,
I'm on a Mac and ESTK lists all the versions I have with the "common name" (Photoshop CC 2015.5) and the internal version, like 100.032.
What does .032 exactly refers to? 32 bits? Shouldn't all Mac's PS be 64bits?
By the way, is there a way to query PS for its internal version string?
Thank you!
Davide
Copy link to clipboard
Copied
I look at that number every day and say. That should be 100.064. Then I think, I wonder what will break if I change it...
Copy link to clipboard
Copied
So it's a hold over then from 32 bit days, and might not mean anything - but maybe it does. Just check my Win system, and it's all .064
One thing I've noticed with ESTK is that often I can't run a script with it with any version of PS that is open by just using:
#target photoshop
Even if I set the dropdown list to the version I have open. it will ask to open a default version of PS. I will only be able run that particular version is I have the version number in the target line. It seems with just a generic #target photoshop, it should work on whatever is open.
Copy link to clipboard
Copied
Yes. You have to remove that if you have multiple versions installed and you want the old one. The logic is "what is the newest version, attach to it" Having two versions installed and running the old version BridgeTalk will attempt to attach but the detailed version numbers won't match and things stop. Ideally we would give a "wrong version" error or other information to tell you why things have stopped.
Copy link to clipboard
Copied
I normally don't put the version number on the script, just #target photoshop, but as you mentioned, that will only open the latest version, even if I specify in ESTK which program I want it to run. I guess not a big deal, but it would be nice not to have to put the version number on the script for testing if PS is open - especially if you're unsure of what the new number is - if you know what I mean.
Copy link to clipboard
Copied
I never use the #target as I rarely double click a file. I usually right click to "edit in" or drag drop on the Photoshop I am running. I'm constantly using multiple versions of Photoshop so #target always gets in the way for me. You could play some runtime tricks in your scripts to use BridgeTalk to see which versions are installed, which one may be running, and then decide if it is new/old enough to run your script. A lot of work for probably little benefit but would be an interesting bit of code.
When I'm stuck on a tough problem I record my script as an action, assign that action to a hot key. Then I can quickly. Edit (Rinse), Run (Lather), Debug (Repeat)!
That trick is helpful when the ESTK gets in the way of debugging instead of being a helpful debugger...it happens...
Copy link to clipboard
Copied
Thanks, Tom. Yea, using it just for when I'm testing something, and don't want to spend a lot of time messing with workarounds. I normally open ESTK and just run the scripts from there rather than installing them in the right folder for the right version of PS, so that I can run them through the menu.