We are using the RadRichTextbox limiting the width size and configured to wrap the text, automatically increasing its height as needed. While this functionality works correctly for most text, it fails in cases where a line ends with spaces. These trailing spaces extend beyond the control's visible boundaries, making them invisible on-screen, yet they remain present in the RadDocument.
To reproduce: Create a RadRichTextbox with limited width and auto adjusted height. Type in underlined text on first line and add a lot of spaces that go behind the visible width. Type in more text to see the visible underlined text go to the next line (while hiding the added underlined spaces of the previous line). Exporting to RadDocument shows the extra underlined spaces that RadRichTextbox does not.
Hi,
I would like to report that Z-index have unexpected values when RadDiagramContainerShape are used.
Please watch video first, my remarks points to the video attached to the ticket.
1. Currently there is a possibility that Container A can be hidden by Container B and this is fine.(~11sec of movie)
2. However then i will add Container C to Container A and then drag Container B to overlaps Container A it overlaps only Container A and does not overlaps Container C which for end-user could be very confusing, why Container C is visible at that time.(~20-30 sec of movie)
The problem gets more complicated when i drop Container B to overlaps Container A but without adding Container B as a child of Container A.
In that way it looks that children of Container A are children of Container B
3. When i will add new container "Header" to Container B and then overlaps Container A and Container C then its even more mixed up(~ 30-50 sec of movie)
4. When i will add new container "Header" to Container A and Z-index are somehow refreshed and then in magic way Container_C now overlaps "Header" container from Container B(~58sec of movie)
I would expect:
Fix calculation of Z-index in that way if Container B overlaps Container A it means it overlaps as well it's children. Currently you have flat hierarchy of VMI containers which leads to such Z-index issues.
OR
Expose possibility to override your internal methods which calculates the Z-index.
Hi,
I would like to report that automatic generate of connection point for Bezier connection is wrongly generated when link is attached to Gliding Connector.
Connection point is generated at the position where link is attached to shape. I think for such use-case you should generate connection point taking into account angle of link in relate to shape and generate connection point a bit moved. When connection point is generated at attach position it makes that the "arrow" of link have wrong angle.
I'm attaching video and your sample solution with my modifications to easier reproduction.
Best regards,
BH
If a formula contains a named range as an argument, its value may not get updated properly in the following scenario:
In the formula: =SUMIF(A1:A4, 3, ColumnC), ColumnC is a named range refering to C1:C4. Range A1:A4 contains the values 3, 2, 2, 3, which will avoid a circular reference. The formula is entered twice, in C2 and C3. Note that these cells are part of the range ColumnC refers to. When you refresh the formula in C3 (enter edit mode, then press enter), it will calculate correctly, but the formula in C2 will be recalculated to an error. If you refresh the formula in C2, the formula in C3 will be evaluated to an error.
I use RadWindow as the main window for my application (primarily because I want to embed a menu in the title bar). This works well except our users have reported a bug where they are unable to use hotkeys following activating the application from the TaskBar.
A typical scenario:
* minimise the application using the minimise button
* some time later, activate the app by clicking on the TaskBar icon
* Press CTRL+N hotkey combination which should execute a command
I have created a sample application that shows two windows: a regular Window and a RadWindow. They both contain input bindings for the Ctrl+N combination. When the regular window is activated from the taskbar, the input bindings work, but when the same sequence of events is performed on the RadWindow the input bindings do not work. Clicking between the windows does work - it seems the problem is only related to application activation.
On a related note, both windows contain a TextBox control. If text is highlighted in the regular window, the highlighted text is maintained and redisplayed when the window is activated. This does not work for the RadWindow. As it relates to keyboard focus, I wonder if the problem is related.
Can be reproduced in the WPF demo (Windows8 theme): the error description tooltip appears on the left of the control and with the red arrow on the left (see attachment). The tooltip should appear on the same side of the red adorned element (the red triangle, top right corner) and the tooltip arrow should point the control.
In Windows 11, when mouse over top level window title bar maximize box, there should be snap layout drop down, but for any child window there should not be snap layout drop down.
I've tested the following 4 cases and all of them works fine
1. win32 project
2. MFC project
3. general Winform project
4. general WPF project.
but for Telerik WPF project which use RadRibbonWindow as main window, the behavior is wrong. as attached video shows
Exception when editing the template and showing the tooltip of the ValidationErrorElement
Workaround:
Replace the validation element:
<Grid x:Name="ValidationErrorElement" Visibility="Collapsed"><Grid.ToolTip>
<ToolTip x:Name="PART_ToolTip" Placement="Right" DataContext="{Binding RelativeSource={RelativeSource TemplatedParent}}">
<ToolTip.Template>
<ControlTemplate TargetType="{x:Type ToolTip}">
<Grid x:Name="RootVisual" HorizontalAlignment="Right" Margin="5,0" Opacity="0" RenderTransformOrigin="0,0">
<Grid.RenderTransform>
<TranslateTransform X="-25" x:Name="xform"/>
</Grid.RenderTransform>
<VisualStateManager.VisualStateGroups>
<VisualStateGroup x:Name="OpenStates">
<VisualStateGroup.Transitions>
<VisualTransition From="{x:Null}" GeneratedDuration="0" GeneratedEasingFunction="{x:Null}" Storyboard="{x:Null}" To="{x:Null}"/>
<VisualTransition From="{x:Null}" GeneratedDuration="0:0:0.2" GeneratedEasingFunction="{x:Null}" To="Open">
<Storyboard>
<DoubleAnimation Duration="0:0:0.2" To="0" Storyboard.TargetProperty="X" Storyboard.TargetName="xform">
<DoubleAnimation.EasingFunction>
<BackEase Amplitude="0.3" EasingMode="EaseOut"/>
</DoubleAnimation.EasingFunction>
</DoubleAnimation>
<DoubleAnimation Duration="0:0:0.2" To="1" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="RootVisual"/>
</Storyboard>
</VisualTransition>
</VisualStateGroup.Transitions>
<VisualState x:Name="Closed">
<Storyboard>
<DoubleAnimation Duration="0" To="0" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="RootVisual"/>
</Storyboard>
</VisualState>
<VisualState x:Name="Open">
<Storyboard>
<DoubleAnimation Duration="0" To="0" Storyboard.TargetProperty="X" Storyboard.TargetName="xform"/>
<DoubleAnimation Duration="0" To="1" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="RootVisual"/>
</Storyboard>
</VisualState>
</VisualStateGroup>
</VisualStateManager.VisualStateGroups>
<Grid>
<Path Data="M4,0L0,4 4,8z" Fill="#FFDC000C" HorizontalAlignment="Left" Height="10" Stretch="None" VerticalAlignment="Top" Width="6"/>
<Border Background="#FFDC000C" Margin="4,0,0,0" Padding="1">
<TextBlock Foreground="White" MaxWidth="250" Margin="8,4" TextWrapping="Wrap" Text="{Binding ValidationErrors[0].ErrorContent}"/>
</Border>
</Grid>
<ContentControl/>
</Grid>
</ControlTemplate>
</ToolTip.Template>
</ToolTip>
</Grid.ToolTip>
<Border Background="Transparent" HorizontalAlignment="Right" Height="9" VerticalAlignment="Top" Width="9"/>
<Border BorderBrush="#FFDC000C" BorderThickness="1" CornerRadius="1"/>
<Path Data="M0,2L5,2 5,7z" Fill="#FFDC000C" HorizontalAlignment="Right" Height="7" VerticalAlignment="Top" Width="7"/>
</Grid>
private void UpdateHeadersFooters(RadDocument document) { foreach (Section section in document.Sections) { if (section.Headers.Default.Body != null) { this.UpdateFields(section.Headers.Default.Body); } if (section.Headers.First.Body != null) { this.UpdateFields(section.Headers.First.Body); } if (section.Headers.Even.Body != null) { this.UpdateFields(section.Headers.Even.Body); } if (section.Footers.Default.Body != null) { this.UpdateFields(section.Footers.Default.Body); } if (section.Footers.First.Body != null) { this.UpdateFields(section.Footers.First.Body); } if (section.Footers.Even.Body != null) { this.UpdateFields(section.Footers.Even.Body); } } } private void UpdateFields(RadDocument radDocument) { RadDocumentEditor editor = new RadDocumentEditor(radDocument); editor.ChangeAllFieldsDisplayMode(FieldDisplayMode.Code); }
