A multi-platform .NET UI framework. -!-!-!-!- VOTE FOR SUPPORT IN RIDER: https://youtrack.jetbrains.com/issue/RIDER-39247 -!-!-!-!-
I think Avalonia's DrawingOperation is property WPS's Drawing
@Gillibald I was really referring to wpf's shape vs geometry. That aside there are many cases where the same icon could be wanted huge numbers of times in lists etc and I'm intrigued as to the best way to do this in Avalonia. As an experiment I've added an optional
DrawingImage output to iconpacks.
In theory, is this a viable option?
I have the following pretty simple view definition:
<Window xmlns="https://github.com/avaloniaui"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:dxnav="http://schemas.devexpress.com/winfx/2008/xaml/navigation"
xmlns:dxlc="http://schemas.devexpress.com/winfx/2008/xaml/layoutcontrol"
xmlns:dxwui="http://schemas.devexpress.com/winfx/2008/xaml/windowsui"
xmlns:vm="clr-namespace:MyMvvmApp.ViewModels;assembly=MyMvvmApp"
mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
x:Class="MyMvvmApp.Views.MainWindow"
Icon="/Assets/avalonia-logo.ico"
Title="MyMvvmApp">
<dxnav:OfficeNavigationBar >
<dxnav:NavigationBarItem>One</dxnav:NavigationBarItem>
<dxnav:NavigationBarItem>Two</dxnav:NavigationBarItem>
</dxnav:OfficeNavigationBar>
</Window>
<dxnav:OfficeNavigationBar >
<dxnav:NavigationBarItem>One</dxnav:NavigationBarItem>
<dxnav:NavigationBarItem>Two</dxnav:NavigationBarItem>
</dxnav:OfficeNavigationBar>
</Window>
Severity Code Description Project File Line Suppression State
Error Unable to resolve type OfficeNavigationBar from namespace http://schemas.devexpress.com/winfx/2008/xaml/navigation (line 43 position 10) Line 43, position 10. MyMvvmApp C:\avalonia\sandbox\MyMvvmAppWithDevExpress\Views\MainWindow.xaml 43
Error XAMLIL Unable to resolve type OfficeNavigationBar from namespace http://schemas.devexpress.com/winfx/2008/xaml/navigation (line 15 position 10) Line 15, position 10. MyMvvmApp C:\avalonia\sandbox\MyMvvmAppWithDevExpress\Views\MainWindow.xaml 15
Error Unable to resolve type OfficeNavigationBar from namespace http://schemas.devexpress.com/winfx/2008/xaml/navigation (line 43 position 10) Line 43, position 10. MyMvvmApp C:\avalonia\sandbox\MyMvvmAppWithDevExpress\Views\MainWindow.xaml 43
Error XAMLIL Unable to resolve type OfficeNavigationBar from namespace http://schemas.devexpress.com/winfx/2008/xaml/navigation (line 15 position 10) Line 15, position 10. MyMvvmApp C:\avalonia\sandbox\MyMvvmAppWithDevExpress\Views\MainWindow.xaml 15
I pretty much copied from existing WPF project. I'm not sure how to go about trying to figure out this issue.
Is it a namespace resolution issue?
Avalonia is very similar to WPF but not a 1:1 replacement
I'm noticing there are a lot of Issue posts regarding window transparency on Windows, to many of which the response has been something to the effect of "once Windows 7 support ends, we can use
DwmEnableBlurBehindWindow or DwmExtendFrameIntoClientAreato get blurred transparency on Windows". Problem is, that's straight-up incorrect - those APIs only produce blur on Windows Vista and 7. On Windows 8 and newer, they just produce an opaque solid colour, and in all cases, the affected window is, in one way, or another, coloured to match the user's Window frames. The only time you'd get blur out of those APIs on Windows 8 or newer is with that Aeroglass program installed ( http://glass8.eu/ )...surely that's not going to be required, right?
@SCLD-JBuczkowski It depends on the API's that are being used. If they directly use DirectX to render some components like Telerik does this would be much more work. Also, Storyboards are currently not supported. I think we need some kind of compatibility check for migrating from WPF to Avalonia in the future to make this task easier.
and there still were tons of complaints
just quite a bit of work
any avalonia specific pointers or examples ?
Binding for example is a MarkupExtension
Would look like so for example
Text="{loc:Loc MyResourceName}"
localization is a bit controversial
so it would be unwise to try to force a default approach
I have dynamical TabControl:
<TabControl Items="{Binding TabsList}" SelectedItem="{Binding SelectedTab}" HorizontalAlignment="Stretch" HorizontalContentAlignment="Stretch">I have a synchronous command in dynamicaly fullfilled ContextMenu in TreeView in one Tab:
Calibrate = ReactiveCommand.Create
( () =>
{
CalibrateTabOpen((SelectedNode as TankItem).stnk.tnk);
// Dispatcher.UIThread.Post((Action)(() => CalibrateTabOpen((SelectedNode as TankItem).stnk.tnk)));
}
);This command raise an event:
public Unit CalibrateOpen(ecb.t_tnk tnk)
{
UserTabItem userTab = new UserTabItem() { TabImage = "Assets/clb.png", TabTitle = "Перечень тарировок", TabType = UserTabItem.UserTabType.CALIBRATES };
CalibrateViewModel calibrateViewModel = new CalibrateViewModel(userTab,tnk,httpContext);
TabsList.Add(calibrateViewModel);
SelectedTab = calibrateViewModel;
return Unit.Default;
}After clicking menu I've got the new Tab, but also I've got an empty ContextMenu (very small rectangle) above my new Tab in the same position where it was before. This empty menu disappeares by clicking in any area. How can I avoid this strange behavior?
