Since Mac OS Lion, our Flex plugins make Indesign crashed after any browse folder.
I can post the crash details if you want.
I upload an exemple of extension in your ftp ( DFhdgjfhgKJ.zxp )
the flex code is just:
var vFile:File = new File();
vFile.browseForDirectory("select a directory");
I think you already know this, but I had the same problem. Someone at Adobe (maybe even you?) reproduced it for me. I ended up just writing my own file browser--the Silicon Publishing FileBrowser(TM)--to get around it.:-)
I'm just posting here so that Pierre-RAFFA knows that others have run into the same problem.
I guess I have the opposite approach: If ExtendScript has built-in functionality, why rewrite it in Actionscript?
I actually like the standard ExtendScript File dialogs better than the AIR ones...
First of all, is there any word on this issue? browseForDirectory in my extension seems to be crashing Illustrator on Lion and not on Snow Leopard.
Second of all, any tips on writing my own file browser? Or alternatively, any tips on how to get the ExtendScript functionality in my cs extension?
ExtendScript has File.openDialog(), File.openDlg(), File.saveDialog() and File.saveDlg() Folder.selectDialog() and Folder.saveDlg()
the "Dlg" ones are instance methods which open from the selected location, and the "Dialog" ones use the default location.
the same problem you can see with running the Dommy Dumper Extension Builder project on Mac OS X Lion 10.7.3. Just click on the first button on the upper right and after the click InDesign (CS5 or CS 5.5) will crash.
I absolutely quote Harbs on this because, this way, it will look more "InDesign-friendly". The only thing I wasn't able to reproduce by calling a ExtendScript from within actionscript is a progress bar made with ScriptUI. It seems to me that a progress bar needs a targetengine to persist and I could't find a way to have this behaviour. Sorry for the off-topic but is there anyone who knows a possible solution? Why would I prefer this method? A scriptUI progress seems to me more "integrated" in InDesign than a actionscript one...
Any extendscript code run from an extension is run in the service manager persistent engine by default, so that should not be an issue.
What's the code you are using to run your progress bar?
I was preparing a sample project to show you my problem and... boom! It worked as expected :-S
I think I should have to re-insert the progress bar in my main project and see where the problem could really be...
May be its too late but I'm also getting same problem on my lion machine with Indesign 5.5 but same extension working fine on windows indesign5.5.
is there any solution for this problem other than scripting??