Does anyone know about a problem with XamMultiColumnComboEditor on Windows 2012 R2 where the number of items visible in the dropdown (popup) may cause the entire popup window to bounce up and down on the screen? I'm using a recent service release of 2016.1 WPF and I'm having a difficult time figuring this out. I have to make the max height of my popup lists unnaturally small/short to avoid the problem. Making the max height of the popup small generates a vertical scrollbar and makes the control "happy".
Basically if the list of combo items is long enough to generate a vertical scrollbar in the popup then there is *never* a problem.
But if the list of available items is few, and the vertical scrollbar goes away, then the entire combo starts hopping up and down. It doesn't happen for me on Windows 10 but when it is deployed to Windows 2012 R2 it behaves in this wierd way. Additionally if you start typing and the incremental search (while typing) limits the results to a subset that is smaller than the vertical size of the popup window then that makes the "bouncing" problem happen too.
This may have been fixed. I upgraded my Office2010Blue theme XAML files to match our active version of IG WPF (2016.1):
These are the specific files I did first, and after that I have had less trouble with the XamMultiColumnComboEditor.
I took the *new* copies of these (from Program Files (x86)\Infragistics\2016.1\WPF\Themes\Office2010Blue ) and after copying them into the solution, I reapplied some minor customizations.
As a side, are there guidelines for when I should review my theme files in order to pull in potential bug fixes? Should I be doing this with every service release, or just major version changes?
Also, is it a poor practice to make customizations to these XAML files? Is there a better approach? Sorry for the questions. Would like to avoid getting burned again....
Hello,
Can you please provide a sample application or at least some screenshots so that I get an idea what the problem is. I need as much details as possible (XAML snippet, etc..) so that I can reproduce the problem and therefore our developers can come with a decision whether it can be fixed.
Regards,
Stefana