Menu Actions: eventType question. JS

Question

Hi,
(1) How would I add an eventListener for a given menu action that kicks
in when the menu is dismissed?
Eg
myMenuAction.addListener("onInvoke", function(){alert("Hello");});
adds a listener when it is invoked. But what would be the eventType for
"dismiss"?
(2) Where are the list of eventTypes documented?
Thanks,
Ariel

Answer 1

[Jongware] wrote:
OT: Can anyone explain in simple terms what the "bubbleability" of events is all about?
Here's a 30 second crash course in events:
The basic concept to grock is the "box model".
Basically an app can be looked at as nested boxes -- boxes within boxes. In InDesign terms, the outermost box is the application, inside that is a document, inside that are layout windows. Inside that are all the objects.
UI Events generally have two phases. There's the capture phase and the bubbling phase.
When you click on something (for example), the click is "captured" from the outermost box inward. So it's first captured by the application, then the document, then the layout window, etc.
Once the click (or what-have-you) hit the target (i.e. a button or InDesign object), the event then bubbles back out. It starts at the innermost object and bubbles out to the outermost box (i.e. the application).
Theoretically, events can be attached to any box from the innermost one and outwards. If the event is recieved in the capture phase, the outer boxes will catch it first. If it's recieved in the bubbling phase, the inner boxes come first.
Let's say we have a "move" event on page items (which does not exist). We could theoretically add event listeners to the object itself (not possible because that level was never implemented), the page (also not possible), the window which holds the object, the document, or the application. If we attach listener to all the boxes, the innermost ones will be executed first. If bubbling can be canceled, the inner boxes can prevent the event from bubbling out to the outer boxes.
AFTER_CLOSE refers to windows or documents. The event can be attached to the app because it bubbles out to the app. Not that you can listen for an AFTER_CLOSE event for the app itself...