Adobe InDesign: SDK/Scripting Bugs and Features
2 results found
-
When enums are not an enum but cloaked like an enum
const InD = require ( "indesign" );
InD.Leading.AUTO === InD.Leading.AUTO // false
InD.Leading.AUTO.valueOf() === InD.Leading.AUTO.valueOf() // false
InD.Leading.AUTO.toString() === InD.Leading.AUTO.toString() // trueInDesign version: (latest) 21.4.1
OS: (latest) Tahoe 26.5.2Result: trying to use it in any no-string state throws error: "No data available of the requested type."
Simple description:
( leading === InD.Leading.AUTO ) ? fontSize * 1.2 : leading; // throws error above
leading is set to InD.Leading.AUTO so should be TRUE but...1 vote -
Adobe InDesign UXP documents.add({showingWindow: false}) broken?
All other scripting language allows you to create a new document without showing any window, such as in extendScript documents.add(false), but this seems utterly broken in UXP scripting, and it is not even possible to uses "doScript" as a workaround, because then also the extendscript method ignores the false argument and creates a window.
Bizarrely, if I invoke a uxp script from within applescript (I am on mac) using do script, then documents.add({showingWindow: false}) works in uxp
This indicate to me that there is something fundamentally broken
1 vote
- Don't see your idea?