Skip to content

fix: phase 0 quick fixes for the usability plan - #131

Open
lachlangrose wants to merge 3 commits into
mainfrom
fix/phase-0-quick-fixes
Open

lachlangrose wants to merge 3 commits into
mainfrom
fix/phase-0-quick-fixes

Conversation

@lachlangrose

Copy link
Copy Markdown
Member

Summary

Phase 0 of the usability plan (docs/development/usability-plan.md). No change to the layout.

  • Add each toolbar action one time. Call initProcessing() one time.
  • Show the Fault Adjacency instruction labels.
  • Basal Contacts shows one message only.
  • Show success results in the message bar (new gui/messages.py) instead of a modal dialog: basal contacts, thickness, apply colours/age, save state.
  • Ask for confirmation before "Clear Stratigraphic Column".
  • Delete the unused topology_tab.ui, viewer_tab.ui and geological_history_tab.ui. export_tab.ui stays for the export step.

This branch also has the plan commit (docs: add a plan for a guided modelling workflow), because it is not on main yet.

Test plan

  • pytest tests in QGIS 3.42 (164 passed)
  • Check in QGIS: the toolbar shows each action one time, the adjacency legend is visible, and no modal dialog opens for a successful action

🤖 Generated with Claude Code

Describe the current usability problems, a step-based dock, a direct
interpolation entry, and derived data that is updated when its inputs
change. Split the work into phases.
Add each toolbar action one time and call initProcessing one time. Show the
fault adjacency instructions. Show one message for the basal contacts result.
Show success results in the message bar. Ask for confirmation before the
stratigraphic column is cleared. Delete the unused .ui files, and keep
export_tab.ui for the export step.
@lachlangrose
lachlangrose added this pull request to stack #139 October 7, 2026 14:06
QgsMessageBar.pushSuccess, pushInfo and pushWarning do not accept a
duration argument. This caused a TypeError when a tool showed a
success message.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant