Goal: Create event that occurs every time an a user selects an item in the navigation on a multipage app.
Steps: Looked at the navigation component.
Details: I know that as recently as 2 days ago, the event option was present as I created a similar event for a different app. Currently, the even section is missing and new navigation components are also missing them, but the older ones still have the events listed in their state but not in the inspection menu.
That works for my immediate needs but I'm certain I didn't do that 2 days ago when I was using the navigation component. Why would I need to have a mapped navigation component to utilize event handling?
I would generally prefer just having the general event handler menu as the options in my multi-page app are some of the pages in the app so I am using the page option and having re-create selecting a page for each one of the pages AND add this event to each of the pages sounds like a needlessly tedious addition to what was a much simpler process 2 days ago.
I can definitely make a feature request to have an event handler for the page type in Manual mode!
I can also check internally as to why things may have changed, potentially there was some other bug that was created from the previous set up but I should get more details from the UI team on the ticket's thread
From looking at the current setup, I would imagine that they wanted to keep things simple where the 'page' option corresponds to only one possible event, changing to a page. With the pages selectable from the defined list of pages created.
Which is the best and most well optimized for a click event of wanting to change pages. With app for changing apps and custom for events that are NOT changing page or changing apps.
Hopefully this isn't a blocker for you, @Daniel_Fleuranvil! While the current interface might become clunky in certain use cases, I generally recommend Mapped mode anyway as a more flexible, robust implementation in most instances.
Am I understanding correctly that there isn't a 1:1 mapping between pages and menu items in your app? If that's the case, you do still have options, but I'll check on the status of the ticket that that Jack mentioned above.
