-
Notifications
You must be signed in to change notification settings - Fork 17
Description
During development of the tree-view I considered using overlays for the status of a node in the tree. I did not found a satisfying solution and decided to go with the approach we used in the table-view. A simple icon to represent the status (success, failure, error warning). This makes the tree-table and the table view consistent/concise.
However, I think it's worth to reconsider the idea. The following table visualizes it:
| Icon Before Run | Description | Current Icon After Run | Alternative Icon |
|---|---|---|---|
![]() |
Suite folder (package folder) | ![]() |
![]() |
![]() |
Suite (package) | ![]() |
![]() |
![]() |
Context (procedure folder) | ![]() |
![]() |
![]() |
Test (procedure) | ![]() |
![]() |
The table shows just the success state. The other states (failure, error, disabled) need also an overlay icon.
The alternative icons do not look very appealing IMO. The success state (overlay) is not dominate enough. I used a filter with an opacity of 25% to reduce that effect. Now these icons look like they represent some kind of "disabled" status, which is certainly not what I want.
This "feature" should be implemented only if we can produce a nice looking set of alternative icons. Otherwise we should stick to the current approach.








