Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 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. 📝 WalkthroughWalkthroughThe dock frame now recalculates its current index when the tab count changes and returns zero when no tabs or C++ frame are available. Each dock tab also gains a middle-button handler that requests Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to Middle-click resolves to the Close action, removes the dock, and selects the preceding tab. No actionable merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Resolves: musescore/MuseScore#35121
Middle-clicking a panel tab now closes that panel, as middle-click already does for score tabs.
Behaviour changes:
dock/set-openwith that panel'sdock_name), so the panel's open state and the menu check stay in sync.DockFrame.qmlnow re-evaluatesprv.currentIndexwhen the number of tabs changes. Previously, closing a tab before the current one left no title highlighted, becausecurrentIndexwent stale. This also affects the existing context menu "Close".