I am thinking about this one as well. I think that’s what he’s after. Seems combining them would be functional enough.
I would also think some kind of user friendly macro data would be useful too. To be able to have the ability to command the functionality of : visability + filter in one command.
Then with a command that filters layers, and turns visability on for them. Which would leave out turning visability off of all deselected by the filter. Or maybe a option in the command to invert/ change visability of layers not selected by the filter.
Options
SelectandInvert-which would turn filter result matches on, all others off
AddTo, which would add visability to currently visable, allowing to turn off visability selectively of currently visable
Of course any other variation that isn’t a waste.
Then of course the goal would be to be able to take this command, normal person macro friendly and be able to make a toolbar with buttons for macros, with specific filter and state, and toggle between sets.
Now as for the layer state manager, programming it as a command in the same fashion, to be user friendly as a command would be the second part of his request. Having a command to run a layer state change that has been saved.
such as
RunLayerState
Thus having the features separate keeps things more simple, and if you only wanna toggle visability, its quick. If you only wanna change layer states by typing a half word, and clicking on one, its pretty quick. If you want both, combine them in 1 macro, or have two buttons next to each other. But 1 column in a toolbar for visability buttons, and 1 column for layer state could be easier for having 8 combos easier than combining the two.
Then one could easily edit macro format for search criteria and filter options to make each as they arise. Maybe just make the macro sheet on 1 side of a document, and have instructions on other half, or some other workflow. Since it would only be 1 command, changing a few yes’s to no’s and adding a criteria would be quite simple in comparison to multiple command harder macros.
I would think that someone who uses rhino enough, with the complex stuff, wouldn’t mind sticking to a format for how they name their layers, and layer types, and that the toggle buttons would in the end be more simple and faster to make than using the combined layer state manager.
Anywho, I know nothing about rhino, so feel free to criticize me. I had fun thinking about it a little bit.