pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Siegfried Pammer	18d960e6b9	Say what the code does instead of which app did it first A comment that justifies behaviour by pointing at the WPF front-end means nothing to someone reading the file cold: the reason is either already stated beside it or is not stated anywhere. Each of these now names the constraint itself - why navigation waits for pointer-release, why a signature block wraps, why the tree filter ignores the search term. Comments citing an external product's documented behaviour as the source of a rule are left alone; there the reference is the reason, not a memory of how the code arrived. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	1 month ago
Siegfried Pammer	4ff11dd796	Add a hover-only reference mode, distinct from local highlighting References had two behaviors encoded in one bool: navigable links, and "local" references that are non-navigable but highlight all occurrences on click. Synthesized dynamic members were routed through the latter, so they picked up the occurrence highlight even though each use is a distinct synthetic member with nothing to group. Model the three modes explicitly with a ReferenceMode enum on ReferenceSegment (Link / LocalHighlight / HoverOnly). Dynamic members, the dynamic constructor and the dynamic keyword now use HoverOnly: they still show a hover tooltip (BuildHoverContent resolves any IEntity reference regardless of mode) but get the arrow cursor, do not navigate, and do not highlight. Local variables keep LocalHighlight. Plumbed via a new isHoverOnly flag on ITextOutput.WriteLocalReference. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago
Christoph Wille	b153291cdf	Fix #3793 : stop accidental text selection after clicking a reference Clicking a reference left AvaloniaEdit's selection-drag mode stuck, so a subsequent mouse move (with no button held) extended a selection. AvaloniaEdit's SelectionMouseHandler captures the pointer and enters selection mode on press, and extends the selection on every move while that mode is active -- it keys off the mode, not whether a button is down. Only its bubble-phase PointerReleased handler resets the mode and releases the capture, and that handler early-returns when the event is already handled. The reference-click handler ran in the tunnel phase and marked the release handled before AvaloniaEdit saw it, so AvaloniaEdit's cleanup never ran. Move the release handler to the bubble phase so it runs after AvaloniaEdit has reset its state. AvaloniaEdit subscribes from the TextArea constructor, before this view attaches its handlers, so the ordering is deterministic and navigation can stay synchronous. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months 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	9352a58289	Navigate references on click-release so link text stays selectable Reference links navigated on pointer-press, which meant a press-drag over a link could never select its text -- the press fired navigation and handled the event before a selection could start. Move navigation to pointer-release and only follow the link when the pointer did not drag past the click threshold, matching the WPF view's mouse-up handling. A press-drag now selects link text like any other span. Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago