Long story short. No.
I recommend using the plugin that calls dockers to it to do that.
Hey, small issue here. My mixer sliders are just blank. I want them to have the classic HSV format but they are just blank sliders with a number %.
I donāt have anything in front of me right now, but I believe if you go into the settings for the docker, one of the options In the other tabs of it (color or system, I donāt remember which) one of the check boxes should make them permanently visible. I donāt recall what the label is for the option, buts definitely not āmake the mixer visibleā so it took me a bit to find a well.
That worked! Thank you 
your already in HSV mode. now you just need to save colors to mix them together. press and swipe up or down to quickly save and load or RMB for the menu. then you can use the slider.
1 Like
Hi
First of all, thank you for your plugin, this is greatly appreciated.
If this is not too much, do you think
- you could modify the hexagonal view to be static (keep the hexagonal shape when varying values in the sliders?)
- or better, add a view like this (hexagon + triangle selector) ? (OpenToonz color picker)
To me this is a more friendly interpretation of color theory geometry.
And your hexagonal view is in that direction, so I hoped that it could be somehow going in that direction?
If this is possible, of courseā¦
Thank you for your consideration.
Take care
2 Likes
I must say that the hexagon panel is not gonna change though. I have seen the open toonz picker and been curious about it but not enough to make a new one. I feel gamut is really close to the hexagon part but the 2 shapes make it suoer stable.
1 Like
I already fixed that bug, just update it
Hello, first iād like to thank you for making this plugin, iāve been using it for more than a year at this point and itās amazing. I wanted to let you know of a change thatās happened in krita 5.3 thatās affecting your plugin, iāve been talking in another post with people on the forum about this, because at first i thought it was a modified version of krita weāre using but itās something that happens with krita 5.3, itās a change about how python plugins work that will make pigment.o need some rework or update. Iām not a coder so i donāt really understand exactly whatās going behind curtains, but this is what someone who knows his stuff is saying thatās wrong in krita 5.3:
If it were possible, could you take a look at this and maybe implement some kind of fix?
Thank you for all your work on the plugin!
I can write you an ESSAY why I am not changing things, but the short answer is I am not changing things 
As for your other questions :
- if you have performance use the performance options. yes they exist
- When it is needed to update, it will be updated
Donāt spread rumors please. thank you
I think you heavily misunderstood, this is no rumour, itās not a performance issue because of hardware or whatever, we have proof that this is a slowdown happening in krita 5.3 and probably will happen in future versions, i have read the documentation of pigment.o and know of things you made for the plugin to work/run better and have changed stuff in krita so that it performs better on my pc. I just wanted to let you know that this was happening in case you could take a look and see if thereās something you can do for it to work as it used to, your plugin has other bugs which i didnāt even mention considering you havenāt release any update in well over a year as far as i can see in your github, sorry if iām wrong iām not double checking this as youāve already proved youāre not interested in maintaining your own plugins.
I am using the updated version. I deleted the plugin, downloaded it again, reinstalled it, and the problem persists. I guess it doesnāt work. Anyway, thank you.
You say your not spreading rumors but then you spread them with the same breath. My plugins are not abandoned. I use them everyday !!!
Furthermore, concerning your claims you using it in an unstable version. Only one unstable version in 3 years has demanded my attention. what I am waiting now is for the Qt6 version. all other unstable version reports have been fake reports in the end I will wait to see about 5.3.
This is where you can report your issues.
Can you then please give me a better report of the error message. one that is not just a screenshot with the important stuff taken out. please.
But as you can see the error is not reproducible anymore. and the way I fixed is, even if it is wrong, it will still be correct. so the error occurring should be literally impossible currently. you probably just need to clean Kritarc file from the old Pigmento entries now.
1 Like
You were right, I just had to clean the kritarc file. Now it works perfectly. Thank you so much! 
1 Like
Your more than welcome.
1 Like
Okay, first things first, stop with the rumors thing. If you want to pretend your plugins arenāt abandoned, then make a good github page, for someone who knows how to code on python at least, you really made a bare bones github page. My first encounter with your plugin was github and my guy, not even a changelog? no releases, youāve any idea how hard it is for normies to download from github? lmao. About the claims, yes, it is an unstable version, however, it seems that krita is indeed pushing that change forwards, thatās why i reported it to you, if you donāt want to do anything about it, whatever, someone already made a fix for it and another solution is as simple as not using your plugin anymore, i just wanted to let you know about that change so that you can do something about it, you might very well be right about it just being something that will not go through or it may, who knows, i just wanted to let you know. About reporting issues too, man, itās what i was telling you about your github, i donāt see anyone ever reporting issues and even worse, the only one you have is a suggestion left on open, if youāre not taking suggestions, not releasing a changelog, not making a releases page, then it pretty much looks like an abandoned project, especially since you made it open source. Iām grateful to you for your plugin, but man, donāt call everyone a bot or say people are spreading rumors as if thereās a bad reputation in place, you just made a plugin, is it that hard to admit that your code can be unoptimized, can be poorly written or anything like that? are you the best coder in the whole word or something? set your ego aside man, weāre here suggesting you things and trying to make the plugin a good thing for everyone, yet you refuse to everything, smh. And about the bug iāve come across, iād report it but i really donāt see you as someone willing to fix a bug based on how you talk here in the forum, so whatās even the point? I hope, at the end of the day, if krita 6 or 5.3 goes live and you see for yourself how your plugin is not working as intended, that you fix it. Thank you for your time.
I think you should calm down a bit. I donāt think youāre doing things correctly. First of all, EyeOdin is right on several points. His plugin hasnāt been updated in a year, but that doesnāt mean itās been abandoned. Many Krita plugins havenāt been updated in the same amount of time or longer, but that doesnāt mean theyāve been abandoned. It just means that updates arenāt necessary at the moment. In fact, he has updated some of his other plugins.
Secondly, itās true that he canāt fix problems in an alpha version because itās not a version made for production. That bug can only be fixed in another update. Besides, youāre almost demanding something heās not obligated to do. He made this for free, not for pay.
So you should calm down a bit and think about what you write. Itās not right to compare others or make assumptions.
2 Likes
Iām not demanding him to update it or fix it or whatever, i just let him know of it, his use of wording here is what made me react, yes, i understand his plugin not being updated can easily mean thereās nothing to update, but there are bugs iāve found and have not been reported, as i explained earlier, based on his github, itās a project that other than the wiki, it has no clear info about updates or whatever, even the zip doesnāt have a version, what can you expect from that? how do i know iām downloading an update or something? Heās getting suggestions and well, they are suggestions, itās ok if he doesnāt do anything about it, but i meanā¦ is it that hard to just say āiāll keep it in mind, iāll see what is going onā anything like that, hell i even linked the possible cause/solution to what the plugin is doing and all he has to say is that iām spreading rumors? aightā¦ if it sounded as iām demanding him to fix it, well, my bad but thatās interpretation of a written thing, not the actual meaning. Iām by no means insulting him or trying to make him work for this for free, iām just letting him know that the plugin is not working as intended in 5.3, if the changes in 5.3 go live or continue, it wonāt work as it should, iām telling him so that he can maybe prepare something, cuz if i could iād fix it myself but iām not a coder and iām not interested in learning python to fix a plugin i didnāt write. Was there a need to say weāre spreading rumors? rumors about what? about something that DOES happen in 5.3? how is that a rumor lol. But whatever, itās his plugin, his time, his life, i just wanted to let the guy know because i loved the plugin, and the bug i didnāt report itās because i simply donāt use the feature thatās bugged, and as i said, the github page is so barebones when it comes to anything that it makes me believe he just uploaded the plugin and forgot about it. Donāt make this more than it is, iām just letting him know of something, heās saying iām spreading rumors.