Hi,
There seems an issue with the horizontal scrollbar for xamGrid. From an initial state where no horizontal scrollbar is shown, and then the grid is shrunk, the scrollbar appears as expected. However, when the grid is changed back to its previous size the scrollbar is not removed, just disabled. It takes any other change on the grid (e.g. sorting or stretching a column for the scrollbar to finally be removed. I’m guessing this is related to this issue...http://blogs.infragistics.com/forums/p/64258/325443.aspx#325443, where there doesn’t seem to have been a response.
This can be easily reproduced using your own xamFeatureBrowser application shipped with NetAdvantage 11.2. Open the app and maximise it. Go to the ‘xamGrid -> Hierarchical Financial Data’ and there should be no vertical scrollbar (I’m using 1920 by 1080 resolution) on the example grid. Then restore/resize the app so that the vertical scrollbar appears. Then maximise the app again. The vertical scrollbar incorrectly remains. Click on a column header and the scrollbar is finally removed.
Is there a workaround to resolve this before you address the problem?
Hello Matt,
I have been looking through your post and I tried to reproduce the issue on the monitors with different resolution, including 1920 by 1080, using our sample browser still on my side everything looks as expected. Would you please provide me with some additional details about your operating system and a video where the issue is reproducible so I can continue investigating this issue.
Thanks in advance.
Hi Elena,
I produced a video to illustrate the issue, but have wasted too much time trying to get it below the 200k limit for attached files on your forum. Could you please give me an email address that I send it to.
Hello Elena,
Has this issue been resolved? It happens in our product as well.
Hello AntonK,
This issue has been fixed internally and we expect it to be included in our next service release. For additional reference when you could expect this release to be available for public download you can take a look at our release schedule from the following link:
http://es.infragistics.com/help/service-releases/
Please note that while these projected dates are believed to be good estimates, it is possible that a service release will be made available before or after this date. We will update this calendar for you accordingly.
Hello,
The service release containing the fix for your issue is out, you can download it from: https://es.infragistics.com/my-account/keys-and-downloads/
I'd be glad to receive a feedback on the outcome.
I am experiencing the issue too in wpf xamGrid and the build version I am currently working is 12.1.20121.1010. The mentioned URL has certain releases however after August 2012 there are only 2 which are for ASP.NET and Winform.
Can you please confirm if the issue has been addressed for WPF too? If so, from where we can download the fix.
Thanks,
Hello Narendra Singh,
Thank you for posting in the Infragistics Community.
I have verified that this issue is being fixed in the version 12.1.20121.2169 and up. The latest one available is currenly 12.1.20121.2225. In order to download and test it, you could go to your account, click on the corresponding 12.1 product key, and choose the "Service Releases" below the keys, and there you could download the latest available one for you.
Please feel free to let us know if you have any other questions with this matter.
Hello Daniil,
Thank you for posting the workaround to this issue. I believe it may help others who are having a similar issue.
I have tested this scenario against the latest versions of Infragistics WPF 17.1 and 17.2, and it appears that this issue has been fixed as I am no longer able to reproduce this behavior. Unfortunately, it does not appear that this fix made it into the latest 16.2 build, which was the last, and so you may need to either continue using the workaround, or upgrade to the latest versions of 17.1 / 17.2.
Please let me know if you have any other questions or concerns on this matter.
I have verified that this issue is still present in 16.2.20162.2109, and therefore suggest you to test later releases as well.
For those who have stumbled across this as well, the workaround suggested in this thread doesn't work, so you will need to modify the template and wrap your ScrollBar into some containing element, i.e. Border, and when you have references to both ScrollBar and that element, you would subscribe to ScrollBar's IsEnabledChanged and set the parent's Visibility based on NewValue:
var border = scrollBar.Parent as Border;scrollBar.IsEnabledChanged += (s, e) =>{ border.Visibility = (bool)e.NewValue ? Visibility.Visible : Visibility.Collapsed;};