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	2 weeks 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	0826bae4a5	Record fast distinct navigations instead of collapsing them NavigationHistory.Record's 0.5s debounce collapsed ANY two selections inside the window -- including two DIFFERENT nodes -- so a navigation whose decompile finished quickly (cheap targets, or a fast machine) never pushed the previous node onto the back stack, silently losing history. Its real purpose is only to swallow the double-fire a single click produces (SelectedItems.CollectionChanged + SelectedItem PropertyChanged, same node) and tree-refresh re-selects, so gate the collapse on the rapid entry being equal to the current one; a distinct node now records normally. The view-state/navigation tests navigate between two cheap namespace nodes (a C# namespace decompiles to just its "// Some.Name.Space" line) instead of decompiling CoreLib types in full -- fast enough for the headless 15s budget on slow CI runners, and a direct regression test for the collapse bug above. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago
Siegfried Pammer	96d50e2b5b	Run long operations in their own frozen tab Project/solution export, PDB generation, Create Diagram and Extract Package all ran via RunWithCancellation on the active preview tab -- whose cancellation token tree-node navigation cancels. So selecting any node while one of these ran killed it: you couldn't browse while an export was in progress. Add DockWorkspace.RunInNewTabAsync, which opens a new frozen document tab (its own decompile/cancellation scope, never the navigation target), runs the work there, and shows the report in it. Route the long-running command sites through it. A frozen tab is immune to the selection-driven re-decompile, so navigation can no longer cancel the work -- and the report opens in its own tab instead of replacing the current view. The single-node Save Code path intentionally stays on the active tab (matches the prior version and is quick). Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago