I am trying to use the XamTileManager as the Content of an ApplicationMenu2010Item and it does not honor any of the layout settings for the tiles. There is something wrong with the ApplicationMenu2010Item that causes the XamTileManager to get confused. I have also tested this with the WPF WrapPanel. When the WrapPanel is the Content of the ApplicationMenu2010Item it does not wrap its items at all. They are just shown as a single line of continuous items, it never wraps. I am not sure if there is a work-around or some other setting that I am not aware of but from what I can tell at this point...its a bug somewhere...my guess is that its in the ApplicationMenu2010Item.
I am using version 13.1.20131.1009
Could someone please confirm my findings and please tell me if there is a way to get the XamTileManager to behave correctly as the Content of an ApplicationMenu2010Item?
Thanks
I think the issue is that the body of the ApplicationMenu2010 is within a ScrollViewer (to reproduce the MS Office behavior whereby the entire area scrolls) and therefore the children are measured with infinity. Things like a WrapPanel or XamTileManager would probably need an explicit values (e.g. width) in the measure to be able to wrap and when measured with infinity are essentially reporting an auto size (i.e. how big the children want to be). I think the only way you'll be able to get around this would be to disable the scrolling in the ApplicationMenu2010 which will require retemplating the ApplicationMenu2010. We could probably make this a bit easier by binding the scrollbar visibility to properties on the ApplicationMenu2010. Then you could probably disable horizontal scrolling. We can look into changing that part in an upcoming SR.
Hello Eric,
An update is being added to the control so that you can turn off scrolling by disabling the scrollbar’s visibility. In this way the elements within the content of the ApplicationMenu2010Item would then be measured with the available size.
This change has been logged in our internal tracking system with a Development ID of 161425. I have created a private case, CAS-129968-X2X2G6, for you to track this issue and notify you of any changes in its status.
You may access this case at https://es.infragistics.com/my-account/support-activity.
Please let me know if you have any questions.
Sincerely,
Valerie
Developer Support Supervisor - XAML
Infragistics
www.infragistics.com/support
Thanks very much! So when is the next Service Release? Is that going to be 13.3?
This will be updated in a service release for 13.2.
You can view the service release schedule at http://es.infragistics.com/help/service-releases/.
As I mentioned, you will be automatically notified when this is released via your support case CAS-129968-X2X2G6.
So I take back what I said about the UniformGrid. It does work as expected in the eApplicationMenu2010Item if we use Borders as its Child Elements but as soon as you add other controls to the Borders, like a TextBlock, it does not display correctly because of the scroll bar issue stated above. We tried adding a TextBox control to the Border and the text will not wrap and trim because it thinks is has infinite space. So I am looking forward to getting the update so we can control the scroll bar of the ApplicationMenu2010Item.
Well a UniformGrid just measures each child with a percentage of the available width/height depending on the number of rows and columns in the grid that you specify. It then returns a desired size based on the maximum of the desired size width and height of each child times the number of rows/columns. So basically that ends up measuring each child with infinity and essentially using the "auto" size of each to calculate its desired size. Because tile manager is much more complicated and needs to know the actual available size to be able to do things like figuring out which items are in view (because it supports scrolling and virtualization) and that actual available size is not available for something within a scroll viewer.
So we just (as a test) used the standard WPF UniformGrid and it seems to work as expected. This was a surprise based on what has been said earlier.