Unplanned
Last Updated: 12 Mar 2024 14:27 by bernox
Opening and closing the designer force the RadForm to change its width/height with .NET 8
Unplanned
Last Updated: 29 Feb 2024 10:07 by ADMIN
Unplanned
Last Updated: 16 Feb 2024 09:24 by ADMIN
Good morning,

when I open a mdi child form from another child form and change WindowState from Minimize to Normal the form is not shown with correct size.
Unplanned
Last Updated: 09 Aug 2023 10:41 by ADMIN
The controls inside the form are not scaled correctly when the Form is shown on a monitor with DPI higher than 150%. An important step here is that the main monitor where the form is shown has a higher DPI. Moving the form from a monitor with 100% to a monitor with a higher DPI will not reproduce this behavior.
Unplanned
Last Updated: 24 Mar 2023 14:12 by ADMIN
Changing the font size runtime, will not trigger the control to re-measure correctly.
Unplanned
Last Updated: 16 Feb 2023 11:08 by ADMIN
Create a new project with an anchored control in all corners. You can simply do the test, insert a scheduler or gridview, snap on all corners, set WindowsState to maximized and start the program with a DPI of even 125%, and see the problem right away. Tested with new projects both in Net Framework and .Net. I also tried creating a new instance of Winforms and setting the Windowstate from there by code, but the problem remains.
Unplanned
Last Updated: 08 Feb 2023 15:39 by ADMIN
In Net 7 projects, resizing RadForm will serialize the AutoScaleBaseSize property which is deprecated with the latest versions. 
Unplanned
Last Updated: 15 Jul 2022 11:54 by Toby
I have an issue such that when I place my application (which is based on a RadRibbonForm) on to my right hand 4K monitor and then maximise it I get a small amount of "bleed" of my application on to the right hand side of my left monitor.

On inspecting the forms desktop bounds property it see X = 1908, Y = -12, width = 3864, height = 2114. I was expecting X = 1920, Y = 0, width = 3840, height = 2090 which is what is being reported in Screen.AllScreens.

I'm using the latest version of WinForms and have done what is suggested in this link.

I can reproduce the same behaviour when I run "Demo Application - Telerik UI for WinForms R2 2022 SP1", move it to my large right hand monitor then maximise it.

Kind regards
Toby
Unplanned
Last Updated: 21 Jun 2022 05:43 by Jean-Pierre

VS 2022, Telerik 2022.2.510, NET 6.0 (sample app is attached)

1. Creating sample Telerik WinForms App.
2. Add a RadTextBox
3. Load Event with code
radTextBox1.Text = this.Size.ToString();

4. Run the App
5. Close the App
6. Move the RadTextBox Control at design time.
In design, the height of the form is 2 pixels taller.
Run these steps in a loop. After a few hours of work, the form exceeds the size of the screen.

Unplanned
Last Updated: 12 Oct 2021 07:33 by ADMIN
1. Create a new Form that inherits from RadForm and add some rad controls.
2. Checkin the file in your source control system
3. Open the form in design time will cause checkout
Unplanned
Last Updated: 21 May 2020 07:48 by ADMIN

Hi,

I am working on making our Winforms UI projects DPI aware to clean up fuzzy text in Windows 10.

I'm having an odd issue with some layouts. In one example, we have a simple form dialog that will grow with a label inside (similar to a windows message box). THe label is autosizing itself and has a minimum and maximum size set. This dialog is working fine without the DPI awareness, however, after enabling, the RadForm resizes to some strange size. I tried to investigate and it seems that the label is resizing to some large size and not respecting it's maximums (though this doesn't show when rendering as I've switched off the borders).

The label is resizing the form via anchors. I think probably there is a better way at layout here, but I'm wondering if the wild resizing may be considered a bug.

See images below.

I've also attached a project that reproduces this issue.

 

 

Unplanned
Last Updated: 02 Apr 2020 09:18 by ADMIN
Created by: Stoyan
Comments: 1
Category: Form
Type: Bug Report
1

Dear support,

i have a RadForm and custom theme.

To reproduce the problem:

1. Configure 2. montior to have 200% Scale (Monitor2).

2. Start the solution on your main Monitor1 (with 100% Scale)

3. Click on button "radbutton1".

4. Move the shown RadForm1 from Monitor1 to Monitor2 and release it. The form will scale automatically.

5. Now move the RadForm1 back to the main Monitor1

Now you can see the effect from Form.png.

What is causing it and how to remove it?

The problem has some connection with the Anchor options from radButton1 and radButton2.

If i set them to "Top, Left", then the effect does not appear, but this way i have to set their location manually, or is there other option?

 

Regards,

Stoyan

 

Unplanned
Last Updated: 24 Mar 2020 15:05 by ADMIN
The issue is that our system will not be fully maximized when using it on Windows 7, while on our PCs here (windows 10), it's fine.
Unplanned
Last Updated: 16 May 2019 05:12 by ADMIN
ADMIN
Created by: Dess | Tech Support Engineer, Principal
Comments: 1
Category: Form
Type: Bug Report
0
To reproduce: Add a RadForm and at design time in the Properties section of Visual Studio try to customize some properties of the RadForm >> FormElement >> TitleBar, e.g. Padding, ForeColor. You will notice that even though you save the changes, they are not serialized. Thus, when you run the application, none of the changes are applied.

Workaround: set the changes programmatically at run time.
Unplanned
Last Updated: 06 Dec 2018 07:15 by ADMIN
To reproduce:
- Set the StartPosition to CenterScreen
- Show the form on a HDPI monitor

Workaround:
var form = new RadForm();

float dpiX, dpiY;
Graphics graphics = this.CreateGraphics();
dpiX = graphics.DpiX /100;
dpiY = graphics.DpiY /100;

form.StartPosition = FormStartPosition.Manual;
var monSize = Screen.FromControl(this).Bounds;
var centerX = (monSize.Width / 2) - (form.DesktopBounds.Width * dpiX / 2);
var centerY = (monSize.Height / 2) - (form.DesktopBounds.Height * dpiY/ 2);
form.Location = new Point((int)centerX,(int) centerY);
form.Show();


Unplanned
Last Updated: 11 Sep 2018 11:50 by ADMIN
To reproduce: run the sample project. It ends up leaving significant blank space on the right and the bottom, whereas the normal MS Form does NOT do this and works right.

Workaround: in the Load event you can adjust the size with 10/15 px by setting the MaximumSize:

        private void Form1_Load(object sender, EventArgs e)
        {
            this.MaximumSize = new Size(this.Size.Width - 15, this.Size.Height - 10);
        }
Unplanned
Last Updated: 16 Jul 2018 11:16 by ADMIN
How to reproduce: add a RadRibbonForm and set its MaximizeBox, MinimizeBox properties to false. Set the HelpButton property of the form to true and change its Icon. You will notice that the designer in Visual Studio has not updated.

Workaround: use the element hierarchy editor and manually change the visibility of the elements.
Unplanned
Last Updated: 26 Feb 2018 16:24 by ADMIN
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);
    }
}
Unplanned
Last Updated: 27 Dec 2017 06:25 by ADMIN
To reproduce:

public partial class RadRibbonForm1 : Telerik.WinControls.UI.RadRibbonForm
    {
        public RadRibbonForm1()
        {
            InitializeComponent();
            this.AllowAero = true;
            this.RibbonBar.QuickAccessToolbarBelowRibbon = false;
        }
    }

Note: the system buttons not always handle the mouse click.

Workaround: set AllowAero to false OR RibbonBar.QuickAccessToolbarBelowRibbon to true.
1 2 3