You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a template has loads of schemes, it becomes quite hard to see which scheme does what. Therefore, the user should be able to give names to schemes. These do not have to be unique, not amongst all schemes, nor amongst the schemes within a template. The name is of course displayed in the tree.
This may or may not be necessary if #473 is implemented, but since adding names shouldn't be a lot of trouble, I think it should be added anyway.
The text was updated successfully, but these errors were encountered:
Once a template has loads of schemes, it becomes quite hard to see which scheme does what. Therefore, the user should be able to give names to schemes. These do not have to be unique, not amongst all schemes, nor amongst the schemes within a template. The name is of course displayed in the tree.
This may or may not be necessary if #473 is implemented, but since adding names shouldn't be a lot of trouble, I think it should be added anyway.
The text was updated successfully, but these errors were encountered: