- class QDataWidgetMapper#
The
QDataWidgetMapper
class provides mapping between a section of a data model to widgets. More…Synopsis#
Properties#
currentIndexᅟ
- The current row or columnorientationᅟ
- The orientation of the modelsubmitPolicyᅟ
- The current submit policy
Methods#
def
__init__()
def
addMapping()
def
clearMapping()
def
currentIndex()
def
itemDelegate()
def
mappedSection()
def
mappedWidgetAt()
def
model()
def
orientation()
def
removeMapping()
def
rootIndex()
def
setModel()
def
setOrientation()
def
setRootIndex()
def
submitPolicy()
Virtual methods#
Slots#
Signals#
Note
This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE
Detailed Description#
Warning
This section contains snippets that were automatically translated from C++ to Python and may contain errors.
QDataWidgetMapper
can be used to create data-aware widgets by mapping them to sections of an item model. A section is a column of a model if the orientation is horizontal (the default), otherwise a row.Every time the current index changes, each widget is updated with data from the model via the property specified when its mapping was made. If the user edits the contents of a widget, the changes are read using the same property and written back to the model. By default, each widget’s user property is used to transfer data between the model and the widget. Since Qt 4.3, an additional
addMapping()
function enables a named property to be used instead of the default user property.It is possible to set an item delegate to support custom widgets. By default, a
QStyledItemDelegate
is used to synchronize the model with the widgets.Let us assume that we have an item model named
model
with the following contents:1
Qt Norway
Oslo
2
Qt Australia
Brisbane
3
Qt USA
Palo Alto
4
Qt China
Beijing
5
Qt Germany
Berlin
The following code will map the columns of the model to widgets called
mySpinBox
,myLineEdit
andmyCountryChooser
:mapper = QDataWidgetMapper() mapper.setModel(model) mapper.addMapping(mySpinBox, 0) mapper.addMapping(myLineEdit, 1) mapper.addMapping(myCountryChooser, 2) mapper.toFirst()
After the call to
toFirst()
,mySpinBox
displays the value1
,myLineEdit
displaysQt Norway
andmyCountryChooser
displaysOslo
. The navigational functionstoFirst()
,toNext()
,toPrevious()
,toLast()
andsetCurrentIndex()
can be used to navigate in the model and update the widgets with contents from the model.The
setRootIndex()
function enables a particular item in a model to be specified as the root index - children of this item will be mapped to the relevant widgets in the user interface.QDataWidgetMapper
supports two submit policies,AutoSubmit
andManualSubmit
.AutoSubmit
will update the model as soon as the current widget loses focus,ManualSubmit
will not update the model unlesssubmit()
is called.ManualSubmit
is useful when displaying a dialog that lets the user cancel all modifications. Also, other views that display the model won’t update until the user finishes all their modifications and submits.Note that
QDataWidgetMapper
keeps track of external modifications. If the contents of the model are updated in another module of the application, the widgets are updated as well.See also
- class SubmitPolicy#
This enum describes the possible submit policies a
QDataWidgetMapper
supports.Constant
Description
QDataWidgetMapper.AutoSubmit
Whenever a widget loses focus, the widget’s current value is set to the item model.
QDataWidgetMapper.ManualSubmit
The model is not updated until
submit()
is called.
Note
Properties can be used directly when
from __feature__ import true_property
is used or via accessor functions otherwise.- property currentIndexᅟ: int#
This property holds the current row or column.
The widgets are populated with with data from the row at
index
if the orientation is horizontal (the default), otherwise with data from the column atindex
.- Access functions:
- property orientationᅟ: Qt.Orientation#
This property holds the orientation of the model.
If the orientation is Qt::Horizontal (the default), a widget is mapped to a column of a data model. The widget will be populated with the model’s data from its mapped column and the row that
currentIndex()
points at.Use Qt::Horizontal for tabular data that looks like this:
1
Qt Norway
Oslo
2
Qt Australia
Brisbane
3
Qt USA
Silicon Valley
4
Qt China
Beijing
5
Qt Germany
Berlin
If the orientation is set to Qt::Vertical, a widget is mapped to a row. Calling
setCurrentIndex()
will change the current column. The widget will be populates with the model’s data from its mapped row and the column thatcurrentIndex()
points at.Use Qt::Vertical for tabular data that looks like this:
1
2
3
4
5
Qt Norway
Qt Australia
Qt USA
Qt China
Qt Germany
Oslo
Brisbane
Silicon Valley
Beijing
Berlin
Changing the orientation clears all existing mappings.
- Access functions:
- property submitPolicyᅟ: QDataWidgetMapper.SubmitPolicy#
This property holds the current submit policy.
Changing the current submit policy will revert all widgets to the current data from the model.
- Access functions:
Constructs a new
QDataWidgetMapper
with parent objectparent
. By default, the orientation is horizontal and the submit policy isAutoSubmit
.See also
Warning
This section contains snippets that were automatically translated from C++ to Python and may contain errors.
Adds a mapping between a
widget
and asection
from the model. Thesection
is a column in the model if the orientation is horizontal (the default), otherwise a row.For the following example, we assume a model
myModel
that has two columns: the first one contains the names of people in a group, and the second column contains their ages. The first column is mapped to theQLineEdit
nameLineEdit
, and the second is mapped to theQSpinBox
ageSpinBox
:mapper = QDataWidgetMapper() mapper.setModel(myModel) mapper.addMapping(nameLineEdit, 0) mapper.addMapping(ageSpinBox, 1)
Notes:
If the
widget
is already mapped to a section, the old mapping will be replaced by the new one.Only one-to-one mappings between sections and widgets are allowed. It is not possible to map a single section to multiple widgets, or to map a single widget to multiple sections.
See also
- addMapping(widget, section, propertyName)
- Parameters:
widget –
QWidget
section – int
propertyName –
QByteArray
Essentially the same as
addMapping()
, but adds the possibility to specify the property to use specifyingpropertyName
.See also
- clearMapping()#
Clears all mappings.
See also
- currentIndex()#
- Return type:
int
See also
Getter of property
currentIndexᅟ
.- currentIndexChanged(index)#
- Parameters:
index – int
This signal is emitted after the current index has changed and all widgets were populated with new data.
index
is the new current index.See also
Notification signal of property
currentIndexᅟ
.- itemDelegate()#
- Return type:
Returns the current item delegate.
See also
Returns the name of the property that is used when mapping data to the given
widget
.See also
Returns the section the
widget
is mapped to or -1 if the widget is not mapped.See also
Returns the widget that is mapped at
section
, or 0 if no widget is mapped at that section.See also
- model()#
- Return type:
Returns the current model.
See also
- orientation()#
- Return type:
See also
Getter of property
orientationᅟ
.Removes the mapping for the given
widget
.See also
- revert()#
Repopulates all widgets with the current data of the model. All unsubmitted changes will be lost.
See also
- rootIndex()#
- Return type:
Returns the current root index.
See also
- setCurrentIndex(index)#
- Parameters:
index – int
See also
Setter of property
currentIndexᅟ
.- setCurrentModelIndex(index)#
- Parameters:
index –
QModelIndex
Warning
This section contains snippets that were automatically translated from C++ to Python and may contain errors.
Sets the current index to the row of the
index
if the orientation is horizontal (the default), otherwise to the column of theindex
.Calls
setCurrentIndex()
internally. This convenience slot can be connected to the signal currentRowChanged() or currentColumnChanged() of another view’s selection model.The following example illustrates how to update all widgets with new data whenever the selection of a
QTableView
namedmyTableView
changes:mapper = QDataWidgetMapper() connect(myTableView.selectionModel(), QItemSelectionModel.currentRowChanged, mapper.setCurrentModelIndex)
See also
- setItemDelegate(delegate)#
- Parameters:
delegate –
QAbstractItemDelegate
Sets the item delegate to
delegate
. The delegate will be used to write data from the model into the widget and from the widget to the model, usingsetEditorData()
andsetModelData()
.Any existing delegate will be removed, but not deleted.
QDataWidgetMapper
does not take ownership ofdelegate
.The delegate also decides when to apply data and when to change the editor, using
commitData()
andcloseEditor()
.Warning
You should not share the same instance of a delegate between widget mappers or views. Doing so can cause incorrect or unintuitive editing behavior since each view connected to a given delegate may receive the
closeEditor()
signal, and attempt to access, modify or close an editor that has already been closed.See also
- setModel(model)#
- Parameters:
model –
QAbstractItemModel
Sets the current model to
model
. If another model was set, all mappings to that old model are cleared.See also
- setOrientation(aOrientation)#
- Parameters:
aOrientation –
Orientation
See also
Setter of property
orientationᅟ
.- setRootIndex(index)#
- Parameters:
index –
QModelIndex
Sets the root item to
index
. This can be used to display a branch of a tree. Pass an invalid model index to display the top-most branch.See also
- setSubmitPolicy(policy)#
- Parameters:
policy –
SubmitPolicy
See also
Setter of property
submitPolicyᅟ
.- submit()#
- Return type:
bool
Submits all changes from the mapped widgets to the model.
For every mapped section, the item delegate reads the current value from the widget and sets it in the model. Finally, the model’s submit() method is invoked.
Returns
true
if all the values were submitted, otherwise false.Note: For database models, QSqlQueryModel::lastError() can be used to retrieve the last error.
See also
- submitPolicy()#
- Return type:
See also
Getter of property
submitPolicyᅟ
.- toFirst()#
Populates the widgets with data from the first row of the model if the orientation is horizontal (the default), otherwise with data from the first column.
This is equivalent to calling
setCurrentIndex(0)
.See also
- toLast()#
Populates the widgets with data from the last row of the model if the orientation is horizontal (the default), otherwise with data from the last column.
Calls
setCurrentIndex()
internally.See also
- toNext()#
Populates the widgets with data from the next row of the model if the orientation is horizontal (the default), otherwise with data from the next column.
Calls
setCurrentIndex()
internally. Does nothing if there is no next row in the model.See also
- toPrevious()#
Populates the widgets with data from the previous row of the model if the orientation is horizontal (the default), otherwise with data from the previous column.
Calls
setCurrentIndex()
internally. Does nothing if there is no previous row in the model.See also