Some have scoffed when I expressed dismay at the artifice that creates binding. I've just discovered that I'm wasting hours of time converting events into commands. For example, iIt took me an hour to find a piece of sample code that converted KeyDown on TreeView nodes to a binding (found HERE <http://stackoverflow.com/questions/612966/keyboard-events-in-a-wpf-mvvm-app lication> ), but it needed delicate merging with existing ICommand processing classes I use.
I estimate that 50% of the time I spend writing WPF apps is wasted trying to follow MVVM and bind the control XAML to my controller class. It seems that every other man and his dog who is trying to follow the MVVM pattern as well has created untold amounts of confusing and conflicting code for the purpose. I'm sick of searching for and finding jumbles of code that I have to tidy up and include in my projects. I feel compelled to write a small infrastructure that allows event-to-command binding in a generalised way, but I'll bet it's been done already (multiple times and in multiple ways). Has anyone got any suggestions or comments on this? Surely I'm not the first person in the world to have stumbled across these hurdles. MVVM would be wonderful if all of the wiring was just built-in. Greg
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
