CC 2018 13.0.0.125 | Bug with event "afterExport"

[Laubender]

Hi fellow scripters,

somthing's wrong with event listening for event "afterExport" with CC 2018 13.0.0.125.

I found that property fullName of the event will give no reasonable value. It's just an empty string.

In versions before, CC 2017.1 and below, there is no problem to track an exported file.
With CC 2018 13.0.0.125—both on Windows and OSX—there seems no way.

( At least I did not find a workaround.)

Here a discussion in German at hilfdirselbst.ch that came up yesterday:

Verspeichert | Script "Explorer-Fenster nach Export öffnen" und ID 13.0

By Ingo Herber on 20. Okt 2017

http://www.hilfdirselbst.ch/gforum/gforum.cgi?post=560045#560045

Regards,
Uwe

[Kasyan Servetsky]

Thanks for reporting, Uwe!

I suggest to create a sticky thread for each new version of InDesign: something like -- "New scripting bugs in CC 2018".

— Kas

[Kasyan Servetsky]

Uwe,

Are you sure that this is a bug?

In your example, myEventWithAfterExport is event object -- the only argument passed to the myExportPathShow handler.

#targetengine "test" 
main(); 
function main() { 
    var myApplicationEventListener = app.eventListeners.add("afterExport", myExportPathShow, false); 
} 
function myExportPathShow(myEventWithAfterExport) { 
    // RESULTS FOR: 
    for (x in myEventWithAfterExport) { 
        $.writeln(x + "    :    " + myEventWithAfterExport.toString()); 
    }
} 

In the scripting reference, I don't see the fullName property for the Event object, so why do you expect that it should officially work?

— Kas

[Laubender]

Hi Kas,

I think, you have to look after ImportExportEvent :

Adobe InDesign CS6 (8.0) Object Model JS: ImportExportEvent

EDIT:

Or better look here for CC 2018 version 13 DOM:

https://www.indesignjs.de/extendscriptAPI/indesign-latest/#ImportExportEvent.html

Best,
Uwe

[Kasyan Servetsky]

Thanks for clarification, Uwe!

Now I understood it.

— Kas