Open tomka opened 7 years ago
Is there a use case for a single tag table needing to do both simultaneously? We could either split the tag table into a node tag table and a connector tag table, or we could have a switch at the top to show either node tags or connector tags (or feasibly both), or we could have an extra column showing whether the tag applies to a node or a connector (which could then be filtered on).
It doesn't need to be a single table, no. I just thought a single table might give a better overview on how tags are used. Two tables on the same page might not work so well though if you have many tags. However, having two tabs with one table each (skeletons and connectors) could work as well (similar to the log/history widget). I just feel having one general tag table widget widget is better than two specialized ones.
Tracers have expressed interest to also show tagged connectors in the Tag Table. Having an extra "Connectors" column could show the number of tagged connectors, clicking on this number could open a Connector Selection Widget, showing all connected nodes.
Optionally, a "Select connectors" column (or as part of the regular "Connectors" column) could allow selecting all skeletons linked to the tagged connector nodes. This, however, could also be solved by making the Connector Selection Table act as Skeleton Source, so that its listed skeletons can be pulled into other widgets.