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

[Request] Regression for the bitmap layer color palette behavior. #945

Open
Jose-Moreno opened this issue Apr 14, 2018 · 4 comments
Open

Comments

@Jose-Moreno
Copy link
Member

--Issue Summary--

I've been thinking all this time, we should really try to go back to how the color palette worked for both bitmap and vector layers before, allowing you to change without restriction the current color swatch while using the color wheel.

Instead we could add a "LOCK" toggle on the color palette panel that enables the current bitmap behavior preventing the user to change color swatches while using either layer type.

This I believe, improves efficiency when organizing the palette, and helps to avoid the initial confusion which forced us to come up with the current behavior in the first place.

[Discussion]
If you have other ideas , let's discuss them in this thread so there's clarity on how to finally implement this function when the roadmap calls for it.

@MrStevns
Copy link
Member

I'm doing some UI implementation around the color palette and color wheel atm. so I'm considering looking into this. I'm not sure adding a lock is self explanatory enough for users to get the idea.

From a users perspective, I would think when you lock something, then you lose the ability to add, edit nor remove it. That's not what we want though is it?

You just want to be able to toggle whether the current swatch should be updated when you change color using the colorwheel or spinboxes, correct?

if so then a nifty icon could maybe help with that, not a lock though.

@MrStevns
Copy link
Member

MrStevns commented Apr 29, 2018

poc

Here's a proof of concept of what I've come up with so far.. it's not fully functioning because the eyedropper tool relies on some things that I've modified atm. and vector lines are connected to the palette directly, so that'll require a bit of reworking to get that working properly but you should get the idea :)

@Jose-Moreno
Copy link
Member Author

@candyface Agreeing to what you said and what you're showing. Of course I didn't meant a literal lock (that's why I put it under quotation haha), but your icon idea of "color flow" is exactly what I meant in terms of functionality. As a toggle, I feel it would be a great way for people to understand that the palette can be separate from the color selection.

On a side note, I've seen the slider mockup you've been sharing lately and I think it's great as well!, let's not forget however that most artist do prefer to choose, so this visualization could be optional via a visibility toggle similar to the one in the color palette.

As an example that comes to mind in Easy Paint Tool SAI, they use toggle buttons and the main color widget is the color wheel and so you can "add" sliders, mixers and whatnot as below that color wheel, although you can use any of those you prefer as your "main" widget just by deactivating the others. I think they all work inside the same "panel" though:

Color Wheel Toggle Only
image
Most Color Widgets Toggled Active
image

@MrStevns
Copy link
Member

MrStevns commented Apr 29, 2018

I'm glad you like it.
I agree that people should have the ability to hide it if they want, right now it's just shown in the same widget as the colorwheel but I was considering making the slider + spinbox a separate widget that you can add or remove.
I like the idea of having widgets shown as icons too though... I think I'll look into that aswell.

My eyes totally ignored your quotation marks btw. so sorry for not getting that you didn't mean an actual lock :3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Discussion
Feature Priority
  
Discussion
Development

No branches or pull requests

2 participants