Since the Aug11 release of the Windows Phone Toolkit, the ItemCountThreshold's setter is now marked private (thus effectively hardcoding the threshold to 5 items). If this property was previously set in XAML, the code will still compile though it will now fail at runtime (XAML parse error).
Please consider undoing this breaking change. I understand the desire to improve platform consistency, but in this instance it causes more harm than good, especially since it is a legitimate feature that the API used to allow. There are plenty of scenarios where expanding a ListPicker to 7 or 8 items makes more sense than calling the disruptive full mode popup. People who relied on this functionality (enforcing the expansion mode rather than relying on the full mode popup) must now recompile the toolkit and maintain their own build (or endure the disruptiveness of the full mode popup when the expansion mode would sometimes end up being much more elegant).
Comments:
Please consider undoing this breaking change. I understand the desire to improve platform consistency, but in this instance it causes more harm than good, especially since it is a legitimate feature that the API used to allow. There are plenty of scenarios where expanding a ListPicker to 7 or 8 items makes more sense than calling the disruptive full mode popup. People who relied on this functionality (enforcing the expansion mode rather than relying on the full mode popup) must now recompile the toolkit and maintain their own build (or endure the disruptiveness of the full mode popup when the expansion mode would sometimes end up being much more elegant).
Comments:
We are working to get better docs out there but this is closed as "By Design". One of the main drives of the toolkit is to provide controls that are as close the 1st party experience as possible and that means at times adhering to their constraints as well.
I've engaged the 1st party control team to discuss opening this up as an option.