I truly wonder what is so special about Export-as-JPEG-Options-Window that it can instantly drop memory to minimum, even clearing cached page previews out of memory - 10MB is really low mem usage for and app and as I scroll the document and InDesign displays other pages, memory starts to build up again. When I show export options dialog, memory drops to 10MB and "forgets everything". It's really fun to observe how bizarre that is, but when I try to build a real flash panel and see that ONLY THING THAT CAN FREE INDESIGN MEMORY IS EXPORT DIALOG, it kind of makes me grab&pull my hair off.
1 person found this helpful
Please file a detailed bug report on this!
The ARE memory build up issues in InDesign, and the more user cases the engineers have, the better!
If you are working with the CS SDK (Extension Builder), one thing you can try is to create a pdf, and make the thumbnails from that using AIR features...
Thanks Harbs, I just filed a report - I hope it'll help.
The idea with PDF and AIR is interesting, I'll look into it. Albeit it won't solve my problem with memory buildup because the PDF export itself consumes the same ammount of memory as JPEG export.
I wish there was a known way of releasing memory. InDesign has it and that's a fact: Export options dialog calls it. Adobe employees, isn't there some undocumented function that is called when a export options dialog pops up? Care to share it with us? It would really spare much hair on my head. And I like my hair
Harbs, what did you mean by "make the thumbnails from PDF using AIR features"?
HTMLLoader and BitmapData.draw()?
1 person found this helpful
Yes. That should probably do it. Make the container the resolution you need you thumbnails to be, and you should be good to go...
(I haven't actually tried any of this, but it should work...)
it didn't work. Standard HTML pages did well, but when I tried to draw() HTMLLoader with PDF content loaded, it captured only gray area (acrobat reader background, I guess).
I'll try to post new thread about this with better title , hopefully some adobe guys will be able to give us some insight.
Once again, thanks Harbs for ideas and helping people!
A search for "open pdf in air" gets quite a few useful results.
Does this help? (I believe that you do need to have Acrobat 8 or higher installed.)
Thanks, but opening PDF was not the problem. I loaded and viewed PDF inside AIR application with few lines of code. The problem was that when I tried to capture pixels of the HTMLLoader object, it returned single-plain-colorer rectangle. When I loaded a HTML page instead of PDF, if worked fine - draw() returned expected result.
The only explanation I can figure out is that it's something similar to trying to take a snapshot from a movie player. You get the desktop pixels and all, but the area where the movie was supposed to be is just plain black rectangle. I think the flashplayer just defines area where the PDF should appear and then "all the magic" happens outside the plashplayer, in separate "layer".
So I think this way is busted - flash and AIR does not know what it displays (PDF), it only tells the operating system to show Acrobat reader in specific rect.
Interesting. Maybe you can get some better suggestions for extracting the images on one of the Flex/ActionScript forums.
Another suggestion might be to open the pdf in Photoshop and create the thumbnails there...
I just reopened the old project (abandoned because of the memory build-ups) and was really surprised that it was suddenly working alright. I did a bit googling and found out that there's been an InDesign update in the August 2010 that included graphics export fixes.
So if someone googled this thread, It's no longer relevant if you have ID update 2010/10.
Way to go, Adobe!