Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The problem seems to be (though can't say for sure without more XAML) that you're laying out your controls using the <strong>Margin</strong> to position elements. As you've just found out, this isn't necesarily the best approach to take. Silverlight has a wide range of layout containers that help you lay out your controls without requiring you to manually position each element.</p> <p>In this instance, it seems that you might be positioning controls vertically stacked above each other, for which you can use the <code>StackPanel</code> container. You simply add each child element to the <code>StackPanel</code> and it handles layout them out on top of each other. Once you've done this, because the next element is always below the <code>ListPicker</code>, when the <code>ListPicker</code> expands, the elements below it are pushed down.</p> <p>For more complex layouts you can use the <code>Grid</code> container (which is almost certainly the current parent container of your controls), but you should use rows and columns to ensure that elements don't "bleed" into each other. Note: The flexibility of the <code>Grid</code> element comes at a price and you shoudl carefully consider whether you need to use it or whether you can use a simpler container, especially for repeated containers in lists, for example.</p> <p>If you're new to the layout system in Silverlight, you may find this resource particularly useful: <a href="http://msdn.microsoft.com/en-us/library/cc645025(VS.95).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc645025(VS.95).aspx</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload