The top blue box is a docked view (this one does not work)
I copied and pasted the menu into the main view for the page and it works correctly.
Odd. I’ll have to look into this a bit deeper so it’ll be awhile before I get back to you.
It looks to be any Horizontal Menu in a “North” Docked View. I’ll open a ticket to get it fixed.
Well…That’s a very specific bug.
Okay. I’ll go back to a static menu for the time being and bind the enabled property.
just a note. It appears to be the case for all horizontalmenus, not just the bound items. I created a new menu to replace the one I was working with and hard coded all the targets and labels. And I still get the component error problem on Chrome.
Can I bump this reqeust to add a visible prop? I've needed this for a while now and the solution using a binding to dynamically create the props.items doesn't work well when you have bindings on your sub-items props
2 Likes
Hi,
Is there a way to pass parameters to sub menu pages?
Ex. setting the target of a sub menu item to a single parameterized page.
You would have to configure the target with query params.
Supposing you had a configured page ULR along the lines of /bays/:bayNumber, you would configure the target of that nav item as /bays/:6. There's nothing stopping you from binding that value based on some other input on the page. Supposing you had a numeric input which dealt with a specific "bay", you could bind the target prop here against the numeric input:
"/bays/:" + toString({this.view.getChild("SomeContainer").getChild("MyNumericInput").props.value})