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
|
This forum is for any questions, comments or feature requests relating to Mindscape WPF Elements. If you are looking to try WPF Elements you can download it here. John-Daniel Trask |
|
|
|
|
Hi, I am testing the WPF Elements Trial. Using the Spin with IntegerTextBox. The IntegerTextBox is bound to a collection object and that works find. However I need to fire an event everytime the value is increased or decreased. Firstly I cant find any value changed event and secondly none of the events that are their do fire. Please advise. The XAML code i have written is following: < ms:SpinDecorator Change="1"> <ms:IntegerTextBox Name="ITBBW" Value="{Binding Source={StaticResource odp1}, Path=Data.BkgBorderWidth, BindsDirectlyToSource=true}" Minimum="0" Maximum="1000" VerticalAlignment="Center" BorderThickness="0"/> </ms:SpinDecorator> |
|
|
|
|
Hi, I forgot to mention another thing. The IntegerTextBox does not initially load the value which I have initialised the collection with. It only starts updating when I decrease or Increase with spin arrows. It should bind and load the value of the collection.
Thanks,
|
|
|
|
|
Hi, We have added a ValueChanged event to the numeric text boxes. This will be available in nightly builds numbered 20080513 or above, available from http://www.mindscape.co.nz/Products/WpfElements/nightlybuilds.aspx from about 1800 GMT. The reason the IntegerTextBox was not displaying your value was that the behaviour of the numeric text boxes was to initially show an empty string if no value was set, but an initialisation with a value of 0 is indistinguishable from no initialisation at all. I have changed the behaviour to always show the value; this should address your issue. This will also be available in the next nightly build. Thanks for the feedback! |
|
|
|
