summaryrefslogtreecommitdiffstats
path: root/examples/sql/doc/src/sqlwidgetmapper.qdoc
diff options
context:
space:
mode:
authorLiang Qi <liang.qi@qt.io>2016-11-17 14:15:53 +0100
committerLiang Qi <liang.qi@qt.io>2016-11-17 14:43:26 +0100
commite5ac4afbf954a3e1616ce8543d46ddc668d0374f (patch)
treebe6d97001edebd5cb74c64aaf0010f3cc76a7293 /examples/sql/doc/src/sqlwidgetmapper.qdoc
parente3ed95dd44b95b6e9361b562807e711d7ce5a58b (diff)
parent03c1a6ac717e3c5693653a5e294214056bda970e (diff)
Merge remote-tracking branch 'origin/5.8' into dev
Conflicts: mkspecs/features/mac/default_post.prf mkspecs/features/uikit/default_post.prf Change-Id: I2a6f783451f2ac9eb4c1a050f605435d2dacf218
Diffstat (limited to 'examples/sql/doc/src/sqlwidgetmapper.qdoc')
-rw-r--r--examples/sql/doc/src/sqlwidgetmapper.qdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/examples/sql/doc/src/sqlwidgetmapper.qdoc b/examples/sql/doc/src/sqlwidgetmapper.qdoc
index 42e14672c9..a0fc26a642 100644
--- a/examples/sql/doc/src/sqlwidgetmapper.qdoc
+++ b/examples/sql/doc/src/sqlwidgetmapper.qdoc
@@ -33,7 +33,7 @@
\brief The SQL Widget Mapper example shows how to use a map information from a
database to widgets on a form.
- \image sql-widget-mapper.png
+ \borderedimage sql-widget-mapper.png
In the \l{Combo Widget Mapper Example}, we showed how to use a named
mapping between a widget mapper and a QComboBox widget with a special
@@ -74,7 +74,7 @@
including values for the address types that correspond to the address
types are stored in a separate table.
- \image widgetmapper-sql-mapping-table.png
+ \borderedimage widgetmapper-sql-mapping-table.png
We create an "addresstype" table containing the identifiers used in the
"person" table and the corresponding strings:
@@ -93,7 +93,7 @@
used wherever the "typeid" is presented to the user. (See the
QSqlRelationalTableModel::setRelation() documentation for details.)
- \image widgetmapper-sql-mapping.png
+ \borderedimage widgetmapper-sql-mapping.png
The constructor of the \c Window class can be explained in three parts.
In the first part, we set up the model used to hold the data, then we set