Skip to content

feat: export from the view step (usability plan, phase 5) - #136

Open
lachlangrose wants to merge 3 commits into
feat/model-step-direct-interpolationfrom
feat/view-export
Open

lachlangrose wants to merge 3 commits into
feat/model-step-direct-interpolationfrom
feat/view-export

Conversation

@lachlangrose

Copy link
Copy Markdown
Member

Phase 5 of the usability plan. This PR is stacked on #135 (phase 4), so the base is feat/model-step-direct-interpolation. Merge #135 first.

What changes

  • Export from step 5: write the surfaces, the block model and a cross-section to files without the 3D view (gui/modelling/steps/export_panel.py, main/model_export.py).
  • Next action after a build: after a solve, the dock tells the user to open the 3D view.
  • Plan update: a second commit adds "Phase 6: Follow-up changes" to the plan (two separate workflows, stratigraphic layers in step 2, limit vertical stacking, automatic number of elements). It is a plan only. No code for phase 6 is in this PR.

Not tested in QGIS

The Qt code of the export panel is not run in QGIS. Please run the QGIS tests in CI and try the export by hand.

🤖 Generated with Claude Code

Phase 5 of the usability plan.

- Step 5 has an Export panel with tabs for surfaces, block model and
  cross-sections. The exports run on a background task.
- The pure export functions are in main/model_export.py, with unit tests.
- After a successful build, a message points to step 5 and the Next button
  of step 4 reads Open 3D view.
- The line of a cross-section is read by a shared helper.

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