0

I'm working on an application, and I'm using the MVVM approach.
Basically, there are currently two Pages, and 1 MainWindow.
I switch between the pages using a Frame inside MainWindow.

In the main window, there are 2 buttons which are basically global and should show in all pages; x (exit) and settings.
This is basically my 'shell', as I decided to not use a window border.

The problem is I'd like each page to have a different background and this is where it gets complicated:
- Settings page: Grey background.
- Main Page: Rotating background color that changes according to a property.

The thing is the background is being set in the main window, because it should apply to the global area as well (the top, where the exit and settings buttons are).

I first set the background (in MainWindow) as bound to a property the represents the current page (the value is then being translated into a color hex code with the help of a converter).

All in all, this results in a case where the background changes when a page is changed, but not when the property inside MainPage changes. I can clearly understand why, but I have no idea how to solve it.

The possible solutions I came up with so far:

  • Somehow causing the binding in MainWindow to update/refresh when the property is changed in MainPage.
  • Changing the background manually from inside each of the pages. (Although doesn't it negate the idea of mvvm?)
  • Move the background into each of the pages and set it from there, while making the global buttons on top of the page (which could be a bad thing in case controls end up overlapping).

If so, what would be the best solution to this problem?

Asaf
  • 2,005
  • 7
  • 37
  • 59
  • Why not make the pages background transparent? So they actually show the background of the `MainWindow`? – Stefan Over Jun 14 '14 at 15:26
  • They are transparent. They do show the background of the `MainWindow`, but I want that background to change both by the current page and a property inside a page. – Asaf Jun 14 '14 at 15:31
  • 1
    Hey @xTCx, I updated my answer with working examples. Hope it helps you out! – Mikko Viitala Jun 22 '14 at 21:08

2 Answers2

2

If you haven't already, I'd suggest you install some package via NuGet to make MVVM style development more enjoyable. I personally prefer MVVMLight which is... well, light, but it also packs lot's of helpful features.

To communicate between ViewModels, you have (at least) two possible approaches.

1) ViewModelLocator (not recommended)

ViewModelLocator is central place holding references to all of your viewmodels. You could add a property that is then used by all of the viewmodels to get/set the background.

....
x:Name="Main"
DataContext="{Binding Source={StaticResource Locator}, Path=MainVM}">
....
<Grid Background="{Binding Background, Converter={StaticResource StringBrushConverter}}">
...

2) Messenger (recommended)

When ever property changes in your viewmodel(s) or method is executed, you could send a message that your MainViewModel is registered to listen to. Sending a message would be as easy as...

Messenger.Default.Send(new UpdateBackgroundMessage(new SolidColorBrush(Colors.Blue)));

And you'd register for this message in your MainViewModel's constructor:

Messenger.Default.Register<UpdateBackgroundMessage>(this, message =>
    {
        Background = message.Brush;
    });

Actual message class would be:

public class UpdateBackgroundMessage : MessageBase
{
    public UpdateBackgroundMessage(Brush brush)
    {
        Brush = brush;
    }
    public Brush Brush { get; set; }
}

I know I'm simplifying things here but I hope you got the idea. Both approaches are valid even if you decide not to use MVVMLight.

Edit:

Here's Git repo with example https://github.com/mikkoviitala/cross-viewmodel-communication

imgur

Community
  • 1
  • 1
Mikko Viitala
  • 8,344
  • 4
  • 37
  • 62
  • Thank you! I think I will go with the messenger approach, seems more intuitive to me. I will also check MVVMLight. BTW, thanks for setting up an example project!!! :) – Asaf Jun 23 '14 at 19:29
1

I think you should use Application Properties for storing background. There are various benefit of this :

1) Globally available 2) Easy to remember or store user preference 3) Automatically maintain separate profile for each user as it store values in AppData folder of user.

you can use Messenger to notify that background property has changed so that main window or shell could pull out new background value and update it.

Shivam cv
  • 526
  • 5
  • 16