model view controller - MVVM in WPF and many refresh actions interlinked -


we maintain large wpf mvvm application , notice databindings (properties , commands) result in large , therefore obscure stacktraces.

e.g. close view a , observe method load view a called 2 times in row.

view <--> viewmodel <--> data model

what miss controller in between determines views , parts of views need update.

view <--> controller <--> viewmodel <--> data model

in wpf-mvvm controller part data-binding, manage better.
has nice idea + example code how improve in wpf?

the problem cannot solved wpf, must tackled a better architecture.

a high level "master viewmodel" act controller or mediator orchestrates refresh actions, order.

i cannot whether perhaps redux.net helps.


Comments

Popular posts from this blog

python Tkinter Capturing keyboard events save as one single string -

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

javascript - Z-index in d3.js -