Levels tool has problems with output number entry

[frio]

This has changed in the 5.1 branch I think, running 5.100.8930.35902:

Previously when you entered an output high/low level number directly, it would get accepted and used as is even if the gamma tick didn't get updated to an appropriate position -- the gamma *value* was still okay even if the tick wasn't repositioned. Now it seems like the value gets capped to where the midpoint/gamma tick is, then the gamma tick gets updated.

 

Steps to reproduce:

1. Start from scratch to have default settings.
2. Open levels adjustment.
3. Input 32 as the output high level. It will get capped to about 128 instead, since that's where the gamma tick was located in the middle. Gamma tick drops to about 1/4 height.
4. Input 32 again: it will now be set to about 64 instead, again matching the previous gamma tick height.
5. Cancel. Open levels again.
6. Input 8 as the gamma level, to get it as low as possible.
7. Input 32 as the output high level: it will be set to 32, since it didn't "hit against" the gamma tick.
8. Same happens for setting the output low level higher than the gamma tick.

 

It's not a huge deal, but it keeps throwing me off since I often do material maps that are limited to specific output high/low ranges.

Edited June 24 by frio

[Rick Brewster]

Thanks -- I've filed a bug and will definitely look into this. Maybe not for the next alpha build, but certainly during beta.