USERCONTROL AUTOSCALEMODE INHERIT FONT CODE
Just getting the DataGridView to do multi-line in the first place.Įxample code is below. Solve this particular issue, the relevant ones appear to be related to I've googled various terms, and the best items I can come up with don't That someone here must have run into this before and already solved it. I could probably make another usercontrol justįor that cell and just add a scrollbar on it as necessary, but I figured I tried using a DataGridViewTextBoxCell, but it apparently has no On a fixed SplitContainer below other form elements that need to remain There are several places where my userControl is in use Not a problem, they can just resize right? Well, ideally yes, but It impossible to see what is in the entire field. The scrollbar appears stuck on the top of the cell, and makes Into is in how the DataGridView opts to scroll when a cell is being Simple enough, and it's been working fine mostly. UserControl that takes care of displaying and formatting the comments. Itĭoesn't matter what the item is, it could be a blog entry, a widget, orĪ document, I wanted to simplify things by having one generic NET 2.0, I have a WinForms application thatīasically just allows a user to review comments on a particular item. (new day, another problem with DataGridView display. listViewItem2 = new ("A list view control")
USERCONTROL AUTOSCALEMODE INHERIT FONT WINDOWS
#region Windows Forms Designer generated code Protected override void Dispose(bool disposing) As requested: the source code of Form1.cs Changing between 96 and 120 dpi normally needs a reboot under Win XP, otherwise you don't see what really happens. I am looking for a solution that avoids a complete redesign all those dialogs.ĮDIT3: To test this behaviour, IMHO it is a good idea to set up a virtual Windows XP environment with 120 dpi while the development environment resides under 96 dpi (at least, that's what I did). You can imagine that most of our dialogs now look very bad under 120 dpi. Last week, we detected this strange scaling behaviour under WinForms when switching to 120 dpi. Under the old framework, scaling to 120 dpi worked fine - all fixed size controls scaled equal in both dimensions. All of them look fine with 96 dpi using a 9.25pt font. They were migrated from an older C++ GUI framework to C#/Winforms, that's why they are all fixed-size. The problem is not specific to the "Tahoma" Font, it occurs also with Microsoft Sans Serif, 9.25pt.ĮDIT2: Some additional information about my intention: I have about 50 already working fixed size dialogs with several hundreds of properly placed, fixed size controls.
Using AutoScaleMode = Font (with adequate AutoScaleDimensions, of course) either does not scale at all or scales exactly like seen above, depending on when the Font is set (before or after the change of AutoScaleMode). Using the default font (Microsoft Sans Serif 8.25pt), this problem does not occur. I would like to keep it this way, if possible.
NET framework?ĮDIT: some hints: the Font change is only applied to the containing form, the controls inherit their font from the form. Under 120 dpi, Windows XP, the the Windows Forms autoscaling feature produces this 120 dpi example:Īs you can see, groupboxes, buttons, list or tree views are scaled correctly, multiline text boxes get too big in the vertical axis, and a fixed size label does not scale correctly in both vertical and horizontal direction. Under 96dpi, Windows XP, the form looks correctly like this 96 dpi example: This.AutoScaleDimensions = new (96F, 96F) I boiled it down to a simple test application (WinForms 2.0) with only one form, some fixed size controls and the following properties: class Form1 : Form I have some problems with the Form.AutoScaleMode property together with fixed size controls, when using a non-default font.
0 kommentar(er)
