Copy link to clipboard
Copied
Hi,
I had a custom zoom script for CC 2015 that worked perfectly prior to the recent update.
However, while it shows up in the Scripts panel, when I hover over it, it says:
"This file is not executable by any supported script language."
From what I can tell it's in the correct User Scripts folder as it shows in the scripts panel,
and it had worked flawlessly until the update. It's a .jsx script with the following syntax:
{app.layoutWindows[0].zoomPercentage = 89 } catch (e) {};
Is there something I'm doing wrong, or how can I fix this?
Any help is appreciated, thanks!
(Running on Windows 10)
Solved
Embarrassing rookie mistake!
Strangely the script file was displayed as Zoom89.jsx but there was
a hidden extension of Zoom89.jsx.txt which I removed. Also I edited the script to:
try {app.layoutWindows[0].zoomPercentage = 89 } catch (e) {};
Adding "try" at the beginning seemed to have got it working. Not sure how these
problems occurred. I may have had another script file in a different location
for the CC '15 shortcut.
Anyway thanks for your help!
Copy link to clipboard
Copied
Should work.
What is the file extension of that script. Did you forget to unzip it perhaps? It should be .jsx.
Copy link to clipboard
Copied
Hi TaW,
yeah it's .jsx and unzipped in the User scripts folder. I right clicked the user folder in the scripts panel
and clicked show in explorer...So I'm assuming this is the correct place?
See how the script is greyed out in the Scripts panel?
Copy link to clipboard
Copied
Solved
Embarrassing rookie mistake!
Strangely the script file was displayed as Zoom89.jsx but there was
a hidden extension of Zoom89.jsx.txt which I removed. Also I edited the script to:
try {app.layoutWindows[0].zoomPercentage = 89 } catch (e) {};
Adding "try" at the beginning seemed to have got it working. Not sure how these
problems occurred. I may have had another script file in a different location
for the CC '15 shortcut.
Anyway thanks for your help!
Copy link to clipboard
Copied
It sounded like it was a file extension issue. The try-catch can't do any harm, but definitely was not the issue here...
Anyway, glad you got it sorted.