Add a details section to RadMessageBox, so that in mimics standard error messages.
To workaround this issue you should dispose the Instance property of RadMessageBox after each show of message box. For example: WORKAROUND: RadMessageBox.Show("Text"); RadMessageBox.Instance.Dispose(); If you are using themes, consider the following approach: RadMessageBox.SetThemeName("Windows7"); RadMessageBox.Show("This is some long text that sometimes does not wrap as it should."); var field = typeof(RadMessageBox).GetField("radMessageBoxForm", BindingFlags.NonPublic | BindingFlags.Static); field.SetValue(null, null);
When you set the FormBorderStyle property to FormBorderStyle.None, the form size defined initially is changed.
To reproduce: Add a RadForm and set its icon property. You will notice that the Form's icon is changed but it is not in the taskbar.
There should be an option to show a help button at the titlebar part of RadForm
To reproduce:
1. Create a new .NET 7 project and add a RadForm to it with a single control (e.g. RadButton).
2. Open the designer and have a look at the form's Size.
3. Move the button and save the changes
4. Close the designer and open it again.
Expected result: the RadForm's Size is unchanged
Actual result: the RadForm gets smaller, its height is reduced.
To reproduce: Change the monitors positions in the settings pane and try out on both monitors.
To reproduce: - Create a RadForm with a public label in it. - Inherit the new form and change the label text. - Open the second form at design time - the file status is changed to modified.
FIX. RadForm text flickers on change
To reproduce: - Create a new form. - Change the Localizable property to true. - Add a RadLabel to the form. - Select the label and change its name to "name with space" and press Enter. - VS editor will say that it is an invalid name and return the name to previous value. - Now look at designer.cs file of the form and you will see a lot of RootElement properties getting values form resource! Same issue can be reproduced by localizing a custom control: - Open UserControl.cs in Design mode. - On property editor, change property Language from "(Default)" to "Portuguese (Brazil)". - Now change a label text to "Nome". - See file EditUserControl.Designer.cs. It has many RootElement lines! Workaround: Delete the generated code and rebuild.
FIX. RadRibbonForm - setting the FormBorderStyle property does not take effect
When RadMessageBox has not owner and it is using in form that has TopMost = true throws exception after first call of RadMessageBox.Show() Steps to reproduce: 1.Create From with TopMost = true 2. Add button and insert the following code in press event: RadMessageBox.Show("Text"); 3.Run application and press the button two times. Workaround after each show of RadMessageBox add this code snippet: RadMessageBox.Instance.Dispose();
A possible workaround is to set the RadControl.EnableDpiScaling property to false. static class Program { /// <summary> /// The main entry point for the application. /// </summary> [STAThread] static void Main() { RadControl.EnableDpiScaling = false; Application.EnableVisualStyles(); Application.SetCompatibleTextRenderingDefault(false); Application.Run(new RadForm1()); } } Another workaround is to mark the application as DPI-aware: https://docs.telerik.com/devtools/winforms/telerik-presentation-framework/dpi-support
To reproduce: - Set the form MinimumSize to or close to the RadForm's actual size. - Turn all windows visual effects off - Set the theme to Office2010Silver - Start the application Workaround: - Load the theme manually in code like this: ThemeResolutionService.LoadPackageFile("C:\Office2010Silver.tssp") ThemeResolutionService.ApplicationThemeName = "Office2010Silver"
Default button focus is not correct and additional tab press is needed.
RadMessageBox throws ArgumentException - "A circular control reference has been made. A control cannot be owned by or parented to itself." when using with MDI forms. WorkAround: RadMessageBox.Show("Text"); RadMessageBox.Instance.Dispose();
Steps to reproduce: - add RadForm to the project - drop a RadRibbonBar to the project - when asked to use RadRibbonFormBehavior, confirm with Yes - check the form size (height) and close it - reopen it and the size is changed - repeating the last two steps continues to increase the form height Workaround: change the parent of the form having the ribbon form behavior public partial class RadForm1 : CustomRadForm { public RadForm1() { InitializeComponent(); } } public class CustomRadForm : Telerik.WinControls.UI.RadForm { public new FormControlBehavior FormBehavior { get { return (FormControlBehavior)typeof(RadFormControlBase) .GetField("formBehavior", BindingFlags.Instance | BindingFlags.NonPublic) .GetValue(this); } set { this.ResetFormBehavior(false); if (value != null) { Size clientSize = this.ClientSize; typeof(RadFormControlBase) .GetField("formBehavior", BindingFlags.Instance | BindingFlags.NonPublic) .SetValue(this, value); typeof(RadFormControlBase) .GetMethod("PrepareBehavior", BindingFlags.Instance | BindingFlags.NonPublic) .Invoke(this, new object[] { }); this.RecreateHandle(); this.ClientSize = clientSize; } } } }
To reproduce: Add a RadRibbonBar, associate AcceptButton and CancelButton and subscribe to their events. Run the application press escape and the CancelButton's event should be fired. Press enter - no results. Workaround: protected override bool ProcessCmdKey(ref System.Windows.Forms.Message msg, System.Windows.Forms.Keys keyData) { if (keyData == System.Windows.Forms.Keys.Enter) { this.AcceptButton.PerformClick(); } return base.ProcessCmdKey(ref msg, keyData); } Resolution: The issue is fixed in Telerik`s RadForm and RadRibbonForm. If you use MS Form, this is still not working.
If you have a RadForm that contains a RadTextBox (TextBox), set the WindowsState of this form to Maximized and add this form to an MDI Parent with RadDock which handles the forms, you will notived that you are not able to mouse select the text.
To reproduce: - Create new project. - Make the default form to inherit RadForm. - Start the application and maximize the form. - You will notice that a few pixels are displayed on the right monitor as well. Workaround: var screen = System.Windows.Forms.Screen.PrimaryScreen.Bounds; this.MaximumSize = new Size(screen.Width, screen.Height); Second Workaround: public Form1() { InitializeComponent(); this.SizeChanged += Form1_SizeChanged; } private void Form1_SizeChanged(object sender, EventArgs e) { if (this.WindowState == FormWindowState.Maximized) { this.Region = null; } }