Currently PropertyDefinitions have only one Property for DataBinding, which is very strange solution.
All these instances are DependencyObject, but at the same time they are not in the visual tree and we could not bind to a visibility or to readonly or to any other property without some starnge sorkarounds (why this was designed in this way?).
This makes these objects almost useless. becuae we cannot fully use them in an MVVM way (bindings, multiibindings, etc.)
Possible solutions:
Using RadTabbedWindow I noticed difficulty dragging maximized windows between monitors. It seems to happen in multi-monitor environments and only when dragging Left of the PrimaryScreen.
In the video I've included , the blue window is a standard window and can be maximized in one drag across any display.
The white window is RadTabbedWindow and the drag will default to the PrimaryScreen when dragged to the left-most display.
Any help would be appreciated. Thanks
Hi,
Since we want to boost up the performance of the ScheduleView , we've applied the 2023_2_718 UI for WPF to enable the virtualization of the group headers with setting the property IsGroupHeadersVirtualizationEnabled="True". However we've experienced issues also with rendering for the appointments and group headers(resources) when scrolling.
In one of the screens where the schedule view is used, the group headers don't have equal sizes, for example:
The height may vary depending on the overlapping appointments for the resource which is allowed for our system.
There is a note that there might be issues and unexpected behavior when the headers have different sizes claimed here:
WPF ScheduleView - UI Virtualization - Telerik UI for WPF
In this scenario we experience multiple issues, like for example when scrolled at the bottom, and the schedule view is fully refreshed, the resources and appointments are not rendered :
until it's scrolled.
Also when scrolling, we experience a "blinking" rendering, the group headers change sizes on scrolling :
Can you please let us know if/when this is planned to be fixed.
Another issue not related to the header size differences is that some of the appointments are lost (not rendered) when the height of the schedule view is changed resulting in some of the appointments to not be visible anymore .The selection is kept on the group headers, but the appointments are not rendered.
Thank you!
After using Direct2D in ChartView, zoom in/zoom out/pan , finally shrink back to the original size. After many iterations, it is possible that the Scatter spline will be shifted, if don't use Direct2D or use the Net Framework,Such problems do not arise.
Please check the attachment.
Hi,
I download the source code 'Telerik_UI_for_WPF_Source_2022_1_117' and then I want to run 'Build_WPF60.bat' [\Telerik_UI_for_WPF_Source_2022_1_117\Build\BatFiles]. An error occurs, see the attachment: 'Could not locate the assembly "Telerik.Windows.Documents.Core".' I tried it on Win 10 and Win 11 with installed VS202
2."
Best regards
Huráb Radek
Hello,
I want to report a bug with text color in textbox and presumably in some other controls. When the textbox is edited, then the color is correctly black:
Telerik: Windows 11 settings textBox:
But when the textbox loses focus, it changes the color to gray, which is hard to read and looks like disabled:
Telerik: Windows 11 settings textBox:
Thanks
i hope add char controls
like :
https://developers.google.com/chart/interactive/docs/gallery/timeline
https://github.com/dreamRs/timelineschart
I have a Pie chart like this:
<telerik:RadPieChart Palette="Arctic">
<telerik:DoughnutSeries ItemsSource="{Binding GraphedStatistics, Mode=OneTime}" ValueBinding="Previous" ShowLabels="True">
<telerik:DoughnutSeries.LabelDefinitions>
<telerik:ChartSeriesLabelDefinition>
<telerik:ChartSeriesLabelDefinition.Template>
<DataTemplate>
<StackPanel Opacity="{Binding Value, Mode=OneWay>
<TextBlock Text="{Binding DataItem.Name}" HorizontalAlignment="Center" Foreground="{StaticResource textBlockForeground}"/>
<TextBlock HorizontalAlignment="Center" Foreground="{StaticResource textBlockForeground}">
<Run Text="{Binding Value, Mode=OneWay, StringFormat=' {0:#}'}"/>
<Run Text="{Binding Percent, Mode=OneWay, StringFormat=' ({0:#}%)'}"/>
</TextBlock>
</StackPanel>
</DataTemplate>
</telerik:ChartSeriesLabelDefinition.Template>
</telerik:ChartSeriesLabelDefinition>
</telerik:DoughnutSeries.LabelDefinitions>
</telerik:DoughnutSeries>
If I generate a pie or doughnut chart the Percent is not updated when I update a value in the bound data source (GraphedStatistics). Note: I am updating the observable collection not replacing it. The graph is redrawn correctly and Value updates correctly.
The version is 22.1.1.0 (not in the options below)
Updated (See that 'Monaco' is the same percentage as before the update, Value is correct and the UI Graph is correct but the segment is clearly not 26%)
Hello,
When I do the following:
and I assign this style to my dynamically created columns from a behavior attached to the RadGridView, the style of the tooltip is the same as the style of the header.
They seem to share the same style, so that when I change one property on the header, the tooltip gets the same, and vice-versa.
Do you repro? I'm on version 2020.3.1020.45.
Thanks,
Arthur
Right now, it is not easy to disable styles for standard controls like Button.
Especially when using NoXaml.
You have to create an Empty style on Application level for the control to "rewind" its style.
I do believe this kind of style drags down performance of controls when unloading, since it causes StyleChanged events.
Some explanation about performance (how things work to my understanding). Might be BS, but I spend a few hours debugging through .net code to get this idea:
Issue is, that when control is unloaded, its not part of the logical / visual tree of the application anymore, so it falls back to styles defined on assembly level.
e.g. Themes/Generic.xaml. So the empty styles defined on Application level do not count anymore, but the ones you defined in your theme.
This can be observed on RadTabbedWindow. When unloading pages (like switching between them), controls fall back to the styles defined in the theme from Telerik.Windows.Controls.Navigation, because they are still children of that page.
You can observe this behaviour if you set a Breakpoint in FrameworkElement.OnStyleChanged before unloading a control tree.
If you'd remove the System.Windows.xaml from your theme-dictionaries so that one can decide to merge those styles or not, that would be great.
I've just updated Telerik and are now getting this compile time error:
Severity Code Description Project File Line Suppression State
Error XDG0047 The specified value cannot be assigned. The following type was expected: "IFilteringControl". Modelkatalog.Client C:\develop\data-tool-modelkatalog\Modelkatalog.Client\Controls\List\CarVariantsList.xaml 1
I'm getting this error from 2 XAML documents that both implement a custom Fitler for the RadGridView
I didn't get this error before, and I'm still able to compile and run the project - which kind of defeat the purpose of [Severity: Error]
Hi
I would like to know if Progress Telerik has some plan to port their WPF controls to Avalonia (avaloniaui.net).
Thanks
Laurent
Hi:
China has the largest population and we have a lot of Chinese customers. Increasing support for Chinese localization, IME and bug fixes should be a high priority.
Unfortunately, there are still no support plans for many features. In the Chinese environment, there are still many bugs.
Hope can be taken seriously!
There is too much unplanned feedback, not just in Chinese, but also in Japanese and Korean. These should be viewed as a single issue and considered a serious one.
That's more than enough votes. The following should be combined。
https://feedback.telerik.com/wpf/1351270-radrichtextbox-introduce-support-for-other-chinese-imes-input-method-editors-like-sogou-pinyin-and-qq-pinyinkato-pr
https://feedback.telerik.com/wpf/1355000-richtextbox-implement-out-of-the-box-support-for-sogou-pinyin
https://feedback.telerik.com/wpf/1352638-maskedinput-add-support-for-chinese-input-symbols
We are noticing inconsistent display issue when it comes to running this app via Citrix.
In particular the when we are using the Filter option on a grid screen, some times we get a partial display vs the Complete display. Please advise what we can do to ensure stable presentation
Correct
incorrect
After defining my colors in the Telerik color theme generator vs wasn't recognizing the emitted code as valid. I had to explore the Intellisense suggestions and try different variations until I arrived at the correct solution:
I'm not sure if this has to do with versioning differences or is a general case. Regardless, I figured I'd let the Telerik team know.
Best,
Nick
// Theme Editor Output
VisualStudio2019.Palette.AccentColor = (Color)ColorConverter.ConvertFromString("#FFF5CC84");
VisualStudio2019.Palette.AccentMainColor = (Color)ColorConverter.ConvertFromString("#FFAAC0FF");
VisualStudio2019.Palette.AccentDarkColor = (Color)ColorConverter.ConvertFromString("#FF5F6FA4");
VisualStudio2019.Palette.AccentSecondaryDarkColor = (Color)ColorConverter.ConvertFromString("#FF40508D");
VisualStudio2019.Palette.AccentMouseOverColor = (Color)ColorConverter.ConvertFromString("#FFC4D5FF");
VisualStudio2019.Palette.AccentFocusedColor = (Color)ColorConverter.ConvertFromString("#FFD2A85E");
VisualStudio2019.Palette.AccentForegroundColor = (Color)ColorConverter.ConvertFromString("#FF5F6FA4");
VisualStudio2019.Palette.ValidationColor = (Color)ColorConverter.ConvertFromString("#FFFF3333");
VisualStudio2019.Palette.BasicColor = (Color)ColorConverter.ConvertFromString("#FF94A6CA");
VisualStudio2019.Palette.SemiBasicColor = (Color)ColorConverter.ConvertFromString("#FFC0CAE9");
VisualStudio2019.Palette.PrimaryColor = (Color)ColorConverter.ConvertFromString("#FFF2F5FC");
VisualStudio2019.Palette.SecondaryColor = (Color)ColorConverter.ConvertFromString("#FFFFFFFF");
VisualStudio2019.Palette.MarkerColor = (Color)ColorConverter.ConvertFromString("#FF1E1E1E");
VisualStudio2019.Palette.MarkerInvertedColor = (Color)ColorConverter.ConvertFromString("#FFFFFFFF");
VisualStudio2019.Palette.IconColor = (Color)ColorConverter.ConvertFromString("#FF414141");
VisualStudio2019.Palette.AlternativeColor = (Color)ColorConverter.ConvertFromString("#FFF7F9FE");
VisualStudio2019.Palette.MouseOverColor = (Color)ColorConverter.ConvertFromString("#FFFFF8DF");
VisualStudio2019.Palette.ComplementaryColor = (Color)ColorConverter.ConvertFromString("#FFD9E0F8");
VisualStudio2019.Palette.MainColor = (Color)ColorConverter.ConvertFromString("#FFFCFCFC");
VisualStudio2019.Palette.HeaderColor = (Color)ColorConverter.ConvertFromString("#FF40568D");
VisualStudio2019.Palette.DockingBackgroundColor = (Color)ColorConverter.ConvertFromString("#FF5F6FA4");
VisualStudio2019.Palette.ReadOnlyBackgroundColor = (Color)ColorConverter.ConvertFromString("#FFFCFCFC");
VisualStudio2019.Palette.ReadOnlyBorderColor = (Color)ColorConverter.ConvertFromString("#FF94A6CA");
VisualStudio2019.Palette.DisabledOpacity = 0.3;
VisualStudio2019.Palette.ReadOnlyOpacity = 0.6;
// Fixed Output
VisualStudio2019Palette.Palette.AccentColor = (Color)ColorConverter.ConvertFromString("#FF5399EE");
VisualStudio2019Palette.Palette.AccentMainColor = (Color)ColorConverter.ConvertFromString("#FF5399EE");
VisualStudio2019Palette.Palette.AccentDarkColor = (Color)ColorConverter.ConvertFromString("#FF233042");
VisualStudio2019Palette.Palette.AccentSecondaryDarkColor = (Color)ColorConverter.ConvertFromString("#FF2E6FF2");
VisualStudio2019Palette.Palette.AccentMouseOverColor = (Color)ColorConverter.ConvertFromString("#FF5399EE");
VisualStudio2019Palette.Palette.AccentFocusedColor = (Color)ColorConverter.ConvertFromString("#FF2E6FF2");
//VisualStudio2019Palette.Palette.AccentForegroundColor = (Color)ColorConverter.ConvertFromString("#FFBBD3F0");
VisualStudio2019Palette.Palette.ValidationColor = (Color)ColorConverter.ConvertFromString("#FFFF3333");
VisualStudio2019Palette.Palette.BasicColor = (Color)ColorConverter.ConvertFromString("#FFBBD3F0");
VisualStudio2019Palette.Palette.SemiBasicColor = (Color)ColorConverter.ConvertFromString("#FFEAEFF6");
VisualStudio2019Palette.Palette.PrimaryColor = (Color)ColorConverter.ConvertFromString("#FFEAEFF6");
VisualStudio2019Palette.Palette.SecondaryColor = (Color)ColorConverter.ConvertFromString("#FFFFFFFF");
VisualStudio2019Palette.Palette.MarkerColor = (Color)ColorConverter.ConvertFromString("#FF262626");
VisualStudio2019Palette.Palette.MarkerInvertedColor = (Color)ColorConverter.ConvertFromString("#FFFFFFFF");
VisualStudio2019Palette.Palette.IconColor = (Color)ColorConverter.ConvertFromString("#FF414141");
VisualStudio2019Palette.Palette.AlternativeColor = (Color)ColorConverter.ConvertFromString("#FFF7F9FE");
VisualStudio2019Palette.Palette.MouseOverColor = (Color)ColorConverter.ConvertFromString("#FF5399EE");
VisualStudio2019Palette.Palette.ComplementaryColor = (Color)ColorConverter.ConvertFromString("#FFBED4F0");
VisualStudio2019Palette.Palette.MainColor = (Color)ColorConverter.ConvertFromString("#FFFCFCFC");
VisualStudio2019Palette.Palette.HeaderColor = (Color)ColorConverter.ConvertFromString("#FF233042");
//VisualStudio2019Palette.Palette.DockingBackgroundColor = (Color)ColorConverter.ConvertFromString("#FF233042");
VisualStudio2019Palette.Palette.ReadOnlyBackgroundColor = (Color)ColorConverter.ConvertFromString("#FFFCFCFC");
VisualStudio2019Palette.Palette.ReadOnlyBorderColor = (Color)ColorConverter.ConvertFromString("#FF94A6CA");
VisualStudio2019Palette.Palette.DisabledOpacity = 0.3;
VisualStudio2019Palette.Palette.ReadOnlyOpacity = 0.6;