Skip to content

Enable side panels by default and increase edge trigger size#2

Open
xdonu2x wants to merge 12 commits into
mainfrom
codex/explain-codebase-structure-to-newcomer
Open

Enable side panels by default and increase edge trigger size#2
xdonu2x wants to merge 12 commits into
mainfrom
codex/explain-codebase-structure-to-newcomer

Conversation

@xdonu2x
Copy link
Copy Markdown
Owner

@xdonu2x xdonu2x commented Feb 13, 2026

Motivation

  • Side panels were difficult to discover because the defaults hid them (leftEnabled/rightEnabled were false) and the edge hover trigger was only 2px, causing users to miss the activation area.
  • Provide a safe runtime fallback so older or partial user configs that omit the sidePanels object do not silently disable the feature.

Description

  • Enable side panels by default by setting leftEnabled and rightEnabled to true in both Commons/Settings.qml and Assets/settings-default.json.
  • Increase the default triggerSize from 2 to 8 in Commons/Settings.qml, Assets/settings-default.json, and the runtime fallback in Modules/MainScreen/SideWidgetPanel.qml so edge-hover activation is easier.
  • Add Modules/MainScreen/SideWidgetPanel.qml (new) which implements hover-reveal side panels, panel sizing, reveal/conceal timers, and loading of bar widgets for left/right sides.
  • Integrate two SideWidgetPanel instances into Modules/MainScreen/MainScreen.qml and extend the mask regions to include panel bodies and trigger zones so pointer and click-to-close behavior remain correct.

Testing

  • Validated Assets/settings-default.json parses successfully with python3 -c "import json; json.load(open('Assets/settings-default.json'))" (succeeded).
  • Searched and inspected code locations with rg/nl to confirm defaults and runtime fallbacks are present in Commons/Settings.qml, Assets/settings-default.json, and Modules/MainScreen/SideWidgetPanel.qml (succeeded).
  • Confirmed files staged and committed locally (commit message: Enable side panels by default and widen edge trigger).
  • No runtime QML execution tests were available in this environment, so UI behavior validation should be performed in a running instance to confirm visible panels and hover activation (not run).

Codex Task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant