Hi!
We're using Ultimate UI 18.1 in our C# WPF application. We have a XamSpreadsheet, and we use following code to autofit the contents:
new SpreadsheetCommand(SpreadsheetCommandType.AutoFitColumnWidth).Execute(_grid);
This works perfectly, as does the double clicking between the column headers.
If we scale our display from Window's display settings, this autofit functionality breaks. It changes the widths, but they became too small, thus some on the cell contents are hidden.
Do you happen to know if this has been fixed in newer versions? Or is there some functionality somewhere in the library that we could use to solve this problem?
Best Regards,
-- Ville Mattila
Hello and thank you for contacting Infragistics. The spreadsheet doesn't support high dpi if that is what you are referring to. I suggest attaching a sample demonstrating the behavior.
I'm not sure what counts as high dpi, but I made the simplest demo I could think of and did some tests with different resolutions and scales.
As you can see, even with moderate resolutions the 125% scale breaks. I didn't use the AutoFitColumnWidth command here, just double clicked the column header borders.
EDIT: The demo app was restarted after each scale/resolution change.
Hello,
I tried to replicate this with a regular blank spreadsheet and I wasn't able to see any thing shown in your screenshots. Please provide detailed steps to reproduce without setting AutoFitColumnWidth but double clicking the column header borders.
DemoApp.zip
Please see the attached Visual Studio (I used 2022 but tried also with 2015) project with my sample code.
Update References to InfragisticsWPF4.v18.1.dll and InfragisticsWPF4.Controls.Grids.XamSpreadsheet.v18.1.dll where you have them locally.
At runtime it seems that also these files should be in bin folder:
I haven't reproduced any issues with your sample. I created a private case to have a meeting to discuss this further.
C-00231306For more details please visit:https://account.infragistics.com/support-cases
I've confirmed this has been resolved between 18.1 and our latest version. I suggest updating to 23.1 to resolve this issue.
Thank you for the update sir.