ILSpy

9645 Commits

54 Branches

94 Tags

91 MiB

Branch: fix/lambda-parameter-syntax

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	7465fb1fb0	Keep the editor zoom separate from the configured font size Zoom was stored as the font size itself, so the zoom overlay had no way to tell a Ctrl+Wheel zoom from a font size picked in the options dialog: any size other than the hard-coded default made the overlay appear, and the percentage was measured against that default rather than the user's font. A separate multiplier restores the split the setting always implied - the options dialog moves the base size, zoom scales it - so 100% means "the font you configured", whatever that is. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	1 month ago
Siegfried Pammer	51aafa0fd9	Move ILSpy UI code back to the ICSharpCode.ILSpy root namespace The Avalonia port had placed the UI app in an ILSpy.* namespace tree, while the csproj RootNamespace and every prior release (through 10.1) use ICSharpCode.ILSpy.*. Restoring the historical namespace reduces the public API diff against release/10.1 for plugin authors and removes the shadowing that forced global:: qualifiers in the test project. The Images class and AccessOverlayIcon enum move back into the root namespace (as in 10.1), since an ICSharpCode.ILSpy.Images namespace would shadow the Images class for all code inside ICSharpCode.ILSpy. Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago
Siegfried Pammer	05ae000bad	Editor zoom — Ctrl+Wheel scale + corner button overlay Mirrors WPF's ZoomScrollViewer behaviour without templating AvaloniaEdit's TextEditor. The Avalonia path scales the editor's FontSize (which feeds DisplaySettings.SelectedFontSize) on Ctrl+Wheel; AvaloniaEdit lays out at the new size on the next render. WPF's full-content-tree LayoutTransform approach doesn't fit AvaloniaEdit's architecture, but the font-scale result is what users actually expect from "editor zoom". Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago

Author

SHA1

Message

Date

Siegfried Pammer

7465fb1fb0

Keep the editor zoom separate from the configured font size

Zoom was stored as the font size itself, so the zoom overlay had no way to
tell a Ctrl+Wheel zoom from a font size picked in the options dialog: any
size other than the hard-coded default made the overlay appear, and the
percentage was measured against that default rather than the user's font.
A separate multiplier restores the split the setting always implied - the
options dialog moves the base size, zoom scales it - so 100% means "the
font you configured", whatever that is.

Assisted-by: Claude:claude-opus-5[1m]:Claude Code

1 month ago

Siegfried Pammer

51aafa0fd9

Move ILSpy UI code back to the ICSharpCode.ILSpy root namespace

The Avalonia port had placed the UI app in an ILSpy.* namespace tree,
while the csproj RootNamespace and every prior release (through 10.1)
use ICSharpCode.ILSpy.*. Restoring the historical namespace reduces the
public API diff against release/10.1 for plugin authors and removes the
shadowing that forced global:: qualifiers in the test project. The
Images class and AccessOverlayIcon enum move back into the root
namespace (as in 10.1), since an ICSharpCode.ILSpy.Images namespace
would shadow the Images class for all code inside ICSharpCode.ILSpy.

Assisted-by: Claude:claude-fable-5:Claude Code

3 months ago

Siegfried Pammer

05ae000bad

Editor zoom — Ctrl+Wheel scale + corner button overlay

Mirrors WPF's ZoomScrollViewer behaviour without templating AvaloniaEdit's
TextEditor. The Avalonia path scales the editor's FontSize (which feeds
DisplaySettings.SelectedFontSize) on Ctrl+Wheel; AvaloniaEdit lays out at the
new size on the next render. WPF's full-content-tree LayoutTransform approach
doesn't fit AvaloniaEdit's architecture, but the font-scale result is what
users actually expect from "editor zoom".

Assisted-by: Claude:claude-opus-4-7:Claude Code

3 months ago

3 Commits (fix/lambda-parameter-syntax)