Scrolling issues in WPF DataGrid after upgrade from 2015.3 to 2017

Scrolling issues in WPF DataGrid after upgrade from 2015.3 to 2017

Posted by: attodorov on 17 December 2019, 8:31 pm EST

• 

  attodorov

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 17 December 2019, 8:31 pm EST

  Hello,

  We’ve been using the C1 WPF DataGrid (version 2015.3) in a major product for many years without any significant issues. The grid is complex, sometimes has multiple rows per cell and text can wrap on multiple lines - which makes row height variable. After upgrading to 2017.3 we are seeing significant issues with scrolling, which has already caused our clients major issues and requires a downgrade to 2015.3, therefore we need to ship a new hotfix build to them and require them to reinstall the product on all their workstations. The issue can be described by observing a jumping scrollbar, choppy scrolling, general slow (not snappy) scrolling, which sometimes makes the grid totally unusable. Here is a more specific observation:

  1. Scroll to the bottom of a grid which has variable row heights due to word wrapping (and multiple lines per cell, but we do believe this simply has to do with just variable row heights)
  2. start scrolling up
  3. Scrollbar constantly jumps to the bottom. if you scroll with scrollbar arrows it can’t even go to the top. You can see how the scrollbar rectangle starts growing and then at some point it becomes smaller and a jump follows.
  4. The bigger the difference between row heights, the worse the issue and the easier to see it - it really becomes more obvious. If rows are relatively similar height, scrolling is OK (doesn’t jump), but is still nowhere near as smooth as with the 2015.v3 version of the grid

  My question is - Are you aware of anything specific, which has caused this behavior and is there any new property /configuration which can revert the old behavior without forcing us to downgrade the C1 components?

  Thank you

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 17 December 2019, 10:04 pm EST

  Hello,

  I tried to check our change logs but could not find an exact problem that matches your issue. Therefore, to help us assist you better can you share a stripped down application that demonstrates the issue?
  
  Moreover, I would suggest you to try running the application using the latest ComponentOne version. You can upgrade to the latest version using C1Live.
  
  (If however, you do not have a valid license for the latest (2019v3) version, you can download the assemblies from the following URL, clear your project’s licenses file and manually refer the downloaded assemblies. This would give us a clarity whether the problematic behavior is still present or has already been resolved in an interim build.
  
  Download latest version: https://prerelease.componentone.com/dotnet40/c1wpflibrary/2019-t3/C1WPFBasicLibrary.4_4.0.20193.685.zip

  Regards,
  
  Ruchir

• 

  attodorov

  • Post Options:
  • Link
    Copy

  Posted 17 December 2019, 10:07 pm EST

  We’ve also noticed that with the 2017 version there are lots of binding errors in the Debug output in visual studio (when ran from VS ) - they are related to ItemsControl and VerticalAlignment. Those are not present in 2015.3.

  Here is one example:

  System.Windows.Data Error: 4 : Cannot find source for binding with reference ‘RelativeSource FindAncestor, AncestorType=‘System.Windows.Controls.ItemsControl’, AncestorLevel=‘1’’. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is ‘ListBoxItem’ (Name=‘’); target property is ‘VerticalContentAlignment’ (type ‘VerticalAlignment’)

  Thanks

• 

  attodorov

  • Post Options:
  • Link
    Copy

  Posted 18 December 2019, 7:44 am EST

  Hi Ruchir,

  I’ve made a simple app which demonstrates the issue. Just scroll to the bottom and then start scrolling slowly up (by clicking on the scrollbar arrows, for example , or by slowly dragging it up). You’ll see you will never be able to scroll up and that the scrollbar constantly jumps down. The issue seems to be obvious and is very important to resolve for our customers because it directly impacts their daily workflows.

  Thanks.

  WpfApp1.zip

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 18 December 2019, 5:12 pm EST - Updated 4 October 2022, 12:00 am EST

  Thank you for creating a demo application.
  
  However, the scrolling works properly at our end with 2019v3 version as well as with 2017v3 version. Please see attached videos.
  
  So, is the issue occurring over some specific environments, can you share the environment details of machines where the issue is occurring?I ran the application in Win10 + VS19 environment.

  Thanks & Regards,
  
  Ruchir
  
  

• 

  attodorov

  • Post Options:
  • Link
    Copy

  Posted 18 December 2019, 8:02 pm EST

  Hi Ruchir,

  No, there isn’t anything specific in the environment. I use Win10 and VS17, .NET framework version is specified the zip file (project files) , so we should be using the same. I can confirm the scenario works fine with your latest DLLs, but it does not work as expected with 2017.3. So we either have to downgrade or upgrade. Downgrading is the safest because that version has already been used in the product and there is much less risk of regressions. I can see in your videos that you aren’t following precisely the steps to reproduce I gave :

  1. Scroll to the bottom
  2. use the scrollbar arrow icons to start scrolling up . you can also use the mouse wheel.

  At this point we do not require any further assistance - looks like there was a bug in 2017 which was fixed later, we were wondering whether there is a way to fix this by some setting without requiring a downgrade / upgrade. Also, it would have been good to know what exactly caused the issue.

  Thank you

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 19 December 2019, 7:30 pm EST

  Hello,

  I did scroll to the bottom (with mouse wheel, scroollbar arrows and dragging scrollbar) but for us, the issue was not observed even with the 2017v3 version.
  
  Since we are cannot observe the issue at our end, we are unable to share a workaround for the same.

  Though, its always recommended to upgrade to the latest version only (because of enhancements, performance improvements and general bug fixes) but since you have had already used the older version assemblies in your project and observing no issues with it, you can move back to the 2015v3 version.

  Kind Regards,
  
  Ruchir