Closed SirMortimer closed 4 years ago
Okay the word "action groups" in the title was confusing but I know what you're talking about now. A few things:
Ah, sorry for the confusing title. As to your questions:
Not sure if that really answers the 2nd question. Of course it would be optional and fully configurable. But what else do you plan to put in those groups and how?
These are the current use cases. We use B9PS to switch the configuration for experiment part modules and life support processes.
Switchable experiments on a probe core, there already is a "Science" section that has information about hard drives, and the activated science experiments themselves (when selected, see crew report in next screenshot)
The removed "Select" buttons would be most apparent here, where they currently fill about 1/3rd of the PAW. It's a fairly complex part.
The reason for keeping the button for the moment is that the subtype switcher is annoying to use, and there's no way to see the names of all the subtypes at once.
The best solution is probably to merge the button into the existing UI element. I'm already screwing with the subtype switcher thing to get it to work, just a question of making more modifications.
So you'll mostly be using it with custom modules that either already have or can have group support?
Another question, do you care about startCollapsed
?
So you'll mostly be using it with custom modules that either already have or can have group support?
Yes.
Another question, do you care about startCollapsed?
Not particularly. I might use it if it is there, but the goal is having a PAW that is small enough to not need default collapsed groups.
Done #190
It would be very nice (and help clean up the PAW) if we were able to put the switch buttons into PAW action groups (the list switch and the button that opens the switch dialog). The PAW group UI name should be configurable.