-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EEZ Flow: Styles can be hierarchical/derived #257
Comments
This is fixed now. |
I'm not sure I want to automatically remove changes that are not needed anymore. Because, if you first move style at some position and if you change your mind and move somewhere else then it can loose modification. Maybe we should extend this menu: With another option called "Remove Unnecessary Modifications". |
Hm, we don't have this menu in style properties, only in widget style properties. |
With automatically I mean: drag a style to become a 'child' style AND both these styles have a setting explicitly set to the same value it will remove this setting in the child style because it is already set in the parent child. Doing this automatically after the dragging doesn't seem like a good idea, but implement it like 'reset all modifications' but in the styles menu and calling it 'Remove redundant modifications' or 'Simplify style'. I really like this enhancement as it is already implemented. It allows for good overview and cleanup of styles (in combination with the 'find all references' feature) without needing a 'big design up-front'. |
I think this is exactly what is described above. |
Perfect now. |
Working with styles is pretty essential in EEZ Flow if the project get bigger. To make it more manageable I would like it to be possible to derive styles from each other in the UI (it doesn't have to be in the resulting code):
The text was updated successfully, but these errors were encountered: