In the following scenario, we have enabled the pager functionality of the control. If we move to a different page and then set the DataSource to Null, the page index will not be reset.
//set SmallTickHeight
this.radTrackBar1.TrackBarElement.BodyElement.ScaleContainerElement.TopScaleElement.TickContainerElement.SmallTickHeight = 10;
When the RadPropertyGrid is in group scenario and we expand more property items, the scroll value is incorrect.
Hello team!
I've found a misbehavior on RadForm when setting the size.
When you set the Size of the Form before it actually has shown then it will do some re-calculation, change the form size several times, and ending up in a too big size. The behavior is different to a original Form and that's why I'd treat this as bug.
The first screenshot shows a RadForm that set itself to ClientSize = 500; 500 on the constructor, like usual. It ends up in a size slightly bigger then defined.
This second screenshot shows a RadForm that set itself to ClientSize on "Shown". It ends up in having the correct size.
Whenever you set a breakpoint to the method "Form1_Resize" you can capture that the first time the Size of the RadForm get changed is our "ClientSize = new Size(500, 500)". Then the Size get changed two times by RadForm itself to something slightly smaller. Lastly the Size get changed by RadForm another time, but this time slightly bigger
This behaviors can lead to inconsistent UI size, e. .g small spaces when using AutoSize = true in certain cases. But yet didn't figured completely out when exactly it happens, just that it comes from this slightly increased Size of RadForm.
Can you please take a look to it and, if it is one, report it as bug?
Thank you very much!
Regards,
Pascal
How to reproduce: set the Size property of the form in the designer of Visual Studio, pay attention to the serialized ClientSize value. Run the form and check the ClientSize, it has increased Workaround: public partial class Form2 : RadForm { public Form2() { InitializeComponent(); Padding p = TelerikDpiHelper.ScalePadding(this.FormBehavior.ClientMargin, new SizeF(1f / this.RootElement.DpiScaleFactor.Width, 1f / this.RootElement.DpiScaleFactor.Height)); this.MaximumSize = new Size(this.Size.Width - p.Horizontal, this.Size.Height - p.Vertical- this.FormBehavior.ClientMargin.Bottom + this.FormElement.TitleBar.Size.Height); } protected override void OnShown(EventArgs e) { base.OnShown(e); this.MaximumSize = new Size(0, 0); } }
When trying to open the QuickStart solution from
C:\Program Files (x86)\Progress\Telerik UI for WinForms 2025 Q1\Examples
installation folder, the following error appears:
Workaround: set UseCompatibleTextRendering to true.
Visual Studio 2022 crashes when working with a solution containing two WinForms projects:
Steps to Reproduce:
Expected Result:
Visual Studio should smoothly switch between code and designer views without issues.
Actual Result:
Visual Studio freezes and crashes after switching back to the WinForms designer in Project 2.
Environment:
Additional Notes:
Use attached to reproduce. Workaround: - Use RadForm it explicitly handles the controls scaling. - Make sure that the following of the user controls are set like this: this.AutoScaleDimensions = new System.Drawing.SizeF(96F, 96F); this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Dpi;