BroseForDirectory() crashes Indesign.

Hi All,
when i am trying to call browseForDirectory() method from my extension it carshes the indesign, I am a newbee in extension development, please suggest.
I am also handling select and cancle events in my code. for reference i am also posting the code that i am using to do that.
  var cFileReference:File = File.desktopDirectory;
                                        cFileReference.browseForDirectory(File.desktopDirectory.nativePath);
                                        cFileReference.addEventListener(Event.SELECT,fileReferenceSelect);
                                        cFileReference.addEventListener(Event.CANCEL,fileReferenceCancel);
Thanks
Ashif

@kc2scy
You have to place your jsx file inside the resource of your app.
here is a sample
[Embed (source= "Resources/Browse.jsx" , mimeType= "application/octet-stream" )]
                    private static var myScriptClass:Class;
                    public static function runTwo():String {
                              var jInterface:HostObject = HostObject.getRoot(HostObject.extensions[0]);
                              var path:String="";
                              try{
                                        var path:String=jInterface.eval( new myScriptClass().toString());
                              }catch(e){
                                        return "";
                              return path;

Similar Messages

  • [CS3 JS] event crashes InDesign

    Scripting ladies and gentlemen,
    I'm working on this event script that searches for linked PDF files and
    lets the user copy/relink them. Using the afterOpen eventListener however
    crashes InDesign no matter what I do. This is also the case with
    beforeClose. It appears that my function cnvrtPDFlnk is causing the crash
    (I'm able to alert succesfully with the afterOpen event if I //-comment
    the cnvrtPDFLnk(myDocument)).
    Do one of you scripting gurues have a tip?
    #targetengine "session"
    main();
    function main() {
       app.addEventListener("afterOpen", myEventFunction, false);
    function myEventFunction(myEvent) {
       var myDocument = myEvent.parent;
       var label = docLabel(myDocument, "PDFCheck");
       if(label) {
          //myEvent.stopPropagation();
          //myEvent.preventDefault();
          exit();
       else {
          cnvrtPDFLnk(myDocument);
    function docLabel(myDocument, key) {
       var hasLabel = (eval(myDocument.extractLabel(key))?true:false);
       return hasLabel;
    function cnvrtPDFLnk(myDocument) {
       var graphics = myDocument.allGraphics;
       var link; var linkExt; var linkType; var linkPath; var linkPageRef; var myConfirm; var myFolder; var myFile; var myOrgPath;
       var myLinkObjects = [];
       for (var i = 0; i < graphics.length; i++) {        
          link = graphics[i].itemLink;
          linkExt = link.filePath.split('.').pop().toLowerCase(); 
          linkType = link.linkType.toLowerCase();       
          if (linkExt == 'pdf' || linkType.match('pdf') != null) {
             link.show();
             if(myConfirm= confirm(link.name+"\nDo you want to convert this link?")?myLinkObjects.push(link):alert("Link skipped!\n"+link.name));
       if (myLinkObjects.length > 0) {
          myFolder = Folder.selectDialog("Point me to a hotfolder..");
          copyLink(myLinkObjects, myFolder); // run copyLink function - copies links according to myfolder
          if(myConfirm = confirm("Do you want to relink now?")) {
             reLink(myLinkObjects); // run reLink function - relinks according to myFile dialogue
             app.menuActions.item("Fit Page in Window").invoke();
             app.menuActions.item("First Page").invoke();    
       myDocument.insertLabel("PDFCheck", "true");
       }// no links
    }// end cnvrtPDFLnk
    Best regards,
    Rasmus

    Hi Rasmus,
    Here is an example of scripted plug-in — very simple yet useful for me.
    Its goal is to check color settings in InDesign and Photoshop after a document opens. We use two profiles at work: one for the main part of our magazine and another profile for its cover and the inset for another magazine. Sometimes, although rarely, we forget to switch on the correct setting.
    That's where the plug-in comes to the aid. After a document opens it checks if the file name contains certain characters – e.g. if file name starts with "Obl_" that means that this is a cover and the script checks the color settings, if they are not correct it gives warning.
    Here is short description of how to do it:
    Create a new scripted plug-in project from APIDTemplate.indd file.
    Open APID panel
    Enter 'docLoaded' into Event Filter field and press Enter
    Here is the script that does the job (the script file is generated in the same folder as indd-file):
    if (theItem.eventCode == "docLoaded") {
       var gKasmyDoc = app.activeDocument;
       var gKasDocumentName = app.activeDocument.name;
       KasCheckProfile();
       KasinfoFromPS();
    function KasCheckProfile(){
       var myIssueNumber = parseInt(gKasDocumentName.substr(2, 3));
       if (gKasDocumentName.substr(0, 2) == "Q_" && myIssueNumber >= 730 && myIssueNumber <= 999 && gKasDocumentName.match("_Vshivka") == null){
          if (app.colorSettings.workingSpaceCMYK != "ISO Web Coated"){
             alert("Внимание! Для газеты должен использоваться провиль \"ISO Web Coated\", а установлен. — " + app.colorSettings.workingSpaceCMYK);
       if (gKasDocumentName.substr(0, 2) == "Q_" && myIssueNumber >= 730 && myIssueNumber <= 999 && gKasDocumentName.match("_Vshivka") != null){
          if (app.colorSettings.workingSpaceCMYK != "ImationMatchprn175lpi_avr.icc          "){
             alert("Внимание! Для вшивки должен использоваться провиль \"ImationMatchprn175lpi_avr.icc\", а установлен. — " + app.colorSettings.workingSpaceCMYK);
       else if (gKasDocumentName.substr(0, 4) == "Obl_"){
          if (app.colorSettings.workingSpaceCMYK != "ImationMatchprn175lpi_avr.icc          "){
    //         alert("Внимание! Для обложки должен использоваться провиль \"ImationMatchprn175lpi_avr.icc\", а установлен. — " + app.colorSettings.workingSpaceCMYK);
             if (confirm("Внимание! Для обложки должен использоваться провиль \"ImationMatchprn175lpi_avr.icc\", а установлен. — " + app.colorSettings.workingSpaceCMYK)) {
                app.colorSettings.cmsSettings = "Listovaya Mashina";
    function KasinfoFromPS() {
       var bt = new BridgeTalk;
       bt.target = "photoshop";
       bt.body = "app.colorSettings;"
       bt.onResult = function(resObj) {
          var myResult = resObj.body;
          KascheckPsColorSettings(myResult);
       bt.send();
    function KascheckPsColorSettings(myColorSettings){
       var myIssueNumber = parseInt(gKasDocumentName.substr(2, 3));
       if (gKasDocumentName.substr(0, 2) == "Q_" && myIssueNumber >= 730 && myIssueNumber <= 999 && gKasDocumentName.match("_Vshivka") == null){
          if (myColorSettings != "ISO Web Coated"){
             alert("Внимание в Photoshop! Для газеты должен использоваться провиль \"ISO Web Coated\", а установлен. — \"" + myColorSettings + "\"");
       if (gKasDocumentName.substr(0, 2) == "Q_" && myIssueNumber >= 730 && myIssueNumber <= 999 && gKasDocumentName.match("_Vshivka") != null){
          if (myColorSettings != "Listovaya Mashina"){
             alert("Внимание в Photoshop! Для вшивки должен использоваться провиль \"ImationMatchprn175lpi_avr.icc\", а установлен. — \"" + myColorSettings + "\"");
       else if (gKasDocumentName.substr(0, 4) == "Obl_"){
          if (myColorSettings != "Listovaya Mashina"){
             alert("Внимание в Photoshop! Для обложки должен использоваться провиль \"ImationMatchprn175lpi_avr.icc\", а установлен. — \"" + myColorSettings + "\"");
    You can put your own stuff into the script:
    if (theItem.eventCode == "docLoaded") {
    // do your stuff here
    And finally generate the plug-in.
    Kasyan

  • CS2 Javascript crashing InDesign works as 2 parts and in CS3.

    I have a script which works fine in CS3 but when I set it up in CS2 I found it was crashing InDesign. I've tried to cut it down to the minimum and set the 2 parts as functions.
    The first function makeMyslug create a new layer called slug and then some text frames on all master pages, with details about the document. The second function printMyslug prints all pages to postscript and adds a page number to the postscript file.
    If I have a document open and run each of the functions separately all is well. If I try and run both function in one go InDesign crashes. The script seems to crash InDesign once the printing process begins.
    NOTE for this example to work you will need to have a document open and make sure there are no blank pages. I'll post in as a reply so that it can be copied if anyone is able to help me out.
    Any suggestions would be greatly appreciated.

    //Here is the script.
    var mySluglay, myBlueBlk, mySlugChr, mySlugPar, myPageNo, myTitle
    myPageNo = 1;
    myTitle = "Test";
    myDocument = app.activeDocument;
    function makeMyslug(){
    //Create a layer for the slug items.
    mySluglay = myDocument.layers.item("Slug");
    if (mySluglay == null){
    mySluglay = myDocument.layers.add({name:"Slug"});
    //Create a blue background color.
    myBlueBlk = myDocument.colors.item("BlueBack");
    if (myBlueBlk == null){
    myDocument.colors.add({name:"BlueBack", model:ColorModel.process, colorSpace:ColorSpace.cmyk, colorValue:[100, 60, 0, 0]});
    //Create a cahr style.
    mySlugChr = myDocument.characterStyles.item("SlugChar");
    if (mySlugChr == null){
    myDocument.characterStyles.add({name:"SlugChar", appliedFont:"Arial"});
    //Create a para style.
    mySlugPar = myDocument.paragraphStyles.item("SlugPar");
    if (mySlugPar == null){
    myDocument.paragraphStyles.add({name:"SlugPar"});
    // Set units to mm.
    app.activeDocument.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.MILLIMETERS
    app.activeDocument.viewPreferences.verticalMeasurementUnits = MeasurementUnits.MILLIMETERS;
    with(myDocument.documentPreferences){
    //Slug
    slugBottomOffset = "20";
    slugTopOffset = "20";
    slugInsideOrLeftOffset = "0";
    slugRightOrOutsideOffset = "0";
    //Set the documents ruler origin to page origin. This is very important
    //--if you dont do this, getting objects to the correct position on the
    //page is much more difficult.
    myDocument.viewPreferences.rulerOrigin = RulerOrigin.pageOrigin;
    //Create the slug details on all master pages.
    with(myDocument.masterSpreads.item(0)){
    myDocument.pages[0].appliedSection.continueNumbering = false;
    myDocument.pages[0].appliedSection.pageNumberStart = parseInt(myPageNo);
    var myDetails = "Title: "+myTitle;
    var myPageWidth = myDocument.documentPreferences.pageWidth;
    var myPageHeight = myDocument.documentPreferences.pageHeight;
    mp = app.activeDocument.masterSpreads.everyItem().pages.everyItem().getElements();
    for (i = 0; i < mp.length; i++){
    var myTitleBox = mp[i].textFrames.add(myDocument.layers.item("Slug"), undefined, undefined, {geometricBounds:[myPageHeight+6,10,myPageHeight+14, myPageWidth-10], contents:myDetails});
    myTitleBox.label = "Title";
    myTitleBox.textFramePreferences.verticalJustification = VerticalJustification.bottomAlign;
    myTitleBox.parentStory.paragraphs[0].appliedCharacterStyle = "SlugChar";
    myTitleBox.parentStory.paragraphs[0].appliedParagraphStyle = "SlugPar";
    myTitleBox.parentStory.fillColor = myDocument.swatches.item("Paper");
    myTitleBox.parentStory.pointSize = 10;
    myTitleBox.bringToFront();
    myTitleBox.textFramePreferences.ignoreWrap = true;
    myTitleBox.textFramePreferences.textColumnCount = 1;
    var mycount = app.activeDocument.masterSpreads.item(0).pages.item(0).textFrames.item("Title");
    var myBlueBlock = mp[i].textFrames.add(myDocument.layers.item("Slug"), undefined, undefined, {geometricBounds:[myPageHeight+6, 8,myPageHeight+20, myPageWidth-8]});
    myBlueBlock.label = "BlueBlock";
    myBlueBlock.fillColor = "BlueBack";
    myBlueBlock.textFramePreferences.verticalJustification = VerticalJustification.bottomAlign;
    myBlueBlock.sendToBack();
    var myWhiteBlock = mp[i].textFrames.add(myDocument.layers.item("Slug"), undefined, undefined, {geometricBounds:[myPageHeight+14.5, 9,myPageHeight+19, myPageWidth-9]});
    myWhiteBlock.label = "WhiteBlock";
    myWhiteBlock.fillColor = myDocument.swatches.item("Paper");
    var myPageNoBox = mp[i].textFrames.add(myDocument.layers.item("Slug"), undefined, undefined, {geometricBounds:[myPageHeight-5, 10, myPageHeight+18, myPageWidth-10]});
    myPageNoBox.label = "PageNo";
    myPageNoBox.insertionPoints.item(0).contents = SpecialCharacters.autoPageNumber;
    myPageNoBox.insertionPoints.item(0).contents = SpecialCharacters.emSpace;
    myPageNoBox.insertionPoints.item(0).contents = "Page No";
    myPageNoBox.parentStory.paragraphs[0].appliedCharacterStyle = "SlugChar";
    myPageNoBox.parentStory.paragraphs[0].appliedParagraphStyle = "SlugPar";
    myPageNoBox.textFramePreferences.verticalJustification = VerticalJustification.bottomAlign;
    myPageNoBox.textFramePreferences.ignoreWrap = true;
    myPageNoBox.textFramePreferences.textColumnCount = 1;
    //print function
    function printMyslug(){
    alert("Start print process.");
    myDocument.printPreferences.printer = Printer.POSTSCRIPT_FILE;
    myDocument.printPreferences.ppd = PPDValues.DEVICE_INDEPENDENT;
    for(var myCounter = 0; myCounter < myDocument.pages.length; myCounter++){
    myPageName = myDocument.pages.item(myCounter).name;
    myDocument.printPreferences.pageRange = myPageName;
    //The name of the exported files will be the base name + the page name + ".pdf".
    //If the page name contains a colon (as it will if the document contains sections),
    //then remove the colon.
    var myRegExp = new RegExp(":","gi");
    myPageName = myPageName.replace(myRegExp, "_");
    myFilePath = "/c/idjavascript/test_" + myPageName + ".ps";
    myFile = new File(myFilePath);
    document.printPreferences.printFile = myFile;
    try{
    myDocument.print(false);
    catch(e){
    alert("Page "+myPageName+" may be blank plesae check.");
    //call the makeMyslug function
    makeMyslug();
    //call the printMyslug function
    printMyslug();

  • CS3: Period in findWhat crashes InDesign

    This code crashes InDesign CS3:
    app.findTextPreferences.findWhat = ", .";
    app.changeTextPreferences.changeTo = ".";
    app.changeText();
    This works fine:
    app.findGrepPreferences.findWhat = ", \\.";
    app.changeGrepPreferences.changeTo = ".";
    app.changeGrep();
    Hope this helps someone.
    Walt

    Sadly, CS3 may crash on virtually any scripted search/replace. I had it crash on double quotes, tabs, and even spaces. Usually, moving the specific s&r from regular to GREP or the other way around clears it for that offending file only.
    The symptom seems connected to a specific file (as it may always fail on one and never on another), but saving as INX and re-loading never cleared it up for me. As it is quite a hassle to find the exact code it crashes on this time (with intermittant crashes on each new try), I usually shrug and do my replaces from memory. After all, it's just a few hundred of'em.

  • Crashes InDesign on saving document

    Hello All,
    I am facing a unique problem for all my plugins under CS5, which are create from Scratch or which are ported. If I try to save my document after i create a new frame on the document or move or resize the existing frame on the document it crashes InDesign.
    Initially I thought it might be my mistake and I might not be passing the proper commands. But later I tried on a sample plugin, which created a new frame with Layout helper and tried to do Save / SaveAs document using LayoutHelper. It still crashed.
    Has anyone faced this type of problem. How can I resolve this problem. Can some one please help.
    Thank you all in advance.
    Regards
    Farzana.

    Hi,
    I am trying on Released version of InDesign.
    Thanks
    Regards
    Farzana.

  • Textframe crashing InDesign...??

    I'm breaking a bunch of documents out of their textframes. I'm basically taking a bunch of objects that have been placed into one textframe and I'm placing them into individual ones. Essentiallly I get the paragraph outlines, and copy the correlative contents into it. There's been a lot of exception handling etc. that I've had to deal with, but for the most part its gone smoothly. Then I stumble into this:
    OS_PopupWindows: InDesign.exe - Application Error
    The instruction at 0x71482357 referenced memory at 0x171d9000. The memory could not be read.
    I feel like that means something is corrupted, but don't really know. The application isn't particularly informative of why it's crashing... I'm sure this means something to a machine. I suppose this is a nice crash in the sense that I get any information at all.
    Is it possible for a single textframe to be somehow "corrupted"? Otherwise any ideas on how this type of thing could happen? Anything at this point would help. Every other document processes fine without crashing InDesign. Ultimately it might be a matter of simply laying it out from scratch...
    A brief summary of some of the testing I've done to try and isolate the problem:
    1) Checked to see if any of the objects were locked and if so I unlocked them.
    2) Tried removing the paragraphs one at a time, I found that a paragraph containing a graphic would crash if I removed it.
    3) If I duplicate the textframe, its duplicate behaves "normally" in the sense I can move it around or remove it without experiencing a crash, however even with a duplicate attempts to remove the original crash the application.
    4) Checked if the textframe was anchored... it's not.

    Ok, ho capito dove è il problema. Cambia i dizionari in Proximity, e togli Hunspell. Ero quasi certo fosse un problema di dizionario.. ed in effetti è quello.
    Ne approfitto per ricordarti che esiste anche un gruppo italiano di InDesign..
    https://www.facebook.com/groups/indesignusergroupit/
    Leonardo Agosti
    AdobeGuru
    PS.. for the english people reading this conversation, the problem is in the HUNSPELL dictionary. Changing it in the preferences and choosing the old (and wise) Proximity, InDesign doesn't crash.

  • Uploading article crashes InDesign

    I am in CS6 and when I upload an article it crashed InDesign. So far out of 32 articles in this folio, this is the only one that crashes. Any ideas?

    Hello Alistair,
    I'm facing the same problem in terms of uploading an article. Is there any way of testing this? I've got a multi-state layer (about 43 states) with separate links within one state and checking them one-by-one isn't very feasible. Alternatively, is there any way of manually uploading an article (not through Folio Builder panel)?
    Any help is appreciated!
    Thanks!

  • FolioBuilder crashes InDesign CS5

    The FolioBuilder crashes InDesign everytime I hit the locate button in the "import article" window.
    Is this a known issue? How can it be fixed?
    I already tried to un/reinstall InDesign and the latest updates on DPS without success.
    Regards
    David

    This is a known issue. The workaround is to paste the pathname into the field.
    Sent from my iPad

  • GREP search crashes InDesign

    Hi,
    I have a script which imports XML and formats it. As part of the formatting, there's numerous GREP searches which remove redundant spaces, returns and so on.
    One in particular crashes InDesign and it's driving me nuts.
    It's supposed to remove redundant returns in a table:
    // GREP Search for redundant returns
    app.findGrepPreferences = app.changeGrepPreferences = null;      
    app.findGrepPreferences.appliedParagraphStyle = "ArticleMinister";
    app.findGrepPreferences.findWhat = "\r$";
    app.changeGrepPreferences.changeTo = "";
    app.activeDocument.changeGrep();
    The problem is there's an XML closing tag between the carriage return and the end of the para, i.e. data{return}</closingtag>, but it works fine when the XML is data</closingtag>{return}.
    Any assistance would be most appreciated.

    Hi Vamitul,
    Thanks very much for the reply and it makes perfect sense.
    This script creates quite a complex document and, for some reason, moving the {return} outside the XML tags makes a mess of the document. I do not know why but I suspect that some of the 'clean up' non-GREP search and replace commands in the script are ignoring the XML data - perhaps not but I cannot for the life of me work out why a simple change is making the text a real mess.
    So the 'harder fix' sounds like something worth pursuing as this is the last step in a long process. Do you have any more information about checking the xmlContents? I don't expect anyone else to do my work for me, but advanced (or even intermediate) scripting is something I struggle with.
    Cheers,
    Simon.

  • Idml open and idml Save As crash InDesign CS6 8.0.1

    I am using:
    2012 MacMini
    Mac OSX 10.8.3
    2.6 GHz Intel Core i7, 8 gb 1600 MHz DDR3
    InDesign CS6
    Version 8.0.1
    I have run software update
    Opening an idml file crashes InDesign.
    Saving a file to idml crashes InDesign.
    Assistance would be very much appreciated.
    Thank you.

    Via Font Book, I checked all fonts with pro in the name. All appear OK.
    I created a new document with nothing in it with same result. My crash report (http://pastebin.com/Rgd5AAHZ) was a little different under VM Regions.
    Do you believe a re-install would solve the issue?
    Thanks again for your help. It is appreciated.

  • SmartStream crashes InDesign CS6

    The SmartStream Designer plugin crashes InDesign every other time I use it. Here is the bug report:
    Process:          
    Adobe InDesign CS6 [382]
    Path:             
    /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
    Identifier:       
    com.adobe.InDesign
    Version:          
    8.0.0.370 (8000)
    Code Type:        
    X86 (Native)
    Parent Process:   
    ??? [1]
    Responsible:      
    Adobe InDesign CS6 [382]
    Date/Time:        
    2014-12-22 14:20:54.756 -0700
    OS Version:       
    Mac OS X 10.10.1 (14B25)
    Report Version:   
    11
    Time Awake Since Boot: 470 seconds
    Crashed Thread:   
    0  Dispatch queue: com.apple.main-thread
    Exception Type:   
    EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:  
    KERN_INVALID_ADDRESS at 0x0000000000000003
    VM Regions Near 0x3:
    -->
    __TEXT            
    0000000000001000-0000000000005000 [   16K] r-x/rwx SM=COW  /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.applescript   
    0x10589e99 CreateStyleMapFromLegacyData(STElement**) + 99
    1   com.apple.applescript   
    0x10589dce TASDialect::SetStyleMapObsolete(STElement**) + 24
    2   com.apple.applescript   
    0x105866fd ASSetSourceStylesLocal(STElement**) + 32
    3   com.apple.CoreServices.CarbonCore    0x97091983 callComponent_4 + 18
    4   com.apple.CoreServices.CarbonCore    0x9707f062 CallComponentFunction + 42
    5   com.apple.applescript   
    0x1057d1d6 AppleScriptComponent + 728
    6   com.apple.CoreServices.CarbonCore    0x96fee848 CallComponent + 190
    7   com.apple.CoreServices.CarbonCore    0x96fee89c CallComponentDispatch + 29
    8   com.apple.openscripting 
    0x90fa39fc OSASetDefaultScriptingComponent + 43
    9   com.apple.openscripting 
    0x90f9b4b3 OSADoIt(short, ComponentInstanceRecord*, FSRef const*, unsigned long, unsigned long, long, unsigned long*, AEDesc*, unsigned char*) + 2772
    10  com.apple.openscripting 
    0x90f9bacf OSALoadFile + 79
    11  com.adobe.InDesign.Support for AppleScript    0x17ad17cf 0x17ac5000 + 51151
    12  com.adobe.InDesign.Support for AppleScript    0x17ad2fd4 0x17ac5000 + 57300
    13  com.adobe.InDesign.Merger.sdk     0x1bcb085b YTDDMEUtils::RunAppleScriptGetMyDocumentsPath() + 939
    14  com.adobe.InDesign.Merger.sdk     0x1bcb0b2b YTDDMEUtils::GetMyDocumentsPath(PMString, PMString) + 43
    15  com.adobe.InDesign.Merger.sdk     0x1bcab216 YTDDMEUtils::GetSmartStreamUserDataPath(PMString, PMString) + 166
    16  com.adobe.InDesign.Merger.sdk     0x1bcae4db YTDDMEUtils::GetImpositionUserPresetsFolderPath(PMString) + 171
    17  com.adobe.InDesign.Imposition UI.sdk    0x1bfb4bb5 YTDImpUtils::getImpUserTemplatesPath(PMString&) + 133
    18  com.adobe.InDesign.Imposition UI.sdk    0x1bf7c091 YTDImpGlobal::buildTemplatesVec() + 209
    19  com.adobe.InDesign.Imposition UI.sdk    0x1bf7c97d YTDImpGlobal::initImpGlobal() + 269
    20  com.adobe.InDesign.Imposition UI.sdk    0x1bf6ac05 YTImpositionDialogController::InitializeDialogFields(IActiveContext*) + 37
    21  WidgetBinLib.dylib      
    0x00034b4d CDialogController::InitializeDialog(IActiveContext*) + 61
    22  com.adobe.InDesign.Widgets  
    0x158a560d 0x1588e000 + 95757
    23  com.adobe.InDesign.Widgets  
    0x158a4c4e 0x1588e000 + 93262
    24  com.adobe.InDesign.Imposition UI.sdk    0x1bf68313 YTDImpActionComponent::DoImpositionDialog() + 387
    25  com.adobe.InDesign.Actions  
    0x1a859bc4 GetPlugIn + 19908
    26  com.adobe.InDesign.Actions  
    0x1a85e7b2 GetPlugIn + 39346
    27  com.adobe.InDesign.AppFramework    0x11620614 0x11610000 + 67092
    28  com.apple.HIToolbox     
    0x9401d5d4 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
    29  com.apple.HIToolbox     
    0x93e67501 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2291
    30  com.apple.HIToolbox     
    0x93e664dc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 402
    31  com.apple.HIToolbox     
    0x93e79d25 SendEventToEventTarget + 88
    32  com.adobe.InDesign.AppFramework    0x1161ee21 0x11610000 + 60961
    33  com.adobe.InDesign.AppFramework    0x1163d327 GetPlugIn + 12007
    34  com.adobe.InDesign      
    0x00001ec5 main + 341
    35  com.adobe.InDesign      
    0x00001d55 start + 53
    That is just the first chunk of text that seemed relevant to the crash. If more is needed I can easily recreate the scenario and get the whole report.
    I initially tried using the latest release of Indesign CS6 (8.0.2) with the same results. I thought that going to a previous version would help. If anyone can make sense of the text above, it would be greatly appreciated.
    Thanks,
    Dan

    Hi Danariotti,
    My workmate and I are having the same problem here, with the same report you are getting with Indesign CS6.
    This started with the upgrade to Yosemite, so we trialled the latest update to Smartstream with Adobe Indesign CC 2014 but this caused the programme to shutdown as soon as you start running indesign. I am hesitant to fully upgrade our Smartstream, as it is expensive for an unstable plug-in. The problem we are having is Adobe blame HP Smartstream and they blame Apple and back around again, we don't seem to get much support. Can you tell me if you get an answer to this please.
    Cheers Tony

  • Bug: Configurator crashing InDesign

    Hello,
    Unfortunately I cannot use Configurator because it crashes InDesign whenever I run certain scripts that would otherwiser run fine when launched from the old script panel.
    I get this messsage:
    "An attached script generated the following error:
    Object is invalid
    Do you want to disable this event handler?
    (No) (Yes)"
    Afterwards, InDesign crashes.
    Can I report this somewhere?

    Sorry for this.
    Could you please send the panel that containing the script to [email protected] ?
    And tell us which objects in the panel containing the script that make InDesign crash.
    We will investigate the problem.
    And here you mentioned:
    that would otherwiser run fine when launched from the old script panel.
    what doesn the "old script panel" mean?
    Thanks
    Xiaoyan

  • Overlay creator crashing InDesign

    Hello,
    I've been working with DPS in InDesign CS5.5 with no problems. About five days ago I updated to the current Folio Producer Tools and Folio Panel Tools for CS5.5 and have had no problems. Today out of the blue, every time I try to open the Overlay Creator panel it crashes InDesign.
    I am on a Mac and I have rebooted, trashed InDesign preferences, uninstalled the tools and reinstalled, and even went back to an earlier version of the Folio Producer and Folio Panel. I tried opening the Overlay Creator in a new blank document and it still crashes the entire program.
    I'm tearing my hair out and would appreciate any new suggestions of what I might try.
    Thank you,
    lkovalic

    Hi Dave,
    I'm not sure how the server problems would affect opening the Overlay Creator -- I'm not trying to upload anything or trying to do a preview -- the simple act of trying to open the Overlay Creator extension is what is crashing InDesign. Doesn't that extension reside on my computer?
    Thank you,
    lkovalic

  • Crashing Indesign writing 5 letters

    Hi,
    I'm trying to write this 5 letters combination:
    ÌÍ5GÓ
    Always causes the crash of indesign.
    Just write this in a new document with the text instrument.
    I have test it with indesign CC 2014 and indesign CS6 (italian versions), with mac and windows...always crash.
    There is an hack to write this without crashing indesign?
    This text is present in a big document that I need to merge, so I can't create outline of it.

    Ok, ho capito dove è il problema. Cambia i dizionari in Proximity, e togli Hunspell. Ero quasi certo fosse un problema di dizionario.. ed in effetti è quello.
    Ne approfitto per ricordarti che esiste anche un gruppo italiano di InDesign..
    https://www.facebook.com/groups/indesignusergroupit/
    Leonardo Agosti
    AdobeGuru
    PS.. for the english people reading this conversation, the problem is in the HUNSPELL dictionary. Changing it in the preferences and choosing the old (and wise) Proximity, InDesign doesn't crash.

  • Liquid Layout crashing InDesign CS6

    I was using liquid layout - pinning a graphic-  and when I tried to resize, the whole program crashed.   Every time I try to resize - on any page in the doc, it crashes the program.  
    InDesign CS6.   Liquid page rule:  controlled by master [which is object based].   Objects move with page.
    I've tried everything, for hours now.   I have no idea why it was fine, then all the sudden it's broken.
    Very frustrated.  

    How would you go about exporting your alternate layout alone for print?

Maybe you are looking for

  • Adding 2 more monitors to HP p7 1435 pc

    I want to run a third monitor on my HP Pavillion p7 1435 desktop computer. When I hook the third one up using a USB Video adapter...it shows that its there but unable to get it to function at all

  • MacBook Pro First 2011 Port Thunderbolt

    Hi, I have a mac book Pro 15" First 2011 with a Thunderbolt Port. I would like to add another monitor for dual display. But I don't know, or I don't find realy which adapter I could use for this second display- • Only VGA or DVI. • Or HDMI it's possi

  • HPG62-229WM Pavilion Notebook pc Charging New Battery

    How long do I charge my new replacement 12cell primary battery ? Do I have to reset the startup error #106 message ? "replace primary battery error106" go to www.hp.com/go/tech/startup  This question was solved. View Solution.

  • Cleaning up multi- CSS files

    Hi Folks! I have build my first RH project (Webhelp and AIR) by importing topics from an existing system. Initially, Imported all my topics and THEN organized them into folders and build my TOC from the folders. We need to cleanup the existing master

  • Download Assistant Unsupported 16 -bit Application error (Windows 7 64 bit)

    I cannot download CS6 Master Collection. Air Installer gives me an error even when I run as administrator. Download assistant won't install because Windows 7 64 bit recognizes it as a 16 bit app. I believe that if I were given a link to a direct down