When dealing with resizable dialogs, anchoring is the best way to ensure that certain controls, like containers or data grids, stretch and resize along with with the form itself. This ensures that the user experience is enhanced when dealing with large quantities of data that are, by default designed, viewed on small window. While this design is sufficient for certain cases, in other, more business like, there are limitations that can be overcome by using different container. read more
upcoming talks
none, but you can drop me an invite :)
tags
.NET asp.net async Behavior bug C# C#5 C++ C++/CX c++11 canvas debugging design DirectX DirectX Tool Kit Extensibility gamification Google HTML5 IIS js KineticJS KZ layout ListBox Metro microsoft xna OAuth OData RestSharp Team Explorer 2012 TFS11 three.js tool vs11 vs11 beta WebGL Windows 8 Windows Forms WinRT wp7 wp8 WPF XAML XNAnotable posts
- Create app bar button icons using Segue UI Symbols font
- Installing and configuring OData Service for TFS 11
- DirectX Tool Kit - native "XNA" for Windows 8
- DirectX and XAML in Windows (Phone) 8 - part 1 of N - Simple 2D surface
- Google Data API with RestSharp on WP7
- C++ and Metro: event handling and MessageBox
- Drawing the control bar for Metro-style WPF applications
- Metro Studio - your modern UI style icons paradise
- Combining three.js and KineticJS
Back to top