-
Notifications
You must be signed in to change notification settings - Fork 326
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
Reorder nodes after connecting. #8494
Comments
i think this would benefit from waiting for AST edits first |
Also keep in mind that the cycle can involve arbitrary number of nodes:
|
Paweł Grabarz reports a new STANDUP for yesterday (2024-01-11): Progress: Added tests, fixed edits from initial empty function state and when deleting multiple nodes at once. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for yesterday (2024-01-15): Progress: Reviewed Selection Widget: shorten entries #8727 which is now merged. Working on feedback from PR for "Reorder nodes after connecting" story It should be finished by 2024-01-19. Next Day: Next day I will be working on the #8387 task. Finish "Reorder nodes after connecting" story. After that other GUI2 defects as found. Then back to Process for simple exporting icons from Figma. |
…placeholders (#8731) - Correctly applying code edits when connecting to argument placeholders or disconnecting existing arguments. - Prevented the placeholders from temporarily flickering right after the edit operation. - Rewritten the placeholder argument placing logic to match the old GUI exactly - the argument should never move right after being connected. - Fixes #8494 - Fixed some cases of ports either not existing, or existing where they shouldn't.
Paweł Grabarz reports a new STANDUP for the provided date (2023-12-28): Progress: Debugging AST updates, trying to understand failing widget update operations. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for the provided date (2024-01-03): Progress: Started implementing node reordering. Started 360 Feedback. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for the provided date (2024-01-04): Progress: Reordering blocked by incorrect AST update handling, had a meeting about AST design details. Finished 360 Feedback. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for the provided date (2024-01-09): Progress: Continuing work on reordering after necessary AST manipulation fixes have landed. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for the provided date (2024-01-10): Progress: Finished initial implementation and opened a PR. It should be finished by 2024-01-19. |
Paweł Grabarz reports a new STANDUP for the provided date (2024-01-12): Progress: Working on feedback from PR for "Reorder nodes after connecting" story It should be finished by 2024-01-19. |
After #8367
After connecting node, we must sure that for each connection, the target node will be after the source node in the code (unless there is a cycle)
The text was updated successfully, but these errors were encountered: