Re: Exposing plugin to javascript

Article View: adobe.indesign.sdk

Article #61

Back to adobe.indesign.sdk Previous Next

#61

From: Mike_Marconi
Date: Fri, 13 Mar 2009 14:47

8 lines
1133 bytes

For anyone interested I found the problem. The the root fr file in the "VersionedScriptElementInfo" block must have a locale ID declared for any Indesign context the plugin is will be used in.

Using DollyXs if you choose support for Indesign desktop and Indesign server with scripting. DollyXs will only insert the the locale ID for Indesign desktop.

Add the following after the locale for Indesign desktop to enable the plugin for Indesign server;
kFiredrakeScriptVersion, kCoreScriptManagerBoss, kInDesignServerAllLanguagesFS, k_Wild,

Thanks Mike

Technical Details

Message-ID: <59b83245.0@webcrossing.la2eafNXanI>

Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newshub.sdsu.edu!webcrossing

References: <59b83245.-1@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: f63e9,6d0008542c1f1cf6
X-Google-Attributes: gidf63e9,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Mike_Marconi@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.indesign.sdk
Subject: Re: Exposing plugin to javascript
Message-ID: <59b83245.0@webcrossing.la2eafNXanI>
Date: Fri, 13 Mar 2009 07:47:41 -0700
References: <59b83245.-1@webcrossing.la2eafNXanI>
Lines: 14
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message