132 results found

1. UXP Multipanel-Plugin Flyout Bug

   Product: Adobe InDesign
   Version: 20.5
   Forum post: https://forums.creativeclouddeveloper.com/t/flyout-menu-with-mutli-panel-plugins/11436/2

   When creating a multi-panel UXP plugin and attaching a flyout menu to one of the panels, the flyout menuappears on a different panel than the one to which it is defined.

   Steps to Reproduce
   1. Create a UXP plugin for InDesign with multiple panels.
   2. In the plugin’s entrypoints.setup, define a flyout menu for one of the panels.
   3. Load/activate the plugin so all panels are present.
   4. Look to which panel the flyout-menu gets attached. It's probably not the one defined in the entrypoints.setup.

   Expected Result
   The flyout menu appears at the panel where it was defined (i.e. the menu is bound / attached to the correct panel).

   Actual Result
   The flyout menu instead attaches to a seemingly random panel, not necessarily the one in which it was defined. It may be possible that it's randomly placed at the correct panel, though in my cases it was always wrong. It's not always the last panel defined (in one case it was the third panel with a total of four, though the menu was attached to the first panel in the entrypoints.setup.

   Additional Notes
   • The issue appears specific to InDesign. According to the forum post, the same plugin works correctly in Photoshop: each panel gets its proper flyout menu. 
   • Bug was affirmed by another user in the forum post

   I was going to upload a test-plugin demonstrating the issue. But weirdly I can neither upload a zip file nor a ccx file, which is weird for the official place to report bugs. You can get the test file from the forum post though.

   Product: Adobe InDesign
   Version: 20.5
   Forum post: https://forums.creativeclouddeveloper.com/t/flyout-menu-with-mutli-panel-plugins/11436/2

   When creating a multi-panel UXP plugin and attaching a flyout menu to one of the panels, the flyout menuappears on a different panel than the one to which it is defined.

   Steps to Reproduce
   1. Create a UXP plugin for InDesign with multiple panels.
   2. In the plugin’s entrypoints.setup, define a flyout menu for one of the panels.
   3. Load/activate the plugin so all panels are present.
   4. Look to which panel the flyout-menu gets attached. It's probably not the one defined in the entrypoints.setup.

   Expected Result
   The flyout menu appears at… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. InDesign 2026 crash on UXP plugin shutdown – regression bug

   This bug appeared in InDesign 2025 v20.4.1, then was fixed in InDesign 2025 v20.5 (see this thread: https://indesign.uservoice.com/forums/913162-adobe-indesign-sdk-scripting-bugs-and-features/suggestions/50122545--id-4265726-error-during-shutdown-uxp-plugin-inde).

   The bug is present again in InDesign 2026 v21.0

   Philip

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. [ID-4265726]Error during shutdown UXP plugin (InDesign 20.4.1)

   If you try to access indesign.app when shutting down a plugin, an error is thrown and causes InDesign to freeze. Specifically, in the lifecycle hook »hide« and »destroy«.

   The error occurred with version 20.4.1

   ---

   Exception: Error: Shutting down in progress, can't process! at Object.cleanup (/Users/<username>/Desktop/UXP-Panel-Dummy/pkg/panel/hide.js:26:24) at ./main.js:58:31 at new Promise (<anonymous>) at e.exports.hide (./main.js:57:16) at e.exports.destroyPanel (uxp://uxp-internal/pluginmanagerscripts.js:2:38052)
   app: Application {conditionalTextPreferences: undefined}
   docCount: <unreadable>

   this: Object

   A dummy plugin can be downloaded here:
   https://kdrive.infomaniak.com/app/share/1606376/3efc4813-cd2e-40a1-9844-193d31807628

   How to reproduce the error:
   1: Load plugin in UDT
   2. Unload plugin in UDT

   Here is a report from another user: https://forums.creativeclouddeveloper.com/t/indesign-20-4-1-issue-with-the-destroy-lifecycle-hook/11133

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Closed: Fixed  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2025(v20.5.0.048). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

4. UXP, InDesign: WebView postMessage does not work in 20.4

   Since version 20.4 of InDesign, sending messages to the WebView element no longer works. Here is a dummy plugin to reproduce the behavior.

   https://kdrive.infomaniak.com/app/share/1606376/dbdbc8c1-10c3-4c9a-b4ce-d048fc2864fd

   How to test?
   Click on the “Send message” button.

   Expected behavior?
   The message “Hello form panel!” appears in the Webview element (white background).

   In InDesign 20.3 it works, from 20.4 no longer.

   Why is this important?
   This affects the functionality of one of my published plugins.

   Code:

   Plugin:
   const sendMessageButtonElem = document.getElementById("send-message-button");
   sendMessageButtonElem?.addEventListener("click", () => {
   /* Send message to WebView */
   const webviewElem = document.getElementById("webview") ;
   webviewElem.postMessage({
   "message": "Hello from panel!"
   });
   });

   ---

   Webview:
   /**
   * Window message event listener
   * Receive messages from Plugin
   */
   window.addEventListener("message", panelMessageHandler);

   /**
   * Panel message handler
   * @param evt
   * @returns
   */
   async function panelMessageHandler(evt: MessageEvent) {
   const webviewMessageOutputElem = document.getElementById("webview-message-output") as HTMLElement;
   webviewMessageOutputElem.textContent = evt.data.message;
   }

   Since version 20.4 of InDesign, sending messages to the WebView element no longer works. Here is a dummy plugin to reproduce the behavior.

   https://kdrive.infomaniak.com/app/share/1606376/dbdbc8c1-10c3-4c9a-b4ce-d048fc2864fd

   How to test?
   Click on the “Send message” button.

   Expected behavior?
   The message “Hello form panel!” appears in the Webview element (white background).

   In InDesign 20.3 it works, from 20.4 no longer.

   Why is this important?
   This affects the functionality of one of my published plugins.

   Code:

   Plugin:
   const sendMessageButtonElem = document.getElementById("send-message-button");
   sendMessageButtonElem?.addEventListener("click", () => {
   /* Send message to WebView */
   const webviewElem = document.getElementById("webview") ;
   webviewElem.postMessage({
   "message": "Hello from panel!"
   });
   });

   ---

   Webview:
   /**… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   FIXED  ·  AdminSanyam Talwar (Senior Lead Software Engineer, Adobe InDesign) responded

   The fix of the issue is now available in the latest InDesign 2026(v21.0.0.192). We recommend you upgrade to the latest version for the fix.

   If you are unable to see the update, go to the Creative Cloud application, click on the context menu on the top right, and click on Check for App Updates.

   —

   Adobe InDesign Team

5. UXP logs in the wrong folder

   The UXP logs for InDesign 2026 still end up in the 2024 folder.

   Wouldn't it be more consistent to adjust the path to the corresponding version?

   InDesign 21.0, macOS Sonoma

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UXP plugins  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. InDesign 21.0 UXP: File URI scheme

   With InDesign 21.0, my plugin can no longer access files in the plugin folder when using the standard file uri scheme: file:///pathToFile (3 slashes).

   Error: Could not find an entry of 'file:///Users/<user name>/Library/Application%2520Support/Adobe/UXP/Plugins/External/9e463c3edemo1.2.2/assets/files/main.css'

   I use:

   uxp.storage.localFileSystem.createEntryWithUrl(url.href, {
   "type": types.file
   })

   It works:
   - in 2024 and 2025
   - when loading the plugin via the Adobe UXP Developer Tool
   - with file:/pathToFile (just 1 slash)

   It doesn't work:
   - when installed (via double-click).

   Is this a bug, or does it mean we can no longer use the standard URI (https://en.wikipedia.org/wiki/File_URI_scheme)?

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UXP plugins  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. checking text object with isValid breaks reference

   I have already described this issue on creative cloud forum for devs: https://forums.creativeclouddeveloper.com/t/accessing-isvalid-property-updates-object-reference/11477

   but since there was no response, i still don't know if this a bug.

   Basically, reference to text object updates after checking it with isValid.

   Steps to reproduce:

   1) get selected text in textframe with app.selection[0] and put it in the variable (selection)
   2) add some text just before selected text
   3) try to select selection with app.select(selection) -> text selected correctly.
   4) check selection with isValid (selection.isValid)
   5) try to select selection once again with app.select(selection) -> text selected incorrectly.

   Indesign version: 19.2
   Expected behavior: preserve link to initially selected text

   I have already described this issue on creative cloud forum for devs: https://forums.creativeclouddeveloper.com/t/accessing-isvalid-property-updates-object-reference/11477

   but since there was no response, i still don't know if this a bug.

   Basically, reference to text object updates after checking it with isValid.

   Steps to reproduce:

   1) get selected text in textframe with app.selection[0] and put it in the variable (selection)
   2) add some text just before selected text
   3) try to select selection with app.select(selection) -> text selected correctly.
   4) check selection with isValid (selection.isValid)
   5) try to select selection once again with app.select(selection) -> text selected incorrectly.

   Indesign version: 19.2
   Expected behavior: preserve… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. macOS error -2740: Enable access to helpful InDesign scripts (Accessibility & more)

   Since macOS Sequoia, AppleScript calls in JSX scripts – especially those using curl or doShellScript – are blocked by the system. This prevents tools like Octopus from running (error -2740), even when installed correctly and granted full accessibility permissions.

   This is especially critical in light of the upcoming European Accessibility Act: Octopus greatly supports the creation of accessible PDF/UA documents by automating ALT text management, export tags, and other metadata – all of which are still very manual in native InDesign.

   Beyond accessibility, Octopus also offers powerful features for GREP automation, quality control, and editorial workflows.

   Suggestion: Adobe should either provide a system-friendly way for such scripts to work – or even better: integrate key Octopus functionalities directly into InDesign, e.g. as an official accessibility panel or workflow tool.

   Since macOS Sequoia, AppleScript calls in JSX scripts – especially those using curl or doShellScript – are blocked by the system. This prevents tools like Octopus from running (error -2740), even when installed correctly and granted full accessibility permissions.

   This is especially critical in light of the upcoming European Accessibility Act: Octopus greatly supports the creation of accessible PDF/UA documents by automating ALT text management, export tags, and other metadata – all of which are still very manual in native InDesign.

   Beyond accessibility, Octopus also offers powerful features for GREP automation, quality control, and editorial workflows.

   Suggestion: Adobe should either… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java Script  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. TypeScript Definitions for InDesign UXP

   Do we have an ETA on when we should expect TypeScript Definition files for UXP in InDesign?

   Currently both Photoshop and Premiere Pro have auto-generated types from their respective teams. This is really crucial for UXP adoption and reliable development.

   Also posted in the forums: https://forums.creativeclouddeveloper.com/t/typescript-definitions-for-indesign-uxp/9098

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. No consistent way to control undo/redo of script execution

    In a UXP plugin, there is no consistent way to control the undo/redo stack.

    The closest we have is through app.doScript, but this is fraught with many issues.

    1. When you run an async UXPScript (most would be, if working with files), the undo mode is ignored.
    2. You can run extendscript, but as we are trying to move away from that I would like a uxp supported solution. In general, we have run into issue after issue with app.doScript using extendscript.

    Ideally, you would fix item 1 and also some of the surrounding issues with UXP script execution (no way to wait for result? documentation seems to be incorrect as well).

    In a UXP plugin, there is no consistent way to control the undo/redo stack.

    The closest we have is through app.doScript, but this is fraught with many issues.

    1. When you run an async UXPScript (most would be, if working with files), the undo mode is ignored.
    2. You can run extendscript, but as we are trying to move away from that I would like a uxp supported solution. In general, we have run into issue after issue with app.doScript using extendscript.

    Ideally, you would fix item 1 and also some of the surrounding issues with UXP script execution (no way… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  UXP plugins  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Need Control over Adobe Fonts

    Currently there is no straightforward way to detect Adobe Font usage in a document. There needs to be an API to determine which fonts are used in the document (exists) and of those fonts which of them are auto-activated Adobe fonts (does not exist). In addition, it would be great to expose an method for forcing Adobe Fonts used in the document to be activated, and for monitoring the status of the activation. Of course, you can enable auto-activation for the document to trigger when it is opened, but this seems somewhat unreliable in our experience, and in any case there is no method to monitor the state of the font activation, so the plug-in does not know when the activation has been completed.

    Currently there is no straightforward way to detect Adobe Font usage in a document. There needs to be an API to determine which fonts are used in the document (exists) and of those fonts which of them are auto-activated Adobe fonts (does not exist). In addition, it would be great to expose an method for forcing Adobe Fonts used in the document to be activated, and for monitoring the status of the activation. Of course, you can enable auto-activation for the document to trigger when it is opened, but this seems somewhat unreliable in our experience, and in any case… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Request for Full Support of Persian Standard Half-Space (\u{200C})

    Subject: Request for Full Support of Persian Standard Half-Space (Zero-Width Non-Joiner: \u{200C}) in Adobe InDesign

    Dear Adobe Support Team,

    I am reaching out to highlight some significant issues with Adobe InDesign’s handling of the Persian half-space character, also known as the zero-width non-joiner (ZWNJ), encoded as \u{200C}, which is widely used and essential for accurate Persian typography. InDesign currently does not fully support this character, which leads to numerous issues that affect document formatting and usability for Persian-language users.

    Specific Issues with Persian Half-Space Support
    Text Import from Microsoft Word: When importing Persian text from Word documents that contain ZWNJs, InDesign often fails to recognize and interpret the half-space correctly. This leads to formatting disruptions, broken words, or incorrect letter joining, impacting the text flow and readability.

    Headers: If the half-space character is present in headers, InDesign may not handle or display it properly, which can result in incorrect alignment or missing characters, detracting from the document's professional appearance.

    Indexing Issues: During index creation, InDesign does not correctly recognize the half-space character within Persian words. This causes indexing errors, which are particularly problematic in Persian publications, as they lead to incomplete or inaccurate index entries.

    Dictionary and Spell Check Errors: Although custom Persian dictionaries include the ZWNJ character, InDesign frequently fails to recognize words containing it, incorrectly flagging them as misspelled. This hinders the efficiency and reliability of the spell-checking and proofreading process.

    The ZWNJ character (\u{200C}) is essential for proper Persian script handling, as it controls word joins and ensures accurate typesetting. Addressing these issues would greatly enhance the software’s functionality for Persian-speaking users and improve the precision of Persian-language typesetting in Adobe InDesign.

    Thank you very much for your attention to these concerns. We hope that the Adobe team will prioritize full support for the Persian half-space character in future updates to InDesign. Your support on this matter would make a substantial difference for Persian-language users worldwide.

    Sincerely,

    Subject: Request for Full Support of Persian Standard Half-Space (Zero-Width Non-Joiner: \u{200C}) in Adobe InDesign

    Dear Adobe Support Team,

    I am reaching out to highlight some significant issues with Adobe InDesign’s handling of the Persian half-space character, also known as the zero-width non-joiner (ZWNJ), encoded as \u{200C}, which is widely used and essential for accurate Persian typography. InDesign currently does not fully support this character, which leads to numerous issues that affect document formatting and usability for Persian-language users.

    Specific Issues with Persian Half-Space Support
    Text Import from Microsoft Word: When importing Persian text from Word documents that contain ZWNJs,… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  C++ SDK  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Problem related to half space in the dictionary

    "When the Persian dictionary is fully added to the software through the method explained on your website, the software incorrectly identifies words that use half-space as incorrect, even though the exact word exists in the .DIC file and the spelling rules are defined in the .AFF file. Please investigate this issue as it is very important.

    Thank you."

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  InDesign Server  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. BUG: Fix the multiple panel issues in the InDesign UXP plugin framework

    Please fix the panel bug:
    https://forums.creativeclouddeveloper.com/t/uxp-entrypoints-setup-loads-same-panel-always/8026

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  UXP plugins  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Simple script crashes vanilla InDesign 2024 19.5 Debug version

    Running this simple script (tested on Mac x86, Mac M1, and Windows) will crash Adobe InDesign 2024 Debug. It will not crash Adobe InDesign 2024 (regular version).

    • 

    • 

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. html5

    In indesign desktop version, new functionality to export document directly to html5 is added. We are looking to use the new html5 export functionality with Indesign Server. Seems it's currently not possible to write a script or a plugin to export documents to html 5 other than manually via desktop InDesign UI. (no reference found in SDK documentation)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  InDesign Server  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. corrigir bug

    Muitos arquivos RTF estão com problemas para ser importado, o indisign acaba fechando. Observação: os arquivos RTF possuem muitas páginas (média de 500 páginas)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  InDesign Server  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. implement control of layers Composition of imported photoshop file with javascript

    implement control of layers Composition of imported photoshop file with javascript

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java Script  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Inserted special character for current page number is not refreshed from the plugin since version 20.0

    Inserted special character for current page number is not refreshed from the plugin since version 20.0.
    In previous versions, after adding a new section using kNewSectionCmdBoss, the page information was refreshed.
    Now the section is changing, the page number in the information bar at the bottom is correct, but the page number in the text frame with inserted special character has stopped updating.

    When the same is done via the Sections window in Indesign (Numbering & Section Options) with the start of new section field set, it works.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. FINESTRA DEI COLLEGAMENTI

    Come nella immagine allegata, la parte delle informazioni di collegamento appare trasparente. Così risulta illeggibile e inutilizzabile.

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating