CrissCross.WinForms
2.1.2
See the version list below for details.
dotnet add package CrissCross.WinForms --version 2.1.2
NuGet\Install-Package CrissCross.WinForms -Version 2.1.2
<PackageReference Include="CrissCross.WinForms" Version="2.1.2" />
paket add CrissCross.WinForms --version 2.1.2
#r "nuget: CrissCross.WinForms, 2.1.2"
// Install CrissCross.WinForms as a Cake Addin #addin nuget:?package=CrissCross.WinForms&version=2.1.2 // Install CrissCross.WinForms as a Cake Tool #tool nuget:?package=CrissCross.WinForms&version=2.1.2
CrissCross
A Navigation Framework for ReactiveUI based projects
What is CrissCross?
CrissCross is a navigation framework for ReactiveUI based projects. It is designed to be used with ReactiveUI, but could be adapted to be used with any MVVM framework.
Why CrissCross?
CrissCross is designed to be a simple, lightweight, and easy to use navigation framework. It is designed to be used with ReactiveUI.
How do I use CrissCross?
Step 1: Install CrissCross
CrissCross is available on NuGet. You can install it using the NuGet Package Manager:
Install-Package CrissCross
or
Install-Package CrissCross.WPF
or
Install-Package CrissCross.XamForms
or
Install-Package CrissCross.MAUI
or
Install-Package CrissCross.Avalonia
or
Install-Package CrissCross.WinForms
Step 2: Create a ViewModel
Create a ViewModel that inherits from RxObject
. This is the ViewModel that will be used for the MainWindow.
public class MainWindowViewModel : RxObject
{
public MainWindowViewModel()
{
this.BuildComplete(() =>
{
// Do something when the IOC Container is built
});
// Setup the IOC Container
Locator.CurrentMutable.RegisterConstant<MainViewModel>(new());
Locator.CurrentMutable.Register<IViewFor<MainViewModel>>(() => new MainView());
Locator.CurrentMutable.RegisterConstant<FirstViewModel>(new());
Locator.CurrentMutable.Register<IViewFor<FirstViewModel>>(() => new FirstView());
// Notify the application that the IOC Container that it is complete and ready to use.
Locator.CurrentMutable.SetupComplete();
}
}
Step 3: Create a View
Create a View that inherits from NavigationWindow
. This is the View that will be used for the MainWindow.
add xmlns:rxNav="https://github.com/reactivemarbles/CrissCross" to the Window inherits in XAML.
Change Window to rxNav:NavigationWindow in XAML.
Add x:TypeArguments="local:MainWindowViewModel"
public partial class MainWindow : NavigationWindow<MainWindowViewModel>
{
public MainWindow()
{
// Remember to set x:Name in XAML to "mainWindow"
InitializeComponent();
this.WhenActivated(disposables =>
{
// Do something when the View is activated
// Configure the Navigation for the MainWindow
NavBack.Command = ReactiveCommand.Create(() => this.NavigateBack(), CanNavigateBack).DisposeWith(d);
// Navigate to the MainViewModel
this.NavigateToView<MainViewModel>();
});
}
}
Step 4: Create a ViewModel
Create a ViewModel that inherits from RxObject
. This is the ViewModel that will be used for the MainView.
public class MainViewModel : RxObject
{
public MainViewModel()
{
this.BuildComplete(() =>
{
// Do something when the IOC Container is built
// Configure the Navigation for the MainViewModel using, you will pass the name of the Navigation Host Window that you want to navigate with.
this.NavigateBack("mainWindow")
this.CanNavigateBack("mainWindow")
this.NavigateToView<FirstViewModel>("mainWindow")
});
}
}
Step 5: Create a View
Create a View that inherits from ReactiveUserControl
. This is the View that will be used for the MainView.
public partial class MainView : ReactiveUserControl<MainViewModel>
{
public MainView()
{
InitializeComponent();
this.WhenActivated(disposables =>
{
// Do something when the View is activated
});
}
}
Step 6: For WPF Applications Configure Single Instance Application if required
If you want to prevent multiple instances of the application from running at the same time, you can use the Make.SingleInstance
method.
protected override void OnStartup(StartupEventArgs e)
{
// This will prevent multiple instances of the application from running at the same time.
Make.SingleInstance("MyUniqueAppName ddd81fc8-9107-4e33-b848-cac4c3ec3d2a");
base.OnStartup(e);
}
Step 7: Run the application
Run the application and you should see the MainView.
Avalonia
Step 1: Install CrissCross
CrissCross is available on NuGet. You can install it using the NuGet Package Manager:
Install-Package CrissCross.Avalonia
Step 2: Create a ViewModel
Create a ViewModel that inherits from RxObject
. This is the ViewModel that will be used for the MainWindow.
public class MainWindowViewModel : RxObject
{
public MainWindowViewModel()
{
this.BuildComplete(() =>
{
// Do something when the IOC Container is built
});
// Setup the IOC Container
Locator.CurrentMutable.RegisterConstant<MainViewModel>(new());
Locator.CurrentMutable.Register<IViewFor<MainViewModel>>(() => new MainView());
Locator.CurrentMutable.RegisterConstant<FirstViewModel>(new());
Locator.CurrentMutable.Register<IViewFor<FirstViewModel>>(() => new FirstView());
// Notify the application that the IOC Container that it is complete and ready to use.
Locator.CurrentMutable.SetupComplete();
}
}
Step 3: Create a NavigationView
Create a View that inherits from NavigationWindow
OR NavigationUserControl
. This is the View that will be used for the MainWindow.
add xmlns:rxNav="https://github.com/reactivemarbles/CrissCross"
Change Window to rxNav:NavigationWindow in XAML.
OR Change UserControl to rxNav:NavigationUserControl in XAML.
As Avalonia has two modes of operation you will need to select the correct mode for your application.
public partial class MainWindow : NavigationWindow<MainWindowViewModel>
{
public MainWindow()
{
// Remember to set x:Name in XAML to "mainWindow"
InitializeComponent();
this.WhenActivated(disposables =>
{
// Do something when the View is activated
// Configure the Navigation for the MainWindow
NavBack.Command = ReactiveCommand.Create(() => this.NavigateBack(), CanNavigateBack).DisposeWith(d);
// Navigate to the MainViewModel
this.NavigateToView<MainViewModel>();
});
}
}
Step 4: Create a ViewModel
Create a ViewModel that inherits from RxObject
. This is the ViewModel that will be used for the MainView.
public class MainViewModel : RxObject
{
public MainViewModel()
{
this.BuildComplete(() =>
{
// Do something when the IOC Container is built
// Configure the Navigation for the MainViewModel using, you will pass the name of the Navigation Host Window that you want to navigate with.
this.NavigateBack("mainWindow")
this.CanNavigateBack("mainWindow")
this.NavigateToView<FirstViewModel>("mainWindow")
});
}
}
Step 5: Create a View
Create a View that inherits from ReactiveUserControl
. This is the View that will be used for the MainView.
public partial class MainView : ReactiveUserControl<MainViewModel>
{
public MainView()
{
InitializeComponent();
this.WhenActivated(disposables =>
{
// Do something when the View is activated
});
}
}
CrissCross.WPF.Plot
CrissCross.WPF.Plot is a library that provides a simple way to plot data in WPF applications. It is designed to be used with CrissCross.
Adriana Segher came up with the initial concept of creating a Plot that could accept a Reactive data source. This was then developed into a library that could be used with CrissCross Wpf.
The library is built on top of ScottPlot and provides a simple way to plot Reactive data in WPF applications.
The library is available on NuGet. You can install it using the NuGet Package Manager:
Install-Package CrissCross.WPF.Plot
Current Features
- Plot data from a Reactive data source
- Plot data from a array of Reactive data source with multiple series (limited to 9 currently)
- Cursor tracking via a CrossHair
- Zooming and Panning
- Dragging a zoom area
- Visibility of plots
- Auto Scale / Manual Scale
- Enable / Disable interaction with the plot
- Multiple Y Axis
Future Features
- More than 9 series
- Configuration of the Chart through a property dialog
- Axis configuration, Color Configuration, Scale Configuration, Line Configuration
- Multiple CrossHairs with differential analytics
- Multiple X Axis for XY Plots
- Select a plotalbe data from a large data source such as a Dynamic Data Source
CrissCross.WPF.WebView2
CrissCross.WPF.Webview2 is a control for Wpf allowing the placement of other wpf controls on top of the WebView2. The base Microsoft.Web.WebView2 library has a WebView2CompositionControl but this is only targeting net46 and does not work for net core.
In CrissCross.WPF.Webview2 we have created a WebView2Wpf control that has the majority of the features that the WebView2CompositionControl has working, however some use an underlying private layer which we don't have access to. Further Documentation can be found here microsoft.web.webview2.wpf
The library is available on NuGet. You can install it using the NuGet Package Manager:
xmlns:webv="https://github.com/reactivemarbles/CrissCross"
<webv:WebView2Wpf
x:Name="WebView2Wpf"
AutoDispose="True">
<--! Add your Xaml here -->
</webv:WebView2Wpf>
// In Code behind set the Source to the Uri you wish to navigate to, this can be set in the Xaml too.
WebView2Wpf.Source = new System.Uri("https://www.reactiveui.net/");
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0-windows10.0.17763 is compatible. net7.0-windows was computed. net8.0-windows was computed. net8.0-windows10.0.17763 is compatible. |
.NET Framework | net462 is compatible. net463 was computed. net47 was computed. net471 was computed. net472 is compatible. net48 is compatible. net481 was computed. |
-
.NETFramework 4.6.2
- CrissCross (>= 2.1.2)
- ReactiveUI.WinForms (>= 20.1.63)
-
.NETFramework 4.7.2
- CrissCross (>= 2.1.2)
- ReactiveUI.WinForms (>= 20.1.63)
-
.NETFramework 4.8
- CrissCross (>= 2.1.2)
- ReactiveUI.WinForms (>= 20.1.63)
-
net6.0-windows10.0.17763
- CrissCross (>= 2.1.2)
- ReactiveUI.WinForms (>= 20.1.63)
-
net8.0-windows10.0.17763
- CrissCross (>= 2.1.2)
- ReactiveUI.WinForms (>= 20.1.63)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
2.2.1 | 60 | 11/25/2024 |
2.2.0 | 73 | 11/18/2024 |
2.1.3 | 74 | 11/7/2024 |
2.1.2 | 72 | 11/5/2024 |
2.1.1 | 81 | 11/5/2024 |
2.1.0 | 91 | 10/13/2024 |
2.0.6 | 88 | 8/2/2024 |
2.0.5 | 92 | 8/1/2024 |
2.0.4 | 62 | 7/31/2024 |
2.0.3 | 85 | 7/28/2024 |
2.0.2 | 83 | 7/25/2024 |
2.0.1 | 100 | 7/10/2024 |
2.0.0 | 94 | 5/18/2024 |
1.0.25 | 112 | 4/30/2024 |
1.0.24 | 115 | 4/19/2024 |
1.0.23 | 106 | 4/10/2024 |
1.0.22 | 111 | 3/29/2024 |
1.0.21 | 119 | 3/26/2024 |
1.0.20 | 118 | 3/22/2024 |
1.0.19 | 120 | 3/21/2024 |
1.0.18 | 134 | 3/19/2024 |
1.0.17 | 116 | 3/14/2024 |
1.0.16 | 123 | 3/13/2024 |
1.0.15 | 119 | 3/12/2024 |
1.0.14 | 129 | 3/11/2024 |
1.0.13 | 130 | 3/8/2024 |
1.0.12 | 131 | 3/7/2024 |
1.0.11 | 120 | 3/5/2024 |
1.0.10 | 120 | 2/22/2024 |
1.0.9 | 119 | 2/21/2024 |
1.0.8 | 116 | 2/21/2024 |
1.0.7 | 118 | 2/19/2024 |
1.0.6 | 118 | 2/16/2024 |
1.0.5 | 127 | 2/8/2024 |
1.0.4 | 179 | 1/4/2024 |
1.0.3 | 151 | 9/11/2023 |
1.0.2 | 126 | 9/9/2023 |
1.0.1 | 129 | 9/8/2023 |
1.0.0 | 136 | 9/7/2023 |
Compatability with Net 6/8 and netstandard2.0