{"version":"2.1.271","anchor":"new-settingsstatus-props-decoupled-from-context-click-to-f","canonical_anchor":"settings-panel-gains-mouse-wheel-scrolling-and-pane-click-aw","heading":"Settings dialog refactored to take explicit props, gains scrolling and click-to-select","tier":"notice","area":"Settings UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-settingsstatus-props-decoupled-from-context-click-to-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Settings dialog refactored to take explicit props, gains scrolling and click-to-select\n\nThe Settings dialog now takes mcpClients\/messages as explicit props instead of a bundled context object, and supports mouse-wheel scroll and click-to-select\n\n**Unclear.** The finding doesn't say what consumes the 'unclaimed pane click' event or what visible behavior it enables.\n\n**What**\n\n- The Settings\/Config dialog (and related Status\/Stats\/Usage views) now receive `mcpClients`, `messages`, `ideInstallationStatus`, and other data as explicit separate props, instead of a single bundled `context` object.\n\n- Several call sites were switched to use this updated component with the new explicit props.\n\n- The dialog now supports mouse-wheel scrolling, and gained click handling: an `unclaimedPaneClick` event routes clicks not claimed by a specific row into row selection\/activation, with the dialog content wrapped in a clickable container.\n\n**Why**\n\nThis reworks how the settings dialog gets its data (explicit props instead of a hidden bundled object) and adds mouse-wheel scrolling plus click-to-select interaction to the settings panel.\n\n- Area: Settings UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}