![]() So I guess it is up to the Blender users/devs to implement it the way they prefer. This section should be expanded to try and clarify the intended usage. ![]() Unfortunately there is a fair amount of variation in how applications interpret OCIO roles. But instead, they updated the docs with this warning : I asked in one of the OCIO meetings to replace it by “set” or “defined”. This is the current definition :Ĭolors in a color-selection UI can be displayed in this space, while selecting colors in a different working space (e.g. I would have preferred that we settle on defining it precisely and making sure that all developers are on the same page. I think that the official OCIO answer on the “color_picking” role would be : “we removed it from the next ACES OCIO Configs because its behavior is too different between softwares.” Which in my opinion was not necessarily the right move. Perhaps we should add a bug report towards OCIO asking for a better description, including how it is meant to be used. ![]() ![]() This is also one reason why I didn’t take on the challenge to ‘fix the color picker’. Agree, and from a developer point of view, don’t implement something that isn’t clear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |