I am writing a data entry application and am having problems dealing with add vs edit vs view ‘modes’ of the app.
The scenario: From a window, the user selects items in two combo boxes and then clicks a button. If the combo box selections don’t match an existing record, the form should open with a new record ready to have values inserted. If the selections DO match an existing record, this record should be opened with all the textboxes in the form in ‘Readonly’ mode. Should the user wish to modify the existing data, they click the form’s Edit button which sets the textboxes as ‘Editable’.
I’m new to wpf, but in my vba apps, I’d normally have a DataMode property and a ToggleControls method which would loop through the TabControl’s TabItems and then loop through the TabItems’ controls, setting the IsReadOnly property of any TextBox controls found based on the ‘DataMode’ property. However, I have doubts about whether this is the path to follow in wpf.
So, my question is, do i use the approach above? If so, how do I access the controls in a TabItem. This doesn’t work: foreach (Control ctrl in MyTabCtrl) { //if Textbox do stuff }.
If this isn’t the way to do it, can someone show me the way? I’m guessing it’s either a template / style issue or something to do with setting the data as readonly somehow, and then binding the TextBox’s IsReadOnly property to the state of the data. Edit: Oh, or that ViewStateManager thing. All of which i know little about.
An easy approach would be
In Code behind declare a DependencyProperty named
IsReadOnlyImplement the Buttons Click event, so that IsReadOnly gets
falseon ClickBind the TextBoxes to the
IsReadonlyproperty usingDataBindingThis binding assumes that your code behind is not your
DataContextand you therefore have to bind relatively to the Window/ UserControl which the CodeBehind is applied to.This way the TextBoxes listen to changes on this property. When it switches, they change their ReadOnly state automatically.