K-Truss and Hierarchical menu items buttons should enable/disable properly
See original GitHub issueDescription
These menu items are not disabled when there is no graph opened and no valid graph opened. When no graph is opened, the buttons inside are disabled except Cluster. But when loaded on an empty graph, other buttons except Cluster
are initially locked, but if you click on the Cluster
button now, it enables the Interactive-Enabled
button, and clicking that enables other buttons.
The enabled Cluster button or any other button in both windows don’t do anything or throw any errors, so this doesn’t require immediate fixing.
If the empty graph is added after the K-Truss and Hierarchical windows, the buttons are not enabled even after a valid graph is added, until you click on the only enabled Cluster
button, which enable the other buttons in the same order above. It is nice if we can enable the Interactive-Enabled
button as well, similar to when these windows are added on a valid graph.
When these windows are added on a valid graph, both the Cluster
and Interactive-Enabled
buttons are enabled but clicking
on Cluster
doesn’t seem to do anything but disabling itself? May be I am not doing it properly?
Steps to Reproduce
- Tools/Cluster > Hierarchical
- Tools/Cluster > K-Truss
Expected behaviour: Buttons should enable/disable properly
Actual behaviour: Buttons are not enabled/disabled properly
Reproduces how often: 100%
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top GitHub Comments
Is this not already done? Currently: start - Cluster button is enabled, every other button is disabled click Cluster - enables Interactive button, disables Cluster click Interactive button - every other button enables, interactive button changes text click Interactive button again - every other button disables, interactive button changes text
My assumption is the cluster button, does the calculation then disables itself as the user doesn’t need to do the calculation again. The cluster button enables itself again if the user changes the graph, it also tells the user the graph has changed.
Is this issue still valid or am I not understanding the component that is not working properly?
@GammaVel Yes that makes sense. Thanks.