hoowdie

I think I came across a little bug/issue with the live.dial object:

Via scripting I create bpatchers loading UI elements ( live.dials) and then load a saved preset out of a [dict].

The live.dials receive the value ( in this case 1000) and the pointer jumps to the right position

and the value shows 1000 as well. But on the 2. dial you can see that the "fill" doesn't move and it also

outputs the number 0, despite showing a 1000. When i touch the pointer now with the mouse, the output(and fill) jump to 1000, so it seems like the "update" of the live.dial happens for the pointer and the shown value, but not for the fill and the output-value.

I worked around that problem by defering the loading of the preset (to low), but still wanted to share this 

phenomenon, maybe someone else has/had similar issues.

livedial_bug.png

I think I came across a little bug/issue with the live.dial object: 

Via scripting I create bpatchers loading UI elements ( live.dials) and then load a saved preset  out of a [dict].

The live.dials receive the value ( in this case 1000) and the pointer jumps to the right position
and the value shows 1000 as well. But on  the 2. dial you can see that the "fill" doesn't move and it also
outputs the number 0, despite showing a 1000. When i touch the pointer now with the mouse, the output(and fill) jump to 1000, so it seems like the "update" of the live.dial happens for the pointer and the shown value, but not for the fill and the output-value.

I worked around that problem by defering the loading of the preset (to low), but still wanted to share this 
 phenomenon, maybe someone else has/had similar issues. 

Dear Maxers,
I think I came across a little bug/issue with the live.dial object: 
Via scripting I create bpatchers loading UI elements ( liv

live.dial display bug/issue?