2016-05-27, 17:31
(2016-05-27, 08:14)BobCratchett Wrote:The clonewidgets build option worked, that was too easy! I had no idea about that option. Always learning something new, thanks for pointing me in the right direction.(2016-05-27, 03:39)braz Wrote: One more question for you Bob, though I'm guessing this isn't doable. Is it possible, when using the "allmenus" include, to display the main menu item's widget even when one of its submenu items has the focus?
If you're not using templates, it shouldn't be more difficult than adding the correct cloning option to your build line.
If you are using templates it will be more complex, as I doubt the <skinshortcuts>visibility</skinshortcuts> element will be replaced with a vis condition that takes the allmenus tree into account (though there's an outside possibility it might, so do try it!) You'd therefore most likely have to roll your own <visible /> element. As a very rough guide - this is unlikely to work without some playing around - you could pull out the submenuVisibility property:-
Code:<property name="submenuVisibility" tag="property" attribute="name|submenuVisibility" />
and use something like
Code:<visible>StringCompare(Container(9000).ListItem.Property(submenuVisibility),$SKINSHORTCUTS[submenuVisibility])</visible>
(No need for the cloning option in this case)