Skip to main content

Custom button image of AppBar in a Windows 8 Metro application

Intr-o aplicatie Metro pentru Windows 8, in partea de jos avem un app bar in care putem sa punem diferite comenzi. Este extrem de asemanator cu app bar-ul de pe pe Windows Phone 7. By default, framework-ul contine o lista de icoane pe care le putem folosi pentru aceste comenzi.
Pe langa aceste imagini, sunt cazuri cand dorim sa avem iconite custom, pe care noi le-am definit. Aceste imagini trebuie adaugate sub forma unor resurse png. (48px pe 48px). In general avem cel putin doua resurse, una cand butonul este selectat, iar cealalta pentru starea normala.
Urmatorul pas este sa ne definim un stil pentru a avea un efect pe buton cand acesta este apasat. Acesta se poate face ca in felul urmator:
   <Style x:Key="CustomMyCommandAppBarButtonStyle" TargetType="Button" >
            <Setter Property="Template">
                    <ControlTemplate TargetType="Button">
                        <StackPanel  Height="70" Orientation="Vertical" Margin="{TemplateBinding Margin}">
                            <Image Source="/Assets/normalStateButton.png" x:Name="nonpressedImage"/>
                            <Image Source="/Assets/pressedStateButton.png"
                             Visibility="Collapsed" x:Name="pressedImage"/>
                            <TextBlock Text="{TemplateBinding AutomationProperties.Name}"
                                Style="{StaticResource BasicTextStyle}"/>
                                    <VisualState x:Name="Normal"/>
                                    <VisualState x:Name="MouseOver" />
                                    <VisualState x:Name="Pressed">
                                            <ObjectAnimationUsingKeyFrames Storyboard.TargetName="pressedImage" Storyboard.TargetProperty="Visibility">
                                                <DiscreteObjectKeyFrame KeyTime="0" >
                                            <ObjectAnimationUsingKeyFrames Storyboard.TargetName="nonpressedImage" Storyboard.TargetProperty="Visibility">
                                                <DiscreteObjectKeyFrame KeyTime="0" >
Totul pare destul de simplu, dar va atrag atentia la un lucru, daca nu setati si visual state-ul pentru actiune de mouse over, chiar daca nu definim nici o actiune pentru acesta, dupa ce se apasa butonul, imaginea care o sa ramana afisata o sa fie tot cea care se afiseaza cand butonul este apasat.
<VisualState x:Name="MouseOver" />
Pentru acesta problema este nevoie sa adaugam si visual state-ul pentru mouse over. Lasandul fara nici o actiune custom, o sa fie folosita cea default. Prin acest mod, ii putem spune la buton sa revina la normal dupa ce se face click pe el.
Din cauza ca nu sunt un expert in XAML, mi-a trebuit ceva vreme pana sa imi dau seama care era problema. Sper sa nu patit si voi la fel.
Era sa uit, dupa ce va definiti acest style, tot ce mai este nevoie sa il aplicati stilul pe butonul vostru din AppBar.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…