* Enable surface reordering support. Automatically update surface in view ordering based on surface collection ordering
* Remove obsolete code
* Enable drag'n'drop support for surfaces within a surface collection. Still missing the collection update part.
* Bring back code lost in prev. commit
* Add code to accept drops in surface collections. Keep view in sync.
* Add command for adding additional surface folders.
* Make sure we use the current surface collection as our parent when importing
* Enable name editing.
Make sure we use the correct surface collection when importing/creating surfaces
* More work on getting surface collections working.
* Clean up naming
* Make sure name for surfaceinviewcollection is read only
* Support drawing surfaces from subcollections, too
* Allow deleting subfolders.
Fix legends in view
* Refactor topmost flag for surface collections.
* Fix reload surface to work in all subfolders, too
Add copy surface skeleton. Actual copy operation is still missing
* Add support for copying surfaces
* Remove possibility to choose I and J slice directions for grid case surfaces.
* Fix warnings.
* Make sure we create the surface folder at the correct level
* More warning fix
* Use XML serialization for copy operation
* Fix missing delete
* Fix typo
* Remove unnecessary method.
* Add reload command to surface context menus. Still missing the part that actually reloads the data.
* Add additional check for null ptr to avoid crash
* Surfaces: implements reload command in context menu to reload surface data from its source (i.e. a file).
Rename function names to better show what they are actually doing
Refactor a bit to give all RimSurface subclasses the same interface for reloading data.
Also makes sure new RimGridCaseSurface instances are shown by default in the view(s)
* Fixes by clang-format
* Include offset and slice index in surface name shown in project explorer
* Allow importing the same file multiple times
* Disable lighting for surfaces, as it doesn't look good for now. Fixes#6084
* Surfaces: Remove depth offset setting from view. Add slider to depth offset edit for surface
* Create new surfaces only on collection context menu
* Make sure tree view icon is enabled/disabled when the check box is clicked
* Fix depth offset for grid case surfaces, missing base function call.
* Make public method .. public.
* Add reload command to surface context menus. Still missing the part that actually reloads the data.
* Add additional check for null ptr to avoid crash
* Surfaces: implements reload command in context menu to reload surface data from its source (i.e. a file).
Rename function names to better show what they are actually doing
Refactor a bit to give all RimSurface subclasses the same interface for reloading data.
Also makes sure new RimGridCaseSurface instances are shown by default in the view(s)
* Fixes by clang-format
* Include offset and slice index in surface name shown in project explorer
* Allow importing the same file multiple times
* Disable lighting for surfaces, as it doesn't look good for now. Fixes#6084
* Surfaces: Remove depth offset setting from view. Add slider to depth offset edit for surface
* Create new surfaces only on collection context menu
* Make sure tree view icon is enabled/disabled when the check box is clicked
* Fix depth offset for grid case surfaces, missing base function call.
* Make public method .. public.
* Fixes by clang-format
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- restructured according to issue
- but issue indicate export of K-layer only despite RimGridCaseSurface
did support I/ slices, too?
- if so, test and possibly extend RimGridCaseSurface methods
extractDataFromGrid() and getStructGridIndex()
- need to check whether all offsets are taken care of
Work in progress:
- lacks support of views other than Eclipse views
- signature of RicImportFormationNamesFeature::importFormationFiles()
- reconsideration of variable names
* Currently nothing happens in this case, because we insert the dragged item
after the target.
* On balance it seems more intuitive to swap the items in this particular case
even if it is slightly against the regular drag operations.
