A few astute people (@Patric68, @scottisafool) have noticed that we pushed out the September 2012 release of the Windows Phone Toolkit. This was a soft launch, quietly pushed out because we’ve been going like crazy with bug fixes, prepping for Build and doing a whole host of things and I really wanted to get a build out that had the latest fixes and improvements without blocking on all the paperwork.
A big welcome to CustomMessageBox, a new control to the toolkit which is exactly what it sounds like, a customizable, Windows Phone-UI compliant, easy to use message box offering the following features:
Native look & feel including font sizes, layout, alignment and animations Ability to display full screen or to only consume as much space as needed Very simple “basic” mode with ability to easily extend it to complex scenarios Customizable buttons without needing to re-template Here is what it looks like, from the basic (a message and some buttons) to the complex (a full screen message box with an embedded Pivot):
Given how powerful, fast and easy Sublime Text 2 is I find myself editing a great deal of my C# & XAML code in it and then switching to Visual Studio to launch the application. Along those lines I’ve picked up a few C# Sublime tips.
I’m going through the Windows Phone Toolkit bugs fixing some of the low hanging fruit and came across this bug where a ToggleSwitch with a long header is clipped. The proper Metro behavior is that it should wrap which is easy enough to do on a TextBlock.
We’ve received several reports of apps that don’t clear out their text even though the app author is setting the Text property to an empty string. I did a little poking and it’s due to a combination of the application bar and IME.