Skip to main content
J
jasuryusupov
Known Participant
November 8, 2023
Question

Few questions about InDesign Debug version

  • November 8, 2023
  • 2 replies
  • 309 views

So I've joined the Developer Prerelease program and installed Debug version of InDesign in order to debug a plugin that I'm developing using InDesign SDK. I've faced several issues, so in this post I want ask few questions regarding those.

 

1. When I launch the Adobe InDesign (Prerelease-Debug), wether directly or through VS debugger, all the changes that I made in the previous session get reset. For example, workspace goes back to "Essentials" from "Advanced"; Selections get reset to default in the Test > TRACE menu. For example "Hyphenator" gets back to its unchecked state, so I cannot see logs related to it during the launch of the InDesign.

Surely, I can replace all TRACEFLOW calls with TRACE to log them, but was wondering why my configurations are getting reset, and if there any solutions for it.

 

2. Constantly getting Assert window popping-up, saying "No translation of key 'Uzbek: Latin' to English string".

I'm using the Hyphenator project from sdksamples, and installing a new language. I'm assuming I need to define new strings in string-table resource files like "Hyp_enUS.fr" and then reference them with PMString in my program. But wonder if its a correct approach, since program doesn't show assertion pop-ups for other languages defined in there like "Spanish: Castilian" straightly without referencing their name with PMString. Maybe language related names need to be defined in other file?

Besides that, I'm also seeing bunch of "Warning:No translation of key 'Share' to English string" messages in the MSVC logs, but they are not popping-up in an Assert window.

 

3. What is "Debug Settings.xml" file that gets opened via WordPad when I press "Open Traces" button from Test -> TRACE menu, is there any guide/documentation on what that file is and how to use/modify that file? Also, what other related options do: "Clear traces", "Remove disabled Traces", "Load Traces" and "Save Traces". Because I see no changes when I press those buttons, except the "Remove Disabled Traces" one that removes list of traces

    This topic has been closed for replies.

    2 replies

    Steve Werner
    Community Expert
    Steve WernerCommunity Expert
    Community Expert
    November 11, 2023

    I agree with @Manan Joshi . Quesions for a prerlease program should never posted on this forum. The information you receive in a prerelease program is under NDA.

      M
      Community Expert
      Manan JoshiCommunity Expert
      Community Expert
      November 11, 2023

      Ok, here is my take to the problem.

      • You are testing prerelease version of Debug? If that is the case then most of these issues could be attributed to it being a prerelease version. If something is blocking you then use the proper debug version not the prerelease one and then see if it resolves the problem. I suppose you can download the debug version directly from the Creative Cloud desktop app if you are a member of the relevant prerelease program.
      • Are the translation assert for the strings used/defined in your plugin? If so then yes you need to either add it to the translation files or make the string non translatable. This can be done in the fr files.
      • I have never used the DebugSettings.xml. I am not aware if it is meant to be used by 3rd party developers.
      • Lastly, even the debug version and even release version for that matter have lots of asserts. If you launch the release version using a debugger you will see many messages popping up on the console. So if the messages don't make sense for your code and is presented regardless of your plugin being loaded or not then ignore it and move ahead. The debug version also shows a "Disable Asserts" button on the assert dialog so that you can stop them and focus on your debugging.

      I would say if you are blocked on anything regarding the prerelease version the better place to post would be the prerelease forum.

      -Manan

      -Manan
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices