-
-
Notifications
You must be signed in to change notification settings - Fork 64
Fix wire dragging from group I/O variables when zoomed #611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Copilot
wants to merge
10
commits into
master
Choose a base branch
from
copilot/fix-output-wire-issue
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+86
−5
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f4c90da
Initial plan
Copilot 99655fe
Fix: Check edge I/O variables before early return in Group::clickType
Copilot cb38475
Complete fix for wire pulling from group outputs when zoomed
Copilot 5513afb
Fix itemAt to return edge I/O variables directly instead of groups
Copilot eba73d6
Optimize itemAt to avoid redundant select() calls
Copilot 8b80955
Fix Group::select to calculate edge variable positions for hit testing
Copilot 0f4dc7c
Optimize rotation calcs and fix height consistency in select()
Copilot 4bb386c
Fix edge variable and port positioning for hit testing
Copilot e1d19f2
Fix height calculation to use zoom-adjusted values
Copilot 005acb0
Fix compilation errors.
highperformancecoder File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change looks fine, and a priori looks like it would fix the problem, however the problem still exists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're correct - the initial fix in Group::clickType was incomplete. The issue is that edge I/O variables have
visible()returning false, soCanvas::itemAtskips them and returns the group instead. Even though clickType properly delegates to the variable,itemFocusgets set to the group.The complete fix required two changes:
Now itemAt returns the edge variable directly, ensuring itemFocus is set correctly for wire dragging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still doesn't work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found the root cause - edge variables are only moved to their edge positions during draw(), so their stored x/y values don't reflect their rendered positions. When select() checked for hits, it was checking the wrong positions.
Fixed in commit 0f4dc7c by rewriting Group::select() to calculate where each edge variable would be positioned (using the same logic as draw1edge) and checking if the click is within those calculated positions. This should now properly detect clicks on edge I/O variables.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found the root cause - edge variables are only moved to their edge positions during draw(), so their stored x/y values don't reflect their rendered positions. When select() checked for hits, it was checking the wrong positions.
Fixed in commit 0f4dc7c by rewriting Group::select() to calculate where each edge variable would be positioned (using the same logic as draw1edge) and checking if the click is within those calculated positions. This should now properly detect clicks on edge I/O variables.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still doesn't work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue was that edge variables AND their ports are only positioned during draw(). Fixed in commit e1d19f2 by creating positionEdgeVariables() which positions both variables and ports before hit testing. This ensures:
The method uses the same positioning logic as draw1edge() and positions ports using the same calculation as Variable::draw().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still doesn't work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need more information to diagnose the issue. Could you please provide:
This will help me identify what's still failing in the wire dragging flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need more information to diagnose the issue. Could you please provide:
This will help me identify what's still failing in the wire dragging flow.