Pysar.Wpf 0.1.41

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Pysar.Wpf --version 0.1.41
                    


                    

                
NuGet\Install-Package Pysar.Wpf -Version 0.1.41
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Pysar.Wpf" Version="0.1.41" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Pysar.Wpf" Version="0.1.41" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Pysar.Wpf" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Pysar.Wpf --version 0.1.41
                    


                    

                
#r "nuget: Pysar.Wpf, 0.1.41"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Pysar.Wpf@0.1.41
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Pysar.Wpf&version=0.1.41
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Pysar.Wpf&version=0.1.41
                    


                            Install as a Cake Tool

Pysar.Wpf

WPF integration for Pysar, a cross-platform report engine for .NET: pack URI and assembly manifest asset access, font registration, a scrollable, zoomable ReportView, and printing. It installs a WpfReportPlatformHandler for file and font access.

Windows only. On macOS and Linux the package is not produced; the real WPF sources compile only under net10.0-windows.

Setup

Call UsePysar from Application.OnStartup:

protected override void OnStartup(StartupEventArgs e)
{
    base.OnStartup(e);
    this.UsePysar(pysar => pysar
        .AddFont("Fonts/Ubuntu-Regular.ttf", "Ubuntu")
        .AddFont("Fonts/Ubuntu-Bold.ttf", "Ubuntu", FontStyle.Bold));
}

Showing a report

<pysar:ReportView Report="{Binding Report}"
                    ZoomMode="FitWidth"
                    Zoom="{Binding Zoom}"
                    EffectiveZoom="{Binding EffectiveZoom, Mode=OneWayToSource}"
                    CurrentPage="{Binding CurrentPage}"
                    PageSpacing="24" />

Ctrl + wheel zooms around the pointer; a plain wheel scrolls; double-click toggles fit width and close-up. PageBorderColor and PageBorderThickness frame each page; PageSpacing is the gap between pages and does not scale with the zoom. Bind EffectiveZoom to show the zoom percentage — Zoom holds what was asked for, not what the view settled on.

Printing

Printing uses the same vector PDF pipeline as export:

var printer = new WpfReportPrinter(PysarWpf.Renderer);
await printer.PrintAsync(builtReport);

The report must already have Build() called.

Documentation

License

MIT — see LICENSE.

Product Compatible and additional computed target framework versions.
.NET net10.0-windows7.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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
0.1.63 97 10/1/2026
0.1.56 108 9/20/2026
0.1.53 98 9/20/2026
0.1.46 112 9/18/2026
0.1.44 99 9/16/2026
0.1.41 102 9/15/2026
0.1.38 101 9/14/2026
0.1.34 111 9/13/2026
0.1.31 108 9/11/2026
0.1.24 116 9/6/2026
0.1.10 118 8/30/2026
0.1.0 108 8/30/2026

## Highlights

### Uno integration: a real entry point

Registering Pysar in an Uno application is now a single call on `Application`, and it works the same
way from every head (WebAssembly, Desktop, Android, iOS, WinAppSDK) — `OnLaunched` is the one place
they all run through.

```csharp
protected override void OnLaunched(LaunchActivatedEventArgs args)
{
   this.UsePysar(typeof(App).Assembly, pysar => pysar
       .AddFont("Fonts/Ubuntu-Regular.ttf", "Ubuntu")
       .AddFont("Fonts/Ubuntu-Bold.ttf", "Ubuntu", FontStyle.Bold));
}
```

- `ApplicationExtensions.UsePysar(...)` and `UsePysarAsync(...)` — the latter preloads
 `ms-appx:///` assets for applications that ship them as `Content` rather than `EmbeddedResource`.
- `assetAssembly` is required: on the WebAssembly head the entry assembly is the head project, not
 the application project the assets are packaged into.
- Registration moved into `UnoRegistration`; `PysarUno` now exposes `PlatformHandler` /
 `ExportService` and resets the export service on re-registration.

### Ctrl+wheel and trackpad pinch zoom the report, not the page (browser head)

`ReportView` has always zoomed on Ctrl+wheel and marked the event handled, but on a browser head
that changed nothing visible: "handled" is a managed routing flag, while page zoom is a DOM default
action that only `preventDefault` on a non-passive listener stops. The reader got a scaled page and
a report that never moved — and the trackpad pinch went with it, since Chrome and Safari deliver it
as a wheel event with `ctrlKey` set.

`UsePysar` now installs a small embedded script, imported from a data URL, so a consuming
application adds one call and no files. Opt out with `suppressBrowserZoom: false` to keep the
browser's own zoom as an accessibility affordance.

Suppression covers the whole Uno canvas: Uno draws the entire application into a single canvas, so
the DOM cannot tell the report from the toolbar beside it. Anything on the page outside that canvas
keeps the browser's zoom.

### Measure probe caching

New `MeasureContext` and `LayoutEngine.ProbeSizeAsync` cache probe measurements, and
`GridLayoutMeasurer` / `StackLayoutMeasurer` now measure through probes instead of re-measuring the
same subtree repeatedly — a large drop in repeat measures on nested layouts.

### A readable diagnostic for the SkiaSharp native/managed split on WebAssembly

An Uno browser head pulls `SkiaSharp.NativeAssets.WebAssembly` through
`Uno.WinUI.Runtime.Skia.WebAssembly.Browser`, which asks for the 3.119 line, while Pysar renders
through 4.151. NuGet resolves one managed SkiaSharp and one native archive, and the two no longer
agree.

Every other platform reports that split as a startup exception with a message of its own.
WebAssembly links the native side statically at build time, so it surfaces instead as a wall of
`wasm-ld: undefined symbol: sk_*` lines naming entry points the application never wrote, with
nothing pointing at the version that caused them.

The check now ships as `buildTransitive`, so it reaches consumers who referenced `Pysar.Uno` or
`Pysar.Blazor` rather than `Pysar` itself — those are the ones who end up on a browser head.
Declaring a dependency on the native package would fix it silently, but it is a 67 MB download
charged to every WPF, console and Uno desktop consumer that will never link a wasm binary.

## Breaking changes

- `PysarUno.Use(...)` and `PysarUno.UseAsync(...)` are removed. Use `Application.UsePysar(...)` /
 `UsePysarAsync(...)` instead.

## Other

- Docs updated: root `README.md`, `src/Pysar.Uno/README.md`, `docs/quick-start.md`.
- New `AGENTS.md`; added `opencode.json`.
- Tests: `UnoRegistrationTests`, `MeasureProbeCachingTests`, and a new `PackageLayoutTests`
 assertion for the `buildTransitive` payload.

**Full Changelog**: https://github.com/MriyaLab/Pysar/compare/v0.1.38...v0.1.42