#Colorconverter xamarin code

#Colorconverter xamarin code

You can find the code for the sample project in this post on my GitHub. Actual screenshot with ValueConverters in place This is not something you should want in a MVVM app. Solving it this way with a value converter prevents you from implementing properties that are just for UI elements. Per game is shown for which platform it is and it shows a little tag in the right color. Of course, this is just a simple example, but I actually use it in this form for the BudgetGaming app. When we run the app again with our converter in place, the output will now look like this: Result with value converter Final thoughts This means, if you write a converter that is used in multiple parts of your application you can easily reuse it.

You can declare a resource at either page or application level, or somewhere in between. The way I have implemented it, is by a using it as a static resource. Besides specifying the binding, you will also state a Converter property. But now, the value of the GamePlatform will be used as input parameter for the Convert method. Normally, this will just take the object call the ToString method and output that. You see that I bind the TextColor property to the GamePlatform, which is the enum.

The real magic is happening in the TextCell. Right above here you see the page I have created to show the games. Below you see the empty implementation I have created. The first thing we need to do is create the actual value converter. The way we are going to do this is to give each game a certain color, based on the platform enum. In this solution we want to make clear to the user which game is for which platform. List of games, one for each platform Writing the IValueConverter A screenshot of our initial solution can be seen below. The ListView shows us a list (doh) of custom, complex types and depending on one of the properties of that object, you want to give the text a certain color. First I will give you a scenario that lets you see the problem. You can get around this in several ways, but the most elegant one will be to leverage the IValueConverter interface. When you are implementing MVVM and more specifically data-binding, you are eventually will run into the problem that you want to use a custom type to influence some UI element. Also, this concept isn’t specific to Xamarin, you will also find it in other applications that can leverage the MVVM pattern. How this works exactly we will see in a moment. To stick with our example above, you can take in a enum and write your own switch statement to decide on a color for a label. With these methods you can take any kind of object and write your own logic to transform it into any other object. You create a class that implements the IValueConverter which makes you implement the Convert and ConvertBack methods. The concepts of value converters is pretty straight forward. This can easily be done by implementing the IValueConverter interface to create a value converter. For example, you want to bind some enum value to the text color. The problem is that you want to bind to a value that is not the right type. When using Xamarin.Forms and the MVVM pattern within your app, at some point you are going to run into a problem.