To reproduce:
- Open The popup
- Click on it, and then click on the form
- Repeat until the popup stays opened
In the image below you can notice lines that disappear, identical lines but rendered more or less thick.
Using Telerik button and dropdown beside and anchored to a standard label or textbox then, when run app in a Win 11 in Korean, the presentation is not correct.
Expected result:
Observed result:
To reproduce: - Drag RadDropDownList control on a form, expand its DropDownListElement property, and change the ItemHeight - Another case is, on a RadForm, expand FormElement>TitleBarElement and set its Visibility to Collapsed Workaround: set the desired property at runtime radDropDownList1.DropDownListElement.ItemHeight = 22;
Steps to reproduce: 1. Drag a grid on the form 2. Drag one or more controls over the grid - at this point in the Document Outline you can see the dragged control is a child of the grid 3. Open the Property Builder of the grid and close it - at this point the dragged control disappears Workaround: 1. Open the Designer.cs file, and locate the line, where the control is added to the grid e.g. this.radGridView2.Controls.Add(this.radButton4); and change it to: this.Controls.Add(this.radButton4); If need be, set the Location property of the control at design time, to position it at the desired place. 2. Alternatively, you can place the control outside the grid bounds and after selecting it, use the arrow keys to position is over the grid. This will not make it its child, hence the issue will not appear.
I'm trying to initialize RadControlSpyForm in a .NET 2.0 application and it throws the following exception:
System.InvalidCastException: 'Unable to cast object of type 'System.Windows.Forms.SplitContainer' to type 'System.ComponentModel.ISupportInitialize'.
I did some research, and I found that since SplitContainer doesn't inherit from System.ComponentModel.ISupportInitialize until .NET 4.0, this message shows up in solutions where a project is downgraded from .NET 4.0, but the Form designer isn't regenerated to remove the SplitContainer cast to ISupportInitialize to call BeginInit() and EndInit().
To replicate the missing button when the application is run on my main monitor with 150% DPI scaling:
If the RadControl.EnableRadAutoScale property is set to false in the Program.cs file, the button is placed as expected:
When I replace the form to inherit from RadForm, not the MS Form, the button is clipped:
The writing-mode attribute is ignored when rendering RadSvgImage.
Here is a sample SVG:
<svg width="200" height="200" viewBox="0 0 200 200" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
<g>
<text style="font-size:20px;writing-mode:tb;" x="30" y="30">
Vertical text
</text>
<text style="font-size:20px;writing-mode:vertical-lr;" x="50" y="50">
Text 2
</text>
</g>
</svg>
When a RadValidationRule has the "PropertyName" assigned to a non-existent property, the RadVAlidationProvider.ValidateCore throws a NullReference exception because the property cannot be found via reflection and throws no error handling.
From OpenEdge ABL class, this is the code written into the forms InitializeComponent method. The "IsValid" property doesn't actually exist.
radValidationRule3:AddControl(THIS-OBJECT:myTextBox). radValidationRule3:Operator = Telerik.WinControls.Data.FilterOperator:IsNotEqualTo. radValidationRule3:PropertyName = "IsValid". radValidationRule3:ToolTipText = "Test". radValidationRule3:Value = TRUE.
While we don't expect the functionality to actually work because the property isn't actually available to .NET, but the NullReferenceException is poorly handled.
I've attached a screenshot of the bit of code from RadValidationProvider.ValidateCore where this occurs. This is from version 2020.3.1020.20
Here is the thrown stack exception details from visual studio.
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=Telerik.WinControls.UI
StackTrace:
at Telerik.WinControls.UI.RadValidationProvider.ValidateCore(Object sender, EventArgs e)
This
The annotation line is supposed to be at 05 point but instead it is between 05 and 06.
In the exported PDF document, the font size of the header and footer is smaller than the font of the data cells, even though the specified font is the same size.
To reproduce set the same font to the header and data cells:
pdfExport.HeaderFont.Font = new Font("Segoe UI", 10f);
private void PdfExport_CellFormatting(object sender, PdfExportCellFormattingEventArgs e)
{
e.CellElement.Font = new Font("Segoe UI", 10f);
}