Aardvark.Dom.Remote
1.1.9
dotnet add package Aardvark.Dom.Remote --version 1.1.9
NuGet\Install-Package Aardvark.Dom.Remote -Version 1.1.9
<PackageReference Include="Aardvark.Dom.Remote" Version="1.1.9" />
<PackageVersion Include="Aardvark.Dom.Remote" Version="1.1.9" />
<PackageReference Include="Aardvark.Dom.Remote" />
paket add Aardvark.Dom.Remote --version 1.1.9
#r "nuget: Aardvark.Dom.Remote, 1.1.9"
#:package Aardvark.Dom.Remote@1.1.9
#addin nuget:?package=Aardvark.Dom.Remote&version=1.1.9
#tool nuget:?package=Aardvark.Dom.Remote&version=1.1.9
Aardvark is an open-source platform for visual computing, real-time graphics and visualization.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
- Aardvark.Application (>= 5.6.4)
- Aardvark.Base (>= 5.3.20 && < 5.4.0)
- Aardvark.Dom (= 1.1.9)
- Aardvark.Rendering.Text (>= 5.6.4 && < 5.7.0)
- Aardvark.SceneGraph (>= 5.6.4 && < 5.7.0)
- FSharp.Core (>= 8.0.100)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Aardvark.Dom.Remote:
| Package | Downloads |
|---|---|
|
Aardvark.Dom.Server
Aardvark is an open-source platform for visual computing, real-time graphics and visualization. |
|
|
Aardworx.WebAssembly.Dom
WebAssembly libraries for Aardvark |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.1.9 | 109 | 5/19/2026 |
| 1.1.8 | 279 | 4/28/2026 |
| 1.1.7 | 223 | 4/28/2026 |
| 1.1.6 | 157 | 4/27/2026 |
| 1.1.5 | 181 | 4/26/2026 |
| 1.1.4 | 177 | 4/26/2026 |
| 1.1.3 | 173 | 4/26/2026 |
| 1.1.2 | 173 | 4/26/2026 |
| 1.1.1 | 168 | 4/26/2026 |
| 1.1.0 | 451 | 4/25/2026 |
| 1.0.25 | 201 | 4/15/2026 |
| 1.0.24 | 223 | 4/13/2026 |
| 1.0.23 | 573 | 11/20/2025 |
| 1.0.22 | 392 | 11/13/2025 |
| 1.0.21 | 328 | 11/9/2025 |
| 1.0.20 | 306 | 10/28/2025 |
| 1.0.19 | 293 | 10/28/2025 |
| 1.0.18 | 295 | 10/23/2025 |
| 1.0.17 | 417 | 10/22/2025 |
| 1.0.16 | 285 | 10/22/2025 |
fix: picking was broken on HiDPI / Retina displays after the renderer started honoring `devicePixelRatio` (Aardworx.WebAssembly 1.2.7). `SceneHandler.HandlePointerEvent` / `HandleTapEvent` / `HandleWheelEvent` computed `pixel = original.ClientPosition - V2i original.ClientRect.Min` — CSS pixels from DOM events — and passed that straight to the pick-buffer read. With a 3× framebuffer (iPhone) the read happened at 1/3 the click location → wrong scope or none. `SceneEventLocation` also got the mismatched `pixel` (CSS) and `viewportSize` (fb), breaking any consumer doing `pixel / viewportSize` for NDC.
convert at the input boundary instead: a new `toFbPixel` helper in `SceneHandler` scales the event position via the per-event `ClientRect.Size` vs. `viewportSize` ratio — self-consistent under any `RenderControl.PixelRatio` override (no `window.devicePixelRatio` lookup needed). Pixel space stays sub-pixel `V2d` end-to-end; rounding to `V2i` happens only at the GL read-edge.
added `RenderControlInfo.ClientSize : aval<V2i>` (CSS pixel size of the canvas) alongside the existing `ViewportSize` (framebuffer pixels). Apps positioning HTML overlays via `Left`/`Top` should bind `let! cs = RenderControl.ClientSize` instead of `ViewportSize`. Shader / projection / NDC math keeps using `ViewportSize`. The split makes the unit explicit in the type — no DPR multiplication in app code. `ClientSize` is populated lazily from the first DOM event (`ClientRect.Size`); it's `V2i.II` before any event arrives, which is fine for the typical case where overlays are conditional on user interaction.