Yes. It can be a little bit awkward but hex codes are heavily used enough that I think it makes sense.
Is there a particular use case it gets in the way of? I figure entering grayscale values is better done as a percentage regardless (type in 0.5 for 50% brightness).
I just tried to use grey-scale values based on 0-255 range. I’ll try use X/255 then.
But it’s a bit strange for me that 255 not treated as HEX, while for example 254 does.
Yeah, I made a specific exception for 255 because a lot of people are likely to fire that off to mean white.
Uh,
I’m sure that’s not intended.
Is there going to be a way to customize these, if ever? They’re useful at the moment, but I can see if someone wants to make entering 4, 2 correspond to a Vector3 of 4, 0, 2 often.
That’s probably why. It’s okay, people are still replying
Probably not. No matter how it would be made, it will be too complicated to make for how simple the task is. And also, the properties panel isn’t really made to support settings for each slot. Basically, it would take up too much space.
Yeah, this is a mismatch of wants. If we were going to create some complex API we would rather make an general API for Properties panel customization (like, showing your own virtual properties), not a specialized one that forces you to hack more capability into the shorthand property input.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.