Take the ImGui suite at 3.24.0 - #30
Merged
Merged
Conversation
3.24.0 makes a graph settle in seconds rather than a minute and a half. The layout's velocity cap was low enough that a body needed seconds to travel the few hundred units to its place, so a freshly opened graph spent its first half minute as a tall narrow column with near-vertical links - correct, but not finished, and the part anyone actually watches. Measured on a graph the size of the Counter document it now reaches its settled shape about five times sooner and settles in much the same place. Behavioural change inside the layout, so nothing here changes but the pins. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D2KNUKr1xJPTEdDmeF2tQN
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
3.24.0 makes a graph settle in seconds rather than a minute and a half (ktsu-dev/ImGuiApp#365).
The layout's velocity cap was low enough that a body needed seconds to travel the few hundred units to its place. A freshly opened graph therefore spent its first half-minute as a tall narrow column with near-vertical links — not laid out wrongly, just unfinished, and unfinished is the part anyone actually watches.
Measured upstream on a graph the size of the
Counterdocument this editor now opens with:It now reaches that settled shape roughly five times sooner, and settles in much the same place.
Two related findings from the same investigation, for context: the horizontal spacing between levels was never the problem (it settles near the spring's rest length), and repulsion is still load-bearing — without it the graph collapses permanently into the same tall column.
What changed
Directory.Packages.propsonly — the six packages published from the ImGuiApp repo, 3.23.0 to 3.24.0:ktsu.ImGui.App,ktsu.ImGui.App.Testing,ktsu.ImGui.SyntaxHighlighting,ktsu.ImGui.Widgets,ktsu.ImGui.NodeEditor,ktsu.ForceDirectedLayout.Verification
cdf97a9, 11:09:56Z).dotnet build -c Releaseclean,Coder.Test329/329 against 3.24.0.Not verified visually: this environment is headless. This is the change most likely to be immediately obvious when you open the editor, since it changes how quickly the graph resolves rather than only where it ends up.
🤖 Generated with Claude Code
https://claude.ai/code/session_01D2KNUKr1xJPTEdDmeF2tQN
Generated by Claude Code