Skip to content
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

UI Accent Color #275

Open
AndreaMonzini opened this issue Oct 23, 2024 · 4 comments
Open

UI Accent Color #275

AndreaMonzini opened this issue Oct 23, 2024 · 4 comments

Comments

@AndreaMonzini
Copy link

AndreaMonzini commented Oct 23, 2024

First of all thank you for your work !

Could be possible to expose the UI Accent Color ( button color stroke, timeline, work area rectangle ) in the "friction.conf" of the "Friction 1.0.0-beta.1" ?

For example as personal preference i liked more the warmer Red UI Accent Color used in "Friction 0.9.6"
While the latest "Friction 1.0.0-beta.1" use bluish UI Accent Color ( i noticed also a orange "hover" color too )

Thank you !

@rodlie
Copy link
Member

rodlie commented Oct 24, 2024

Maybe, I prefer to just have one style. Open for suggestions/feedback on the current style.

I could add support for user colors, but that would require some tweaking etc, as they are hardcoded in a function to avoid performance issues on redraw.

@AndreaMonzini
Copy link
Author

AndreaMonzini commented Oct 24, 2024

Thank you for the answer,

with a dark theme in my opinion warmer colors are preferable.

i personally prefer the previous accent color that is warmer ( red ) like in all previous versions.
I noticed that in Friction 0.9.6 the "work area rectangle" red is brighter than other Red UI elements and can disturb a bit the eyes ( for example the timeline vertical line is less brigtht and i prefer it ).

If you can add support for the colors would be great even if in thefriction.conf without implement a theme option.
But i understand that could be a problem for the redraw performance you mentioned.

@rodlie
Copy link
Member

rodlie commented Oct 24, 2024

I will look into a solution, but it might have to wait to v1.1 as this will require several changes and at this point in the release schedule I don't want to do too many core changes.

@AndreaMonzini
Copy link
Author

Thank you and no hurry !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants