Scaling policy issue when compiling. RRS feed

  • Question

  • I'm having a weird issue with scaling policies:

       <Scale Group="group1" Size="Large" />
       <Scale Group="group2" Size="Large" />
       <Scale Group="group3" Size="Large" />
       <Scale Group="group4" Size="Large" />
       <Scale Group="group5" Size="Large" />
       <Scale Group="group6" Size="Large" />
       <Scale Group="group7" Size="Large" />
       <Scale Group="group8" Size="Large" />
       <Scale Group="group9" Size="Large" />
      <Scale Group="group1" Size="Medium" />
      <Scale Group="group1" Size="Small" />
      <Scale Group="group1" Size="Popup" />
      <Scale Group="group2" Size="Medium" />
      <Scale Group="group2" Size="Small" />
      <Scale Group="group2" Size="Popup" />
      <Scale Group="group3" Size="Medium" />
      <Scale Group="group3" Size="Small" />
      <Scale Group="group3" Size="Popup" />
      <Scale Group="group4" Size="Medium" />
      <Scale Group="group4" Size="Small" />
      <Scale Group="group4" Size="Popup" />
      <Scale Group="group5" Size="Popup" />
      <Scale Group="group6" Size="Popup" />
      <Scale Group="group7" Size="Popup" />
      <Scale Group="group8" Size="Popup" />
      <Scale Group="group9" Size="Popup" />

    I get the following error:

    error SC1053: Element '{http://schemas.microsoft.com/windows/2009/Ribbon}Scale' is unexpected according to content model of parent element '{http://schemas.microsoft.com/windows/2009/Ribbon}ScalingPolicy'.

    It refers to entry:

    <Scale Group="group8" Size="Popup" />

    I started getting this error when I added the medium, small, and popup entries for group4.  If I remove the small and popup entries for group4, the file compiles fine.

    I don't see any documentation indicating there is a limit for the number of entries.  However, the XSD file that comes with the Windows SDK weirdly limits the number of <Scale> entries under <ScalingPolicy> to 15.  The number of <Scale> entries under <ScalingPolicy.IdealSizes> is unbounded.

    Does anyone know if there is a reason for this or is it just a bug in the XSD?

    Thursday, July 21, 2016 8:24 PM