sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-02-28 00:17:30 -05:00
Code Issues Packages Projects Releases Wiki Activity
QGIS/python/gui/auto_generated/qgsfeatureselectiondlg.sip.in

67 lines
2.0 KiB
Plaintext
Raw Normal View History

sipify gui part 3
2017-05-23 14:44:34 +02:00
/************************************************************************
* This file has been generated automatically from *
* *
* src/gui/qgsfeatureselectiondlg.h *
* *
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
************************************************************************/
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
[sipify] handle constrained annotation
2017-05-24 10:26:03 +02:00
// This is required for the ConvertToSubClassCode to work properly
// so RTTI for casting is available in the whole module.
%ModuleCode
#include "qgsfeatureselectiondlg.h"
%End
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
class QgsFeatureSelectionDlg : QDialog
{
sipify gui part 3
2017-05-23 14:44:34 +02:00
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
%TypeHeaderCode
#include "qgsfeatureselectiondlg.h"
%End
%ConvertToSubClassCode
sipify gui part 3
2017-05-23 14:44:34 +02:00
if ( qobject_cast<QgsFeatureSelectionDlg *>( sipCpp ) )
sipType = sipType_QgsFeatureSelectionDlg;
else
sipType = 0;
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
%End
public:
Swap missing 0->nullptr and add missing overrides
2017-12-12 11:44:10 +10:00
[sip] align pointer and reference in blacklisted files this will facilitate sip diff checking
2017-05-01 16:42:33 +02:00
explicit QgsFeatureSelectionDlg( QgsVectorLayer *vl, QgsAttributeEditorContext &context, QWidget *parent /TransferThis/ = 0 );
Swap missing 0->nullptr and add missing overrides
2017-12-12 11:44:10 +10:00
%Docstring
Constructor for QgsFeatureSelectionDlg
%End
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
[sip] align pointer and reference in blacklisted files this will facilitate sip diff checking
2017-05-01 16:42:33 +02:00
const QgsFeatureIds &selectedFeatures();
sipify gui part 3
2017-05-23 14:44:34 +02:00
%Docstring
Add "get ..." to doxygen compliance blacklist Should be "gets ..." for consistent tense, or better yet "returns ..." for consistency.
2018-05-26 18:44:30 +10:00
Gets the selected features
run sipify
2017-12-15 10:36:55 -04:00
:return: The selected feature ids
sipify gui part 3
2017-05-23 14:44:34 +02:00
%End
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
[sip] align pointer and reference in blacklisted files this will facilitate sip diff checking
2017-05-01 16:42:33 +02:00
void setSelectedFeatures( const QgsFeatureIds &ids );
sipify gui part 3
2017-05-23 14:44:34 +02:00
%Docstring
run sipify
2017-12-15 10:36:55 -04:00
Set the selected features
run sipify
2017-12-15 21:36:08 -04:00
run sipify
2017-12-15 10:36:55 -04:00
:param ids: The feature ids to select
sipify gui part 3
2017-05-23 14:44:34 +02:00
%End
Make sure QgsFeatureSelectionDlg does not outgrow the window Fixes #20338 - Can not scroll through attribute list in dialog window when linking existing child features
2018-11-03 15:27:38 +01:00
protected:
virtual void showEvent( QShowEvent *event );
%Docstring
Make sure the dialog does not grow too much
%End
[FEATURE] Add N:M relation editing possibilities This adds the possibility to manage data on a normalized relational database in N:M relations. On the relation editor in a form, the tools to add, delete, link and unlink work (also) on the linking table if a relation is visualized as N:M relation. Configuration is done through the fields tab where on the relation a second relation can be chosen (if there is a suitable relation in terms of a second relation on the linking table). Limitations =========== QGIS is not a database management system. It is based on assumptions about the underlying database system. In particular it expects * A `ON DELETE CASCADE` or similar measure on the second relation * Does not take care of setting the primary key when adding features. Either users need to be instructed to set them manually or - if it's a database derived value - the layers need to be in transaction mode (currently only activatable through the API)
2015-12-01 10:04:20 +01:00
};
sipify gui part 3
2017-05-23 14:44:34 +02:00
/************************************************************************
* This file has been generated automatically from *
* *
* src/gui/qgsfeatureselectiondlg.h *
* *
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
************************************************************************/
Reference in New Issue Copy Permalink