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

forgot theme default case #2096

Merged
merged 2 commits into from
Mar 15, 2024
Merged

forgot theme default case #2096

merged 2 commits into from
Mar 15, 2024

Conversation

raszpl
Copy link
Contributor

@raszpl raszpl commented Mar 13, 2024

all that boasting about ""this time working" and I forgot default case #2076

raszpl added 2 commits March 14, 2024 00:16
all that boasting about ""this time working" and I forgot default case 
#2076
@ImprovedTube ImprovedTube merged commit a545ada into code-charity:master Mar 15, 2024
ImprovedTube added a commit that referenced this pull request Mar 15, 2024
@ImprovedTube
Copy link
Member

hi @raszpl!

myColors()

I combined it with theme switching

where?

the call needs to stay in init.js 0bf8911
while custom colors are set by JS.

thats why it should also stay a separate function ( myColors() )


btw, what about activatating custom colors and a theme advance / separately, to overwrite some of the themes colors?

@raszpl
Copy link
Contributor Author

raszpl commented Mar 18, 2024

the call needs to stay in init.js

Yes I see it now. Whole setTheme() needs to be called from init.js. because it does more than just colors in 'custom', it also needs to be able to change f6 cookie: there is a possibility of user switching theme in YT to light while improvetube is set to dark. This will screw colors up without letting the user know why colors are bad. With setTheme() being run at init cookie will be kept in sync with Theme.

0bf8911

indentation! #2106

btw, what about activatating custom colors and a theme advance / separately, to overwrite some of the themes colors?

can you elaborate?

@ImprovedTube
Copy link
Member

can you elaborate?

Custom colors and presets need not be mutually-excluding. "custom" can look different.
A user could 1. Select a preset 2. select a custom colors too. While the other way around could toggle:off all the custom colors (like we did for other toggles, or ask if it was on another screen)
@raszpl

@raszpl
Copy link
Contributor Author

raszpl commented Mar 19, 2024

Ah, additional customization of pre-set themes. Im not big on colors and customization. If you come up with some framework I can polish it up..

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

Successfully merging this pull request may close these issues.

2 participants