- edited description
- changed title to Redesign DataSourcePanel
- marked as major
Redesign DataSourcePanel & DataSource handling
- add QgsBrowser
- make DataSourceManager a QAbstractItemModel
- remove QgsMapLayer instances
- redesign Drag-and-Drop
- add spezialized filter modes, i.e. QAbstractListModels to fill QComboBoxes, e.g. with “classification raster layers”
- silent data source detect (no gdal/ogr warnings in case a path cannot be opened)
Comments (26)
-
reporter -
reporter - edited description
-
reporter - changed status to open
-
reporter Issue
#503was marked as a duplicate of this issue. -
reporter Issue
#514was marked as a duplicate of this issue. -
reporter imagecube: changed gui, fixed smaller issues removed datasource layers from hidden layers (addresses
#430)Signed-off-by: jakimowb benjamin.jakimow@geo.hu-berlin.de
→ <<cset c4d53d9047b7>>
-
reporter added HubFlowPyObjectTreeNode with own context menu addresses
#517addresses#430Signed-off-by: Benjamin Jakimow benjamin.jakimow@geo.hu-berlin.de benjamin.jakimow@geo.hu-berlin.de
→ <<cset ac4d2a082498>>
-
reporter @Andreas Janz I added a
HubFlowPyObjectTreeNode
toenmapbox/gui/datasourcemanager.py
. You can now implement the required actions to the context menuclass HubFlowPyObjectTreeNode(PyObjectTreeNode): def __init__(self, *args, **kwds): super().__init__(*args, **kwds) def populateContextMenu(self, menu: QMenu): # implement your context menu actions here if isinstance(self.mPyObject, np.ndarray): a = menu.addAction('todo: Copy to clipboard')
-
Thanks @Benjamin Jakimow , shall I edit the
HubFlowPyObjectTreeNode
class and add the functionality? Or do I need to subclass? -
reporter It’s already a subclass of PyQbjectTreeNode, so just enhance it as you like.
-
- changed status to resolved
-
reporter - changed status to open
-
reporter - changed title to Redesign DataSourcePanel & DataSource handling
-
Thats kind of an ongoing issue. Note sure if we should better break it up into subissues that can actually be resolved. TBD
-
reporter → <<cset c1cd21069063>>
-
- changed version to 3.10
-
reporter addresses
#430re-design of data source handling added new DataSourceManager(TreeModel), DataSourceFactory, DataSources based on QgsDataItems→ <<cset b26b38b4894f>>
-
reporter addresses
#430re-design of data source handling WIP: refactoring gui.datasources→ <<cset 4197f8e315e9>>
-
reporter addresses
#430re-design of data source handling WIP: refactoring gui.datasources→ <<cset 762017148b9b>>
-
reporter addresses
#430refactored DataSourceManager DataSourceManager is not a TreeModel DataSources now QgsDataItem based DataSources do not store permanent QgsMapLayers moved datasource related classes to enmapbox.gui.datasources moved dock view related classes to enmapbox.gui.dataviews (rename docks to views in future?) simplified several routines→ <<cset 4b03727679cc>>
-
reporter addresses
#430re-design of data source handling added new DataSourceManager(TreeModel), DataSourceFactory, DataSources based on QgsDataItems→ <<cset b26b38b4894f>>
-
reporter addresses
#430re-design of data source handling WIP: refactoring gui.datasources→ <<cset 4197f8e315e9>>
-
reporter addresses
#430re-design of data source handling WIP: refactoring gui.datasources→ <<cset 762017148b9b>>
-
reporter addresses
#430refactored DataSourceManager DataSourceManager is not a TreeModel DataSources now QgsDataItem based DataSources do not store permanent QgsMapLayers moved datasource related classes to enmapbox.gui.datasources moved dock view related classes to enmapbox.gui.dataviews (rename docks to views in future?) simplified several routines→ <<cset 4b03727679cc>>
-
reporter - changed status to resolved
-
- removed version
Removing version: 3.10 (automated comment)
- Log in to comment