This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
It appears that the default Saturation and Value are not being pulled from the data context properly when bound. I have an HsvColorPicker with H/S/V bound to values, where the underlying Hue is 255, and S and V are both 1.0. When the picker is first loaded, the UI always has a Hue + Saturation of 0.0 selected (even though the bound value is 1.0). The Hue is loaded correctly. This means that touching the Hue slider, for example, pushes through the 0 and changes the underlying values (even if you don't touch that portion of the control). |
|
|
|
|
Hello Thanks for brining this to our attention. These binding issues will be resolved in the next nightly build. Jason Fauchelle |
|
|
|
