I like grouping slaves by group. But then I can’t sort or collapse or filter out the “none” group. Filtering out the “none” group doesn’t remove the “none” part of the list.
So I’ve turned off what would be a great feature otherwise.
B.
I see what you mean. While you can filter out slaves that are only in the “none” group, every slave that is still left visible is also shown under the “none” group because they are of course part if it. A toggle flag next to the “Group Slaves By” dropdown should be able to take care of this. I’ve logged this as a feature request.
Cheers,
- Ryan
The type of view filtering in “group by group” should be on the group, not the items in the groups. Collapsing the tree and/or allow sorting of the groups in the view might be enough too.
B.
Can you elaborate on this a bit more? Maybe a mock up would help. Because slaves can be in multiple groups, it seemed to make sense to have a “header” for each group and show which slaves are in that particular group.
I agree that the group headers should be sorted alphabetically, and that’s an oversight on our part. I’ve logged this as a bug.
Cheers,
Ryan
We’ve decided to just remove the “none” grouping when grouping slaves by Pool or Group, since showing this kind of defeats the purpose of the feature.
Cheers,
- Ryan
Sounds good.
I just meant,
Collapse: if the slave data view was a tree, then you could click on a (+) to hide that group.
Filter: instead of showing a slave if any slave.group.visible == true for every group. just don’t show that group. it’s similar to the collapse. The slave will still show up in its other groups lists.