Hi Chris, I have two feature requests that I'd like to put forward as being very useful for creating reusable, modular "code".
1) A new action under Menu to hide or show all elements of a chosen menu. I use a custom diary system and inventory item closeups that rely on hiding and showing specific elements within a menu. As it stands now, I have to trawl through every element in these menus to hide them all, then show the specified one.
2) This one is a little more involved. I'd like the feature that, when using an asset-based action list as the source of an interaction, and that action list has parameters, those parameters can be set specifically for that interaction, directly in the inspector. I use a lot of reusable, parameter-based action lists. Currently if I want to affect those parameters, I have to create an in-scene action list that only calls an asset-based action list and sends the necessary parameters. It seems like a "waste" of an action list (really, just an extra click), and I think it'd be far more use-friendly and efficient to be able to set those parameters in the inspector.
Thanks!
Comments
It's also possible to write a custom Action that does this - a Menu's elements are stored in its elements List.
2) Very involved, in fact. As the code is distinct to the ActionList: Run Action, I'd hesitant to make changes in case it causes breakages. Is it really that much of a hassle as it is?