WPF MVVM Light - About views communicating

Question

I am currently working on a project for work. I am seeking an outside design opinion, as well as some general information on the issue I am faced with.

We have a MainWindow.xaml file that is located in the root directory of the project. In this main window is some design and logic for some collapsing stack panels, ribbon toolbar, etc.

So far the idea is to include a different in each stack panel to help make the code neat. The views are located in a 'Views' folder. So just to be clear, the MainWindow.xaml and other views ARE NOT in the same directory. This is open to change, if necessary.

So here is my question/issue: We have a Window ('A'), a main panel with a collapsable stack panel with some information ('B') that is contained in window 'A'. Then there is another stack panel to manage the contents in 'B', (collapse/visisble) ('C').

'A' contains a toggle button to show/collapse 'B'. 'B' contains a button to show/collapse 'C'. 'C' contains a button to show/collapse itself, 'C'.

'C' should have its logic all contain within a view, so the MainWindow ('A') should have a simple tag:

Currently, the bindings for toggling the buttons within 'A' are in the styling. The In this case FrameGradient has triggers like so:

Is it possible to, within the 'Content' View to TOGGLE the panel, 'C', which is NOT within the view? I feel like I am missing a core idea of XAML here. I found a 'cheap' work around which is to place the 'Close' button from the Content View outside of the tags, but then that leads to styling issues and I feel like I shouldn't have to do something silly like that. Again, the idea is that the toggle button for Stack Panel 'C' is contained within another view and I want to be able to toggle it from another view.

I apologize if I am not clear enough, I will provide whoever asks with more information if required here.

UPDATE I have some time to actually add the code I am using so that this might make more sense.

MainWindow.xaml - Logic for Filter panel (Located in root)

Filters.xaml - Logic for Filters view (Located in /Views) The button within the file that needs to Collapse the above StackPanel.

Theme.Xaml - Logic for all styling (Located in root, along with MainWindow.xaml and App.xaml) Button Styling

And finally, the FrameGradient Styling also located in Theme.xaml

SO, I hope this makes things more clear. I want the CLOSE button within Filters.xaml to COLLAPSE the stackpanel that is located in MainWindow. I realize this code is a mess at the moment.

ΩmegaMan · Accepted Answer

Is it possible to, within the 'Content' View to TOGGLE the panel, 'C', which is NOT within the view?

Create a shared VM which each other VM will have a property for which it can access. This VM can be loaded with during initialization of the other VMs. To allow for changes to happen put INotifyProperty(ies) on the shared VM which will then flag the desired logic across all views. Finally bind the target control(s) to your datacontext as normal except sub path into the shared VM target's property.

Hence when one view toggles (two way binding) a shared property it is reflected on the view of the target panel.

Update Example

The idea here is that one creates a viewmodel for the AppPage. That VM will hold generic flags which are shared across all viewmodels. Each subsequently created ViewModel will have a reference to the AppPage's viewmodel.

The example below is a mainpage where the AppVM contains a flag which informs the mainpage whether a login is in process. If it is and that value is true then a bound button on the mainpage will be enabled.

enter image description here

Subsequently the mainpage can override the appvm and put a new value within that flag by a bounded checkbox that can in-directly change whether the button is enabled; thus changing the flag for all other VMs in the process.

Here is the Mainpage VM, for this example I simply create the AppVM, but it could be passed in, or gotten from a static reference elsewhere. NOTE also how I don't care when AVs (appVM) property changes; it is not required for this example (we are not binding anything to AppVM, just its properties which need to be monitored).

public class MainVM : INotifyPropertyChanged
{
    public AppVM AV { get; set; }

     public MainVM()
     {
        AV = new AppVM() { LoginInProcess = true };
     }
}

Here is the AppVm

   public class AppVM : INotifyPropertyChanged 
    {
        private bool _LoginInProcess;

        public bool LoginInProcess
        {
            get {  return _LoginInProcess; }
            set { _LoginInProcess = value; OnPropertyChanged(); }
        }
}

Here is MainPage's Xaml where the datacontext has been set to an instance of MainVM:

I base the MVVM off of my blog article Xaml: ViewModel Main Page Instantiation and Loading Strategy for Easier Binding which explains the other missing items of this example such as the mainpage's datacontext loading.

WPF MVVM Light - About views communicating

Answers (2)

Update Example

Related Questions