Styling WPF buttons for Image Viewer

A quick post on styling the next & previous buttons for an Image Viewer written in WPF, I'm using the MahApps libraries to give the UI a modern look & feel - they are available as nuget packages, I'm using the core and resources packages.

The initial version is very simple and hopefully the behaviour is obvious - the image flanked by a couple of buttons for moving to the next\previous image:

The XAML for this is very simple, using grid layout to achieve the alignment required, one thing to note is the Stretch characteristics of the Image control - the image ratio will be maintained as the app is resized. Also I'm using the default (implicit) styling for the button controls, these come from the MahApps libraries:

The next iteration sees the 'cleaning up' of the actual UI elements - the removal of border from around all the controls and the applying of the flat button style to the next & previous buttons.

The other majors changes are the replacement of the 'next' & 'previous' text with a couple of icons implemented as Path embedded on a Canvas, and the moving of the buttons to on top of the image - this obviously is now not ideal because it's obscuring parts of the image:

The XAML has changed subtly, the Image now spans all the columns in the Grid and each Button content has been replaced with a styled VisualBrush:

The Visual for the next button is defined as follows:

The final version isn't that different to the previous, the most obvious change is the use of Property Triggers to control the Opacity of the buttons - the buttons only become visible when the mouse is moved over there location, this means for the majority of the time the whole image will be visible and not obscured by the buttons.

The XAML is now simpler - mainly because the styling has been abstracted away into a separate style resource dictionary:

The complexity (which isn't very complex really) is moved into the styling for the buttons:

Comments

Implementing a busy indicator using a visual overlay in MVVM

This is a technique we use at work to lock the UI whilst some long running process is happening - preventing the user clicking on stuff whilst it's retrieving or rendering data. Now we could have done this by launching a child dialog window but that feels rather out of date and clumsy, we wanted a more modern pattern similar to the way <div> overlays are done on the web. Imagine we have the following simple WPF app and when 'Click' is pressed a busy waiting overlay is shown for the duration entered into the text box. What I'm interested in here is not the actual UI element of the busy indicator but how I go about getting this to show & hide from when using MVVM. The actual UI elements are the standard Busy Indicator coming from the WPF Toolkit : The XAML behind this window is very simple, the important part is the ViewHost. As you can see the ViewHost uses a ContentPresenter element which is bound to the view model, IMainViewModel, it contains 3 child v...

Showing a message box from a ViewModel in MVVM

I was doing a code review with a client last week for a WPF app using MVVM and they asked ' How can I show a message from the ViewModel? '. What follows is how I would (and have) solved the problem in the past. When I hear the words ' show a message... ' I instantly think you mean show a transient modal message box that requires the user input before continuing ' with something else ' - once the user has interacted with the message box it will disappear. The following solution only applies to this scenario. The first solution is the easiest but is very wrong from a separation perspective. It violates the ideas behind the Model-View-Controller pattern because it places View concerns inside the ViewModel - the ViewModel now knows about the type of the View and specifically it knows how to show a message box window: The second approach addresses this concern by introducing the idea of messaging\events between the ViewModel and the View. In the example ...

WPF tips & tricks: Dispatcher thread performance

Not blogged for an age, and I received an email last week which provoked me back to life. It was a job spec for a WPF contract where they want help sorting out the performance of their app especially around grids and tabular data. I thought I'd shared some tips & tricks I've picked up along the way, these aren't probably going to solve any issues you might be having directly, but they might point you in the right direction when trying to find and resolve performance issues with a WPF app. First off, performance is something you shouldn't try and improve without evidence, and this means having evidence proving you've improved the performance - before & after metrics for example. Without this you're basically pissing into the wind, which can be fun from a developer point of view but bad for a project :) So, what do I mean by ' Dispatcher thread performance '? The 'dispatcher thread' or the 'UI thread' is probably the most ...

Awkward Coder

Search This Blog