Having looked at several tutorials I can't help but think data binding seems unnecessarily complicated...
Let's say I want a label to show whether a user is logged in or not. The obvious way to me is in the login code put something like: lb_LoggedIn.Content = User + " Logged In"; and then in the logout code put: lb_LoggedIn.Content = "Please Login"; and maybe add a link or something.
I don't get why you would do all the complexity of adding dependency properties and bindings and stuff here? Would it be useful if there was more than one way to login or logout?
Or alternatively, I want to display a list of names pulled from a web xml file. So they're not known at design time & once the program is running they won't be changed again. So again, I could databind a listview to an arraylist or something, but isn't it simpler just to add them to the listview one by one as they're first read from the XML?
I feel like I must be missing something fundamental here! If anyone can point me to a simple example of binding a control to a single property that would be great, most of the tutorials show binding one control to another or binding to a list of info hardcoded into the XAML which both seem completely pointless.