QKit 0.4.1 Update


The past few updates for QKit has been about adding new and useful controls for that are essential to the Windows Phone UX. Today, I’m only pushing out a small update is mainly bug fixes but I still encourage updating to the latest one for the best experience. In this post, I’ll point out a couple notable fixes.

Previously, the JumpList picker items supported multiple themes such as Light, Dark, and high contrast but due to some limitations, those changes only took effect once the app restarted. This was not true for the rest of the JumpList control or the rest of any WPRT app. So, in this update, I’ve worked around the limitation and the JumpList controls should change its look according through any and all theme changes just like the native OS. Also, while I was in there, I noticed that the Light theme for the JumpList control wasn’t exactly right so I aligned the color so now it should be pretty difficult to tell it apart in any theme.

Also, I simplified the GenericJumpList picker items so it should perform a little better and animations should play a bit smoother. The main thing this fix accomplishes is that it will play the closing animation properly in WP8.1 Update 1. In Update 1, many animations no longer play if it’s too taxing. If you have a lot of groups in a GenericJumpList, the picker doesn’t play the closing animation and just disappears. With the simpler item containers, it now plays properly in most if not all cases.

Full change log:

-Changed EdgeSelectButton to derive from Button instead of ButtonBase.
-JumpList pickers now support theme changes during runtime. No need to restart app anymore.
-Improved Light theme colors to better match OS for JumpListPickers.
-Simplified GenericJumpList picker items for performance increases.
-Renamed incorrectly named JumpListItemBackgroundBrush to JumpListGroupHeaderBackgroundBrush and JumpListItemTextForegroundBrush to JumpListGroupHeaderTextForegroundBrush.


InputAwarePanel Improvement + QKit Open Sourced


One of the limitations that my InputAwarePanel had was that even though it resized available space properly when the InputPane is shown, it didn’t actually keep the TextBox in view when that happened. Even though this sounds like a simple task, I quickly found out that it was quite the opposite. I’ll go over some of the issues I encountered, point out unresolved limitations, and show a small demo of it in action. Along with this little improvement, I’ve also made the source code available on CodePlex for anyone to check out and improve so please check it out and report any bugs you may find.

Continue reading