[javascript] non-modal dialogs

[Mathew]

I appreciate that this is another long-shot feature request and that given the developer workload it may be a dream. Nonetheless, I think this would be an incredibly valuable feature and want to put it out there for consideration:

Currently app.execDialog() blocks all user input and actions until the dialog is closed. It is possible to make changes to the document and have them show during the dialog, but a user cannot, for example, change the page, draw annotations or select annotations while the dialog is active. There is a non-modal dialog (app.thermometer) but it is a very specific and limited function. If there were a way to have a non-modal app.asyncDialog() it opens a range of possibilities for scripts (some of which could reduce pressure on other aspects of developer time ).

For example:

• Bookmarks: It would be possible to make a dialog listing bookmarks along with other properties of the bookmarks (such as page number ) with actions for those bookmarks (ie goto page, change, etc). This could be open alongside another pane, so the user could continue using the document without closing the dialog.
• Annotations list: A table view of annotations similar to Bluebeam. It's currently possible as a non-modal dialog, but it cannot stay open while the user interacts with the document.
  image.png
• Custom tools (such as curve drawing, or synchronize views) could have a dialog open while the element is drawn so that user could change properties or cancel, etc while the tool is active. My curve tool uses the thermometer, but as you can see from that tool, it's a clunky workaround. The synchronize views tool relies on the user picking the same menu item again to make changes or cancel it.

Thanks for the consideration!

[Daniel - PDF-XChange]

Hello, Mathew

Yeah that might be a tall order, but I have passed it on. I will keep you posted if I hear good news.

Kind regards,

[Mathew]

I woke up thinking about this one: app.execDialog() is already event-based (ie the methods in the dialog object are called based on user interaction with the dialog). I guess in essence this FR is wanting a way to use the same dialog object, and instead of it returning a result string, it returns a promise (ie an async function).

OK, I'll stop obsessing about it now

[Daniel - PDF-XChange]

Hello, Mathew

Just under half of that flew right over my head, but I suppose I will stop worrying about it as well.
In any case, I will leave the request open ended for the dev team to come take a look if they feel like it. For now, I hope you have a nice day!

Kind regards,