One of the less known capabilities of UWP apps is the ability to inject input. This is especially useful if you want to give the user a guided tour through the app, offer immediate feedback to users with assistive technologies or implement a remote help functionality into your app. In this article we will explore what the Windows.UI.Input.Preview.Injection namespace has to offer and how can you use it in your app. Continue reading “Injecting input in UWP apps”
Another year has come and with it the fourth annual on-line Microsoft Connect conference. Between 15th and 17th November you could watch the newest goodness from Microsoft for all developers on all platforms.
Two main keynotes were dedicated to intelligent cloud and building intelligent applications of the future. Let’s see what Scott Guthrie (of course in his favourite red polo shirt) and other speakers have unveiled. Continue reading “Connect(); 2017”
UWP apps by default have a splash screen that displays while the app is being loaded. Many UX specialists however argue that this is not the best solution from the user experience standpoint. Fortunately, a new feature Windows Fall Creators Update allows us to make the splash screen optional. Let’s see how we can do it. Continue reading “Making UWP splash screen optional”
The x:Name attribute in XAML creates named fields that you can use to access the controls from the code-behind. However, as opposed to WPF, in UWP these fields are private which means you can access them from the code-behind only, not from other classes. While noting it is a good idea from architectural standpoint, is it possible to change this behavior? Continue reading “Modifying XAML named field visibility”
I have come across an interesting oddity while building a UWP app.
XAML VisualStates define the visual look of control in different states. Even though you sometimes don’t need to make distinction for all of them, you should still implement them however (even if they are just a simple copy-paste of another style) or you might meet some inexplicable problems.
In my case I have customized the
ListViewItem style and forgot to include implementations for the
PressedSelected states. Surprisingly everything worked as expected on my devices, as the visual used the
Selected state as fallback. However, I have later found out the same did not happen on other devices and the list view items stayed in the
PointerOver state until the mouse cursor moved away (which also makes sense).
This difference in behavior is especially interesting, as the problem did not originally occur on the stable builds of Windows 10 Creators Update, but now it seems to occur as well (maybe after some patches?).
There are countless times in the life of a Universal Windows Platform app developer when the “Transparent” color comes handy. However, it is good to remember that “Transparent” is still just a color, otherwise you can encounter some unwelcome surprises.