If I do:
var bmk = this.bookmarks.children;
bmk.open = true;
nothing happens, the first bookmark does not open, although the
documentation says it should
Also, as I mentioned. If I open an AssemblerServices build PDF with
AcrobatPro 9, add a bookmark (any, to anywhere) and save it, next time
I open that PDF, the bookmarks auto-expand.
So I presume Acrobat does change some setting somewhere that does the
Thus there is probably a setting somewhere in a PDF that forces
bookmarks to auto-expand. Maybe that is not exposed to the Assembler :-
I did some further research on the behavioral differences between an Assembler build PDF bookmarks and ones added thru AcrobatPro and noticed something very strange.
When I open the Assembler built PDF with Reader (9), the Bookmarks Action->"Expand Top levels bookmarks" does nothing, nothing gets expanded. It works when you manually expand a node, but not when you ask Reader to expand them all.
If I take the exact same PDF with AcrobatPro (9) and add a new bookmark deep down into one of the bookmarks tree branch I get this:
- the document opens with the entire tree containing that bookmark already open
- the expand/collapse top level actions work only on that part of the tree and even weirder, the tree opens to the new bookmark level, no matter how deep it is
- it is as if none of the Assembler built bookmarks bear any 'level' info, and are thus ignored by the expand/collapse commands.
Does that indicate something I'm not doing right?