I was thinking the exact same thing. It takes me a longer time to decipher what each icon is without color compared to 2.79. These icons need color as without it, I have to scan each icon to find what I want.
With others, they sit alone and I know what they are spatially, but with many icons together, color is important to help distinguish them.
Having started a more serious project than just doodling around recently i am getting more and more familiar with the new icons. Makes me wanna work in Blender even more than before. Eager to see what the vertical tabs will look like in use.
Great to hear about custom icon sets, that way everyone can be happy and replace any icons they may be confused about!
Categories also sound great, and hopefully some color masks for multi-color icons like this suggestion in the devtalks would be amazing to have in the future:
Iām guessing weāre talking about 2.9 now, thoughā¦
Did you try it ? I think it makes it faster actually, as the properties editor has usually a column shape, itās easier and faster to go on the sides with your mouse rather than all the way to the top
No, itās not in the buildbot yet. Also Iām used to it in c4d, but I still found that switching to horizontal is more effective.
They could give us that option, otherwise itās just limiting the customization in blender, imo.
Itās true! Since these new icons came into my life, Iāve found myself entertaining darker thoughts. I was THIS CLOSE to pouring sugar into some random strangerās gas tank the other day.
We might need to consider the societal implications of monochromatic iconography. It could very easily become the next D&D if weāre not careful.
i just recompiled blender and they are now committed, man it gives me uncomfortable feeling since i used to horizontal layout, definitely they should be an option otherwise iāll go nuts.
This is still ongoing. The internals are relatively easy - itās the storing of image data in the ThemeUI RNA/DNA that is the sticking point. No tutorials on how to extend that in C (plenty for Python level changes, but thatās not going to work for this).
Not sure why youād need to save image data in DNA? I donāt think the image(s) should be part of the userpref.blend. So why donāt you just reference them by (relative) file path in DNA/RNA? The default icons should probably still be the fallback though.
Because as soon as we add that to the mix - we add external complexity to loading/saving themes that didnāt before.
As of right now, the theme you start with is stored inside the startup.blend file. If I want to save the theme, I can export a single XML file with the details. If I want to load a custom theme, I simply import that single XML file. As soon as we add another file to the mix, weāre guaranteeing that people will miss that image file (or not know where to get it, or name it incorrectly, etc).
What we have now is simple - theme is stored in startup.blend (no externalities), and can be saved/loaded with one file. Iād very much prefer that we keep it that simple.
the properties tabs icons need to be either scaled up a bit or their area region sized down(i prefer this one), they donāt look compacted like the old onesā¦it feels like you are using Photoshop tools instead of blenderās properties, their vertical alignment needs to get used to though.