Hi Dimitar,
Thanks! This small feature request will then allow to do oh so much more
Here's what I'm really up to (and will be able to do once I can specify root-per-document bookmark titles):
Say I'm combining documents:
pdf1 (1 page) + pdf2 (2 pages) + pdf3 (3 pages)
The resulting combined.pdf will have 6 pages.
I need to inject an additional "title" page (and maybe some more) inside the combined.pdf, so it looks like (9 total pages):
pdf1_title_page
pdf1_page1
pdf2_title_page
pdf2_page1
pdf2_page2
pdf3_title_page
pdf3_page1
pdf3_page2
pdf3_page3
While it might seem this is also possible now - so just add more CoreDocs (doc title page) to the Op's Input Param - that's really not the way to go.
As, for example, if pdf2 has such security settings that it will deny page extraction, the "Cannot add file / operation not permitted for document" dialog will popup and the user can decide to Ignore (or Abort). If "ignore" is selected, pdf2 will not be a part of combined.pdf - and therefore "pdf2_title_page" must also be ignored.
For the moment, there's no way to catch "Ignore" for a particular document as there's no callback (I know of ...?) while the Op is running to get notified if some documents cannot be combined. Relying on filename bookmark titles (how it is now) is also not possible as one might combine documents having the same file name (different folder).
Now, having custom bookmark titles, here's what I will be able to do:
1. Have a dictionary with unique (per document) Guid values set for each document's root bookmark title.
2. Once the operation is done:
2.1. Scan root bookmark titles for a Guid, read resulting bookmark's GoTo action to get the page it points to
2.2. Insert additional page(s) before that page
2.3. Change the bookmark's title to the real needed value
And then only the imagination is the limit
-žarko