Reusable/Terse Way of Transitioning Between Views/ViewModels in WPF without code-behind

Question

THE WHAT

It's bugged me for months, but I finally figured out a generic way to transition between views in WPF--a way that allows me to use whatever animation I want to for the transitions. And no, the VisualStateManager doesn't help at all here--it's only good for transitions within the same view.

Quanta · Accepted Answer

There are frameworks and techniques out there already, but frankly, they all confused the hell out of me or seemed clunky. Another guy's solution was OK, but I didn't really like it for some reason that didn't quite keep me up at night. Maybe, while simpler than most, it still seemed confusing, so I got the gist of it and made my own. It did, however, inspire my solution.

So I imported my helper library, and below is the only code you would need to get transitions going between views. You can use any animation you want, not just my fade in/out animation. If someone lets me know a good place to upload my solution, I'll be happy to share.

THE CODE

There is a window with a red box (RedGridViewModel) and a blue box (BlueGridViewModel). Each box has a button below it that alternately changes the box to the color that it currently isn't. When the button is pressed, the current box fades out, and the new box fades in. The button is disabled while the transition occurs, and both buttons can be pressed in rapid succession without crashing the program. I used two subordinate ViewModels here, but you can use however many you want.

The program running

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows.Input;
using CustomTools;

namespace ViewModelTransitionTest
{
    /// 
    /// View Model for the main windown.
    /// 
    class MainWindowViewModel : ContainsSwappableViewModelsBase
    {
        /// 
        /// ViewModel properties should always follow this basic format.  You can use a string, 
        /// but I like type-safety and I don't have Visiual Studio 2012, so I use this clunky 
        /// extractPropertyNameMethod to convert the ProeprtyName to a string.
        /// 
        public object ViewModelA
        {
            get
            {
                return viewModels[ExtractPropertyName(() => ViewModelA)];
            }
        }
        public object ViewModelB
        {
            get
            {
                return viewModels[ExtractPropertyName(() => ViewModelB)];
            }
        }

        public TransitionCapableViewModel NewViewModelA
        {
            get
            {
                if (ViewModelA is BlueGridViewModel)
                    return new RedGridViewModel();
                return new BlueGridViewModel();
            }
        }
        public TransitionCapableViewModel NewViewModelB
        {
            get
            {
                if (ViewModelB is BlueGridViewModel)
                    return new RedGridViewModel();
                return new BlueGridViewModel();
            }
        }

        /// 
        /// Each ViewModel property should have a command that changes it.  That command should 
        /// call changeViewModel and check canChangeViewModel as follows.
        /// 
        public ICommand ChangeViewModelA
        {
            get
            {
                return new RelayCommand(
                    x => changeViewModel(() => ViewModelA, NewViewModelA),
                    x => canChangeViewModel(() => ViewModelA, NewViewModelA));
            }
        }
        public ICommand ChangeViewModelB
        {
            get
            {
                return new RelayCommand(
                    x => changeViewModel(() => ViewModelB, NewViewModelB),
                    x => canChangeViewModel(() => ViewModelB, NewViewModelB));
            }
        }

        /// 
        /// In the constructor, you'll want to register each ViewModel property with a starting 
        /// value as follows.  And don't forget to call the base constructor.
        /// 
        /// 
        /// 
        public MainWindowViewModel(object viewModelA, object viewModelB)
            :base()
        {
            addViewModelPropertyAndValueToDictionary(() => ViewModelA, viewModelA);
            addViewModelPropertyAndValueToDictionary(() => ViewModelB, viewModelB);
        }

        /// 
        /// The only method you have to override from the base class is this one which regsiters 
        /// your commands with a corresponding viewmodel so that I can raise the relevant change 
        /// notifications because if you're as bad as me, you'll probably screw it up.
        /// 
        protected override void associateCommandsWithViewModelProperties()
        {
            associateCommandWithViewModelProperty(ExtractPropertyName(() => ChangeViewModelA), ExtractPropertyName(() => ViewModelA));
            associateCommandWithViewModelProperty(ExtractPropertyName(() => ChangeViewModelB), ExtractPropertyName(() => ViewModelB));
        }
    }
}

For the sake of completeness, this is literally the only other code I wrote for this example (excluding the very small helper assembly that's a little verbose for this thread):

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using CustomTools;

namespace ViewModelTransitionTest
{
    static class StartingDataContext
    {
        public static MainWindowViewModel DataContext { 
            get 
            { 
                return new MainWindowViewModel(new BlueGridViewModel(), new RedGridViewModel()); 
            } 
        }
    }

    class RedGridViewModel : TransitionCapableViewModel
    {
    }

    class BlueGridViewModel : TransitionCapableViewModel
    {
    }
}

I made use of the following:

WPF Data Pipes

Can't find the original link, but binding wpf events to VM commands was important

Code Contracts Plugin, because I like code contracts

If there's interest, I can post the plumbing code or upload the whole solution somewhere. It's really not that long--two base classes, and a resource file with two styles and two storyboards.

Reusable/Terse Way of Transitioning Between Views/ViewModels in WPF without code-behind

Answers (1)

Related Questions