fix: Path tool requires a double click to insert a new point after having dragged another point#3805
Conversation
Summary of ChangesHello @Annonnymmousss, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a specific usability bug within the Path tool, preventing an unintended interaction where users had to double-click to add new points after performing a drag operation. The fix ensures a smoother and more intuitive workflow for path manipulation by correctly resetting an internal state. Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request fixes a bug where the path tool would require a double click to insert a new point after dragging another point. This was caused by the molding_segment state not being reset after a drag operation. The change correctly resets this flag. The suggested additional state reset for molding_info has been included to improve robustness and prevent similar issues.
5bb6104 to
52d2b38
Compare
…aving dragged another point
22e83f4 to
d80b353
Compare
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="editor/src/messages/tool/tool_messages/path_tool.rs">
<violation number="1" location="editor/src/messages/tool/tool_messages/path_tool.rs:2640">
P2: Missing reset of `temporary_adjacent_handles_while_molding`. Every other location that resets `molding_segment` and `molding_info` also resets this field (lines 2381, 2504). Omitting it here could leave stale handle data that affects overlay drawing or subsequent molding operations.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
closes https://discord.com/channels/731730685944922173/881073965047636018/1419544936986185838
supercede #3631