Something wrong with color sliders?

[Animark]

Hello,

could someone tell me, if the following behavior of the color sliders is normal? I noticed it today for the first time and maybe it has something to do with my last update to 10.0.16.

When I use the color picker sliders and slides the value for L, the sliders of S and H are moving around a little bit.
When I use the color picker sliders and slides the value for S, the slider of H is moving.
When I move the slider of S to the most left, the slider of H is jumping also jumping to the most left.

It dosn't any matter if using the mouse or the stylus. I am on Win7, 64 Bit. The TVPaint is also 64 Bit.

[BenEcosse]

i've noticed that also.

[Animark]

I've tested it today on another computer and found the same misbehavior on 32 and 64 bit. Luckily I could stop our filmschool system admin updating to 10.0.16 early enough. But in the future I will be very very very careful before updating a good working TVPaint - specially when it would happen on 15 workstations and when it would be a very timeconsuming process to go back to an older version. I remember very good the barbeque-bug of version 10.0.13.

[Animark]

Now, before I wanted to go back to version 10.0.14 at my home system, I've seen that there is another update to 10.0.17. I've installed but the Color-slider-bug is always there .

[Animark]

And to come to an end here - I went back to 10.0.14 and be very happy, because the bug is not there . Fortunately I kept those old installer files on my hd.

[Svengali]

Same color slider problems here - also notice If you set LIghtness slider to 0 or 255 OR Saturation slider to 0, the Hue slider setting jumps to 0 (red). I'm pretty sure this didn't happen in 10.0.11 with the sliders... However something similar did happen when using the color picker for the APenColor or the BPenColor, as described in THIS post a short while back.

For now I'm reinstalling back to 10.0.11, even though some of the fixes and improvements in 10.0.16/17 look useful!

Sven

[Fabrice]

hey dev team, we have a problem here