PS CC 2018 breaks previously OK Extendscripts

[FitzFoto]

An early 'heads-up', a number of ExtendScripts that were working under PS CC 2015.5 and PS CC 2017 no longer work.  A number give inexplicable errors in the UI code.

I am investigating and will revert.

[Chuck Uebele]

You will need to post some code where your scripts stop working.

[FitzFoto]

Why?  I'm not asking for help.

[JJMack]

Posting an example would give your thread credibility. Are you just trolling? 

[FitzFoto · Accepted solution]

I am not trolling.  I have posted only a few questions previously as after over 50 years of IT (EDP) I am usually able to sort out problems for myself.  This was not a question, merely a "heads up" in regard to what was at the time a repeatable error, and I did say that I was investigating.

Posting an example would have been pointless, as the code was working under 2015.5 and simply gave "Illegal function" under 2018.  There is nothing wrong with the code.

The problems have since ceased, and appear to have been connected to High Sierra, as the code worked under Win10 (run from the PC folder on both Mac and PC systems to be certain).

I am closing the matter here.

[JJMack]

So you are posting that there are Mac High Sierra and Photoshop CC 2018 problems.  That's better then what you first posted.

[FitzFoto]

At the time of posting I was not aware that the issues were limited to High Sierra.  I did post that they were with PS CC 2018.

i have marked an answer (my own, as it happens) as correct.  This thread is now ended.  Thank you for your participation.

[Davide_Barranca]

Grimbaldus if you happen to narrow down the function / property / whatever that caused the issue you're experiencing, please let us know. If there's something wrong with High Sierra, it's always good to know.

Thank you

[FitzFoto]

Davide

Per my 3 Nov @ 13:55, the problems have "gone away".  They all appeared to be connected to UI code, but the errored line was not always highlighted in the editor, so it was hard to say.  However, some onClick and onChanging events did not execute in a predictable manner, and statements involving the .value of checkboxes would error.  Catch was trapping the errors, but the sole message was "Illegal function" for a script that ran faultlessly on a Win10 PC from the same file.

I inserted breakpoints, but these were inconsistent, and occasionally "fixed" the problem.  Removing them generally, but not on every occasion, reintroduced the error.  $.writeln (s) inserted after every line showed normal progress through the code, but still generated the error.

So some errors were repeatable, and some not.  Not every script containing common UI code would error.  Weird!

The last time I had a similar puzzler with uncompiled code we traced it to a cracked ferrite core that would sometimes switch state and sometimes not.  That was around 1967.  

Thank you for your interest.

[Chuck Uebele]

Sounded like you might have wanted help, and if not, posting an example would let any Adobe staff, who happen to see this know where to look for issues.

[FitzFoto]

Well, thank you for your interest and concern, but I did say "heads up", and that I was investigating.

[JJMack]

All versions of Photoshop has Problems.  Adobe acknowledges some reported bugs on their feedback site. However, Adobe does not fix all the bugs they acknowledge.  Bugs go unfixed release after release and with each new release of Photoshop that bug list grows.  Adobe need to stop and adding bugs and fix the bug they acknowledge.