Answered Scrollbar problems with SemanticZoom

  • Tuesday, June 12, 2012 8:58 AM
     
     

    I am using a default grouped GridView placed inside a ScrollViewer (ScrollViewer fixes scrollbar's length).

    If i use semanticzoom i have to remove scrollviewer which causes scrollbar to get broken again.

    Broken: Scrollbar gets bigger or smallar while scrolling which prevents us from scrolling the content by holding the scrollbar at the right side of it and scroll. Scrollbar gets away from the Mouse pointer which requires us to go and grap the scrollbar again.

All Replies

  • Wednesday, June 13, 2012 12:37 PM
    Moderator
     
     

    Hi,

    Do you mean without a ScrollViewer, a grouped GridView’s scroll bar will not work correctly? It seems the issue cannot be reproduced on my side, it would be better if you can provide some repro code.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • Wednesday, June 13, 2012 1:01 PM
     
     

    Thank you for your help.

    steps to reproduce:

    1. Use http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/966aa897-1413-46f0-bef7-663de36f9423
    2. Replace ScrollViewer with Semantic Zoom
    3. Change the GridView's properties to -> Margin="0" Padding="100,0,60,0"

    Now, grab the scrollbar from it's right-most edge and try to scroll it to the end, you won't be able to.

  • Friday, June 15, 2012 7:07 AM
     
     

    any updates on this issue?

    if this is not a bug, would anyone please share the right way to present a semanticzoom control that has perfect scrollbars (not getting bigger or smaller while you scroll)

  • Monday, June 18, 2012 11:55 AM
    Moderator
     
     

    Hi,

    I downloaded the sample, and found it was designed for Consumer Preview, not Release Preview. When I fixed some break changes, and did the changes you pointed out. It worked fine, I could scroll to the end. I would like to suggest you to upgrade to Release Preview to see whether it helps.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • Monday, June 18, 2012 12:14 PM
     
     
    Thank you for your time, i am already on release preview. I'll prepare and send the project to you if it's ok for you. There might be a step that i didn't write about.
  • Tuesday, June 19, 2012 9:57 AM
    Moderator
     
     

    Hi,

    If it is needed, you can share your project via SkyDrive for us to further investigate.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • Tuesday, June 19, 2012 12:10 PM
     
     

    Thank you

    http://sdrv.ms/MCVG2U

    From this link, hold the scrollbar from it's right edge and try to scroll to the right most of the gridview.

  • Thursday, June 21, 2012 6:57 AM
    Moderator
     
     

    Hi,

    Okay. I see what you mean. Sometimes if you drag the scroll bar with the mouse, you can’t scroll it to the right of the screen. But you can still use the mouse wheel to reach the rightmost place. I will report this issue to see whether our product team can comment on this. As a workaround, please let the users use mouse wheel. In addition, please do not wrap the SemanticZoom inside a ScrollViewer. SemanticZoom itself implements scrolling, so wrapping a ScrollViewer may break its behavior.

    Best Regards,

    Ming Xu.


    Please mark the replies as answers if they help or unmark if not.
    If you have any feedback about my replies, please contact msdnmg@microsoft.com.
    Microsoft One Code Framework

  • Thursday, June 21, 2012 8:13 AM
     
     Answered

    Thank you, i alreay allow users to use mouse wheel in my app but i figured out that even "I" (as the developer) try to use scrollbars while normally using my app. I can already imagine the 1 star reviews in the Store just because of these scrollbars. So i'll really be soooo glad on any further comments on this topic.

    (I do not use ScrollViewer as you said, i've left it in the code to Show that if you replace semanticzoom xaml tag with a scrollviewer, it Works fine)

    Thank you!

  • Thursday, June 21, 2012 1:40 PM
     
     

    I have exactly the same issue. My XAML looks like the following:

    <SemanticZoom>

      <SemanticZoom.ZoomedInView>

        <GridView>

          ...

          <GridView.GroupStyle>...

        </GridView>

      </SemanticZoom.ZoomedInView>

    ...

    </SemanticZoom>

    I case I drop the grouping everythings works fine. I'm highly interested in a solution to this.

  • Saturday, September 08, 2012 11:34 PM
     
     

    Got this one as well...

    When adding margins to the last group in the semantic out gridview (since right padding is not working properly), you can touch-scroll to the end, use mouse wheel as well, but you cannot use the scrollbar - you can drag it to the end but when you leave the button it will elastic scroll by itself to the right edge of the last element in the gridview.

     
  • Thursday, October 25, 2012 11:14 AM
     
     
    Make sure you're not using VirtualizingStackPanel within your GridView. VirtualizingStackPanel will make scroll bar behave as you described as it is adjusting the scroll bar based on item count, and not by the actual width of content.
  • Tuesday, December 04, 2012 12:03 AM
     
     

    Hey, check this post: http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/40dc1387-13d4-4a10-8469-6f755088c7a5

    The solution to that post may help what you encountered.

  • Tuesday, December 04, 2012 6:28 AM
     
     

    Hey, check this post: http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/40dc1387-13d4-4a10-8469-6f755088c7a5

    The solution to that post may help what you encountered.

    Unfortunately, this is not the same problem. But this helped me solve another problem, thank you!