You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Project widgets were not remembering selected layers/fields and qgscombomaplayer/field combos lacked consistent column guessing from project layers.
Data persistence
Added widget_settings storage to ModellingDataManager (saved/loaded with project) for widget-specific selections.
Layer/field auto-guessing & restoration
Basal contacts, sorter, sampler, and thickness calculator widgets now use ColumnMatcher to suggest layers/fields and restore previous selections; guards added when layers are missing.
Thickness calculator passes required parameters and handles multi-part results, with a simple progress updater.
LoopStructural model setup widgets (DEM, Fault Layers, Stratigraphic Layers) now auto-guess layers/fields via ColumnMatcher, persist selections through widget_settings, and restore them on reopen (with missing-layer guards).
For every qgscombomaplayer combo box and field combo box ensure that the column matcher is used to guess the appropriate column from the current layers in the project. Also ensure that any selections of layers are stored in the project data. So that when the widgets are closed and reopened the same layers are selected. This can be managed through the data manager and the selections stored in a json. Feel free to suggest or use a different data structure to achieve the same purpose but ensure that the approach implemented is modular and can be extended.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
CopilotAI
changed the title
[WIP] Implement layer selection storage for combo boxesPersist and auto-guess layer/field selections across map2loop widgetsJan 26, 2026
@copilot can you do the same thing with the LoopStructural widget? e.g. all of the model set up
Added ColumnMatcher-based auto-guessing plus persistence/restore for the LoopStructural setup widgets (DEM, Fault Layers, Stratigraphic Layers). Changes are in 271ca04.
CopilotAI
changed the title
Persist and auto-guess layer/field selections across map2loop widgetsPersist and auto-guess layer/field selections across map2loop and LoopStructural setup widgetsJan 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Project widgets were not remembering selected layers/fields and qgscombomaplayer/field combos lacked consistent column guessing from project layers.
Data persistence
widget_settingsstorage toModellingDataManager(saved/loaded with project) for widget-specific selections.Layer/field auto-guessing & restoration
ColumnMatcherto suggest layers/fields and restore previous selections; guards added when layers are missing.ColumnMatcher, persist selections throughwidget_settings, and restore them on reopen (with missing-layer guards).Example (sampler widget guessing/persisting)
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.