In this case, the RadGridView AutoSizeRows and ColumnGroupViewDefinition are enabled. The rows will have different heights depending on the cell content. When exporting the RadGridView to PDF, the rows will have equal size and won't respect the current size in the view. Thus longer text in a cell will be cut off.
The same behavior is observed when exporting to PDF or XLSX. In addition, this is also observed when printing the RadGridView.
When using the AnchorStyles property, the editor does not update the anchors as expected:
The default MS ContextMenuStrip shows tooltips for disabled menu items:
Currently, RadPdfViewer offers the DataError event which is purposed to handle errors during the import process. However, if there are problematic pages that are rendered in the viewer at a later moment after the document is already imported, the viewer doesn't offer a suitable way for handling such problematic moments even though the PdfProcessing library throws one of its exceptions.
The exact client's case is loading a PDF document which contains images requiring JPX Decoder which is currently not supported. Even though the PdfProcessing library throws internally the following error, the RadPdfViewer control doesn't throw the DataError event with the respective error:
Telerik.Windows.Documents.Fixed.Exceptions.NotSupportedFilterException: 'JPXDecode is not supported.'
Hi Team,
I would like to request to add a Today button to the RadDateTimePicker so when the user clicks on it, the value of the RadDateTimePicker will be set to the current day/time.
Thank you!
In this scenario, the reported behavior is observed in NET 8. The same behavior is not reproducible in .Net Framework 4.8. When the map is zoomed max out and we try to pan the view, missing tiles appear and the performance is very slow. Additionally, in the output tab of VS, we can observe some exceptions:
List Style is not rendered correctly.
Case 1:
Case 2:
Case 3:
When I use the new project wizard provided by Microsoft for a new windows forms project it lets me select the target .net version
When I do the same with the Telerik wizard, it does not let me choose what .net Version I'm targeting and does not generate the optimal code for the target version. For example when I target .net 9.0 with high dpi support, it should generate API calls for High DPI, not an entry in the app manifest. IMHO the generated code should be as close to the Microsoft Standard for the targeted .net version as possible.
Incorrect or missing accessible object names in the Inspect.exe tool (MSAA).