3 ms·
>professionals are going to want to see the rounded “actual” values Ideally, a generalised design tool should cater for rounding to 8bit and other meaningful p
by marcedwards 5y ago
>professionals are going to want to see the rounded “actual” values
Ideally, a generalised design tool should cater for rounding to 8bit and other meaningful precisions, or keeping source data intact.
All we’re talking about is _allowing_ for a user to type in a fractional number, and for it to be kept. It’s not a difficult request, and it doesn’t negatively affect normal use for people who don’t even know the feature exists. They can continue typing in integers.
If we’re talking about software design, it’s likely that in many situations the buffer being rendered into will be deeper than 8bit per channel, so even covering 0-255 is not enough.
- dahart 5y agoFully agree with the UI suggestion of being able to input exact numbers and furthermore: symbolic math expressions. I would personally use expressions even more often than exact numbers, and expressions would as a byproduct allow a true 1/3 rather than a rounded 33.33%. I was agreeing with this idea above, did it seem like I was arguing? Sorry about that. The UI inputs are a somewhat separate topic from how much resolution is needed for transparency. I think a thorough investigation of necessary transparency resolution would be really interesting, something along the same lines as how perceptual color spaces have been developed, by examining things like the “just noticeable difference” in transparency values and mapping that across the space of all possible color mixtures and transparency values to get an understanding of how stretchy the space is.