Repository navigation
PolylinePlot - reworking cancel logic - #343
mathesoncalum wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughPolylinePlot no longer inherits Asyncable, Actionable, or Contextable, and it no longer registers an action://cancel handler. The class now exposes the invokable cancelEdit() method, which clears hover state and resets the gesture. The dragCancelled signal and init() method were removed. cancelEdit() does not emit dragCancelled. Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The change moves cancel handling from an action registration to an explicit cancelEdit() method. The repository has no in-tree consumers, so no concrete merge risk is evident. The author already notes that Audacity must migrate. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Description checkExplanation The description explains the motivation and proposed change, and it includes the AI-assistance disclosure and build configuration. However, it omits the required Resolves issue reference and most of the template checklist. Resolution Add a GitHub issue number or link after “Resolves:”. Complete each required checklist item accurately, including the CLA, title, commit messages, coding rules, build and testing, prior attempts, and unnecessary changes. Complete the unit-test item if applicable. The AI-assistance item and tool list are already present. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
5c731c3 to
f5c7521
Compare
The idea here is that
PolylinePlotshould know nothing about actions etc. If a cancel action is called somewhere in the app, we should instead actively call acancelEditmethod on the polyline. In MuseScore Studio this looks like this, the solution for Audacity will look a bit different since the polylines are QML-based (this is a breaking change for Audacity sinceinitno longer exists).Cursor 2.5 & Claude Opus 5.5 (used for autocomplete and reviewing).
Build configuration
audacity: audacity/audacity/master
audacity platforms: linux_x64
musescore: musescore/MuseScore/main
musescore platforms: linux_x64