pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Siegfried Pammer	1b78c76215	Synchronize headless UI tests on idle and hit-tested clicks The headless UI tests synchronized with the application by pumping a fixed number of frames (39 loops of RunJobs/Delay across 19 files) and by pressing at a point computed once from a control's bounds. Both encode how fast the machine that wrote the test was: on the loaded Windows Debug CI agent the frame count comes up short and the point goes stale, which is the recurring timeout in the tree context-menu tests and the reason each such failure was repaired one test at a time. Waiters.WaitForIdleAsync replaces the frame loops. It observes the actual precondition - no dispatcher job queued at Background priority or above, no assembly still loading in the background sweep, a frame rendered - and requires it on two consecutive polls so a thread-pool continuation about to post back is caught as well. Window.ClickAsync replaces element-targeted MouseDown/MouseUp pairs. It re-resolves the target on every poll and presses only once the window's hit test at the click point answers with that target, reporting the point and what was hit instead on timeout. That diagnostic exposed one vacuous test: User_Click_On_Visible_Row_Does_Not_Recentre_Viewport clicked the centre of a row wider than the tree viewport, which lies under the decompiler text view, so its assertion held without the row ever being clicked. It now clamps the point to the viewport like the other tree-row clicks. Clicks at text positions and press-only gutter clicks stay raw; they do not target an element. Assisted-by: Claude:claude-fable-5:Claude Code	3 weeks ago
Siegfried Pammer	f53ca6d080	Drop redundant global:: qualifiers on ICSharpCode references The global:: prefixes existed because the test project's namespace ICSharpCode.ILSpy.Tests used to shadow the app's old top-level ILSpy namespace. With the UI code back under ICSharpCode.ILSpy there is nothing left to shadow, so plain fully qualified names resolve fine. Assisted-by: Claude:claude-fable-5: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	2ce4ccda05	Show search results in a grid with sortable column headers The search panel rendered hits in a bare ListBox with no headers, so the only ordering was the fixed fitness/name streaming order chosen at search time -- the user could not re-sort by Name, Location or Assembly. Replace the ListBox with the app's standard sortable Avalonia DataGrid (mirroring OpenFromGacDialog / MetadataTablePage): three template columns that keep the per-field icons, each with a SortMemberPath so clicking a header sorts by Name / Location / Assembly. No initial column sort is applied, so the default fitness ranking is preserved until the user clicks a header. The code-behind is unchanged: ListBox and DataGrid share the SelectingItemsControl surface, so the existing selection / activation / keyboard / middle-click handlers port as-is (verified by the existing search niceties tests now running against the DataGrid). Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago
Siegfried Pammer	b538e88be9	Add keyboard and mouse niceties to the search pane Restores the result-navigation gestures the pane shipped with before the port: Ctrl+T/M/S jump the picker to Type/Member/Constant, Down/Up arrow hand focus between the search box and the result list, and Ctrl+Enter or a middle-click open a result in a new document tab instead of reusing the active one. New-tab activation routes through the existing OpenNodeInNewTab so it matches the tree's open-in-new-tab behaviour. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago