I’m not quite sure how to deal with this problem. I’m using a bunch of comboboxes with dropdown lists of values we allow the user to set a property too. (i.e. Currencies = “USD, CAD, EUR”).
Every now and then, when we load data, we’ll find the currency is something not in our list, like “AUD”. In this case, we still want the combobox to display the loaded value, and the current selected Currency should remain “AUD” unless the user chooses to change it, in which case their only options will still be “USD, CAD, EUR”.
My problem is that as soon as the control becomes visible, the ComboBox is calling the setter on my SelectedCurrency property and setting it to null, presumably because the current value “AUD” isn’t in it’s list. How can I disable this behaviour without making it possible for the user to type whatever they want into the Currency field?
This seems to be a reasonably common problem. Imagine you have a lookup list in the database, maybe a list of employees. The employee table has a ‘works here’ flag. Another table references the employee lookup list. When a person leaves the company, you want your views to show the name of the old employee, but not allow the old employee to be assigned in future.
Here’s my solution to the similar currency problem:
Xaml
C#