Note that there are some explanatory texts on larger screens.

plurals
  1. POTextbox + binding to Property with INotifyPropertyChanged from different assembly
    primarykey
    data
    text
    <p>I have a problem with updating the value of property from code which is bind to textbox (the textbox is not displaying new value). </p> <p>It was normally working without any problems but in this case source class is in separate assembly (Don't know if it is making any difference).</p> <ol> <li>If I type in textbox the value will be updated in the code </li> <li>When I change the property value directly in code textbox is not displaying new value.</li> <li>After changing the value in textbox one more time the previously set value (in code) is overwritten (so binding is still working).</li> </ol> <p>Additionally I've checked if PropertyChanged event is fired and it is after every change.</p> <p>Any guesses why it's not working? Below corresponding binding and source class.</p> <p>TextBox Text="{Binding Path=Description, Mode=TwoWay}"</p> <pre><code>[DataContract] public class Source : INotifyPropertyChanged { private String _Description; [DataMember] public String Description { get { return _Description; } set { if (_Description == value) return; _Description = value; OnPropertyChanged("Description"); } } public event PropertyChangedEventHandler PropertyChanged; protected virtual void OnPropertyChanged(string propertyName) { PropertyChangedEventHandler handler = this.PropertyChanged; if (handler != null) { var e = new PropertyChangedEventArgs(propertyName); handler(this, e); } } } </code></pre> <p>I've Fix the problem it was not connected to different assembly obviously. I have a bug in setting value to property.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload