| 1 | /****************************************************************************
|
|---|
| 2 | **
|
|---|
| 3 | ** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).
|
|---|
| 4 | ** Contact: Qt Software Information ([email protected])
|
|---|
| 5 | **
|
|---|
| 6 | ** This file is part of the QtGui module of the Qt Toolkit.
|
|---|
| 7 | **
|
|---|
| 8 | ** $QT_BEGIN_LICENSE:LGPL$
|
|---|
| 9 | ** Commercial Usage
|
|---|
| 10 | ** Licensees holding valid Qt Commercial licenses may use this file in
|
|---|
| 11 | ** accordance with the Qt Commercial License Agreement provided with the
|
|---|
| 12 | ** Software or, alternatively, in accordance with the terms contained in
|
|---|
| 13 | ** a written agreement between you and Nokia.
|
|---|
| 14 | **
|
|---|
| 15 | ** GNU Lesser General Public License Usage
|
|---|
| 16 | ** Alternatively, this file may be used under the terms of the GNU Lesser
|
|---|
| 17 | ** General Public License version 2.1 as published by the Free Software
|
|---|
| 18 | ** Foundation and appearing in the file LICENSE.LGPL included in the
|
|---|
| 19 | ** packaging of this file. Please review the following information to
|
|---|
| 20 | ** ensure the GNU Lesser General Public License version 2.1 requirements
|
|---|
| 21 | ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
|
|---|
| 22 | **
|
|---|
| 23 | ** In addition, as a special exception, Nokia gives you certain
|
|---|
| 24 | ** additional rights. These rights are described in the Nokia Qt LGPL
|
|---|
| 25 | ** Exception version 1.0, included in the file LGPL_EXCEPTION.txt in this
|
|---|
| 26 | ** package.
|
|---|
| 27 | **
|
|---|
| 28 | ** GNU General Public License Usage
|
|---|
| 29 | ** Alternatively, this file may be used under the terms of the GNU
|
|---|
| 30 | ** General Public License version 3.0 as published by the Free Software
|
|---|
| 31 | ** Foundation and appearing in the file LICENSE.GPL included in the
|
|---|
| 32 | ** packaging of this file. Please review the following information to
|
|---|
| 33 | ** ensure the GNU General Public License version 3.0 requirements will be
|
|---|
| 34 | ** met: http://www.gnu.org/copyleft/gpl.html.
|
|---|
| 35 | **
|
|---|
| 36 | ** If you are unsure which license is appropriate for your use, please
|
|---|
| 37 | ** contact the sales department at [email protected].
|
|---|
| 38 | ** $QT_END_LICENSE$
|
|---|
| 39 | **
|
|---|
| 40 | ****************************************************************************/
|
|---|
| 41 |
|
|---|
| 42 | #include "qabstractitemdelegate.h"
|
|---|
| 43 |
|
|---|
| 44 | #ifndef QT_NO_ITEMVIEWS
|
|---|
| 45 | #include <qabstractitemmodel.h>
|
|---|
| 46 | #include <qabstractitemview.h>
|
|---|
| 47 | #include <qfontmetrics.h>
|
|---|
| 48 | #include <qwhatsthis.h>
|
|---|
| 49 | #include <qtooltip.h>
|
|---|
| 50 | #include <qevent.h>
|
|---|
| 51 | #include <qstring.h>
|
|---|
| 52 | #include <qdebug.h>
|
|---|
| 53 | #include <private/qtextengine_p.h>
|
|---|
| 54 |
|
|---|
| 55 | QT_BEGIN_NAMESPACE
|
|---|
| 56 |
|
|---|
| 57 | /*!
|
|---|
| 58 | \class QAbstractItemDelegate
|
|---|
| 59 |
|
|---|
| 60 | \brief The QAbstractItemDelegate class is used to display and edit
|
|---|
| 61 | data items from a model.
|
|---|
| 62 |
|
|---|
| 63 | \ingroup model-view
|
|---|
| 64 | \mainclass
|
|---|
| 65 |
|
|---|
| 66 | A QAbstractItemDelegate provides the interface and common functionality
|
|---|
| 67 | for delegates in the model/view architecture. Delegates display
|
|---|
| 68 | individual items in views, and handle the editing of model data.
|
|---|
| 69 |
|
|---|
| 70 | The QAbstractItemDelegate class is one of the \l{Model/View Classes}
|
|---|
| 71 | and is part of Qt's \l{Model/View Programming}{model/view framework}.
|
|---|
| 72 |
|
|---|
| 73 | To render an item in a custom way, you must implement paint() and
|
|---|
| 74 | sizeHint(). The QItemDelegate class provides default implementations for
|
|---|
| 75 | these functions; if you do not need custom rendering, subclass that
|
|---|
| 76 | class instead.
|
|---|
| 77 |
|
|---|
| 78 | We give an example of drawing a progress bar in items; in our case
|
|---|
| 79 | for a package management program.
|
|---|
| 80 |
|
|---|
| 81 | \image widgetdelegate.png
|
|---|
| 82 |
|
|---|
| 83 | We create the \c WidgetDelegate class, which inherits from
|
|---|
| 84 | QStyledItemDelegate. We do the drawing in the paint() function:
|
|---|
| 85 |
|
|---|
| 86 | \snippet doc/src/snippets/widgetdelegate.cpp 0
|
|---|
| 87 |
|
|---|
| 88 | Notice that we use a QStyleOptionProgressBar and initialize its
|
|---|
| 89 | members. We can then use the current QStyle to draw it.
|
|---|
| 90 |
|
|---|
| 91 | To provide custom editing, there are two approaches that can be
|
|---|
| 92 | used. The first approach is to create an editor widget and display
|
|---|
| 93 | it directly on top of the item. To do this you must reimplement
|
|---|
| 94 | createEditor() to provide an editor widget, setEditorData() to populate
|
|---|
| 95 | the editor with the data from the model, and setModelData() so that the
|
|---|
| 96 | delegate can update the model with data from the editor.
|
|---|
| 97 |
|
|---|
| 98 | The second approach is to handle user events directly by reimplementing
|
|---|
| 99 | editorEvent().
|
|---|
| 100 |
|
|---|
| 101 | \sa {model-view-programming}{Model/View Programming}, QItemDelegate,
|
|---|
| 102 | {Pixelator Example}, QStyledItemDelegate, QStyle
|
|---|
| 103 | */
|
|---|
| 104 |
|
|---|
| 105 | /*!
|
|---|
| 106 | \enum QAbstractItemDelegate::EndEditHint
|
|---|
| 107 |
|
|---|
| 108 | This enum describes the different hints that the delegate can give to the
|
|---|
| 109 | model and view components to make editing data in a model a comfortable
|
|---|
| 110 | experience for the user.
|
|---|
| 111 |
|
|---|
| 112 | \value NoHint There is no recommended action to be performed.
|
|---|
| 113 |
|
|---|
| 114 | These hints let the delegate influence the behavior of the view:
|
|---|
| 115 |
|
|---|
| 116 | \value EditNextItem The view should use the delegate to open an
|
|---|
| 117 | editor on the next item in the view.
|
|---|
| 118 | \value EditPreviousItem The view should use the delegate to open an
|
|---|
| 119 | editor on the previous item in the view.
|
|---|
| 120 |
|
|---|
| 121 | Note that custom views may interpret the concepts of next and previous
|
|---|
| 122 | differently.
|
|---|
| 123 |
|
|---|
| 124 | The following hints are most useful when models are used that cache
|
|---|
| 125 | data, such as those that manipulate data locally in order to increase
|
|---|
| 126 | performance or conserve network bandwidth.
|
|---|
| 127 |
|
|---|
| 128 | \value SubmitModelCache If the model caches data, it should write out
|
|---|
| 129 | cached data to the underlying data store.
|
|---|
| 130 | \value RevertModelCache If the model caches data, it should discard
|
|---|
| 131 | cached data and replace it with data from the
|
|---|
| 132 | underlying data store.
|
|---|
| 133 |
|
|---|
| 134 | Although models and views should respond to these hints in appropriate
|
|---|
| 135 | ways, custom components may ignore any or all of them if they are not
|
|---|
| 136 | relevant.
|
|---|
| 137 | */
|
|---|
| 138 |
|
|---|
| 139 | /*!
|
|---|
| 140 | \fn void QAbstractItemDelegate::commitData(QWidget *editor)
|
|---|
| 141 |
|
|---|
| 142 | This signal must be emitted when the \a editor widget has completed
|
|---|
| 143 | editing the data, and wants to write it back into the model.
|
|---|
| 144 | */
|
|---|
| 145 |
|
|---|
| 146 | /*!
|
|---|
| 147 | \fn void QAbstractItemDelegate::closeEditor(QWidget *editor, QAbstractItemDelegate::EndEditHint hint)
|
|---|
| 148 |
|
|---|
| 149 | This signal is emitted when the user has finished editing an item using
|
|---|
| 150 | the specified \a editor.
|
|---|
| 151 |
|
|---|
| 152 | The \a hint provides a way for the delegate to influence how the model and
|
|---|
| 153 | view behave after editing is completed. It indicates to these components
|
|---|
| 154 | what action should be performed next to provide a comfortable editing
|
|---|
| 155 | experience for the user. For example, if \c EditNextItem is specified,
|
|---|
| 156 | the view should use a delegate to open an editor on the next item in the
|
|---|
| 157 | model.
|
|---|
| 158 |
|
|---|
| 159 | \sa EndEditHint
|
|---|
| 160 | */
|
|---|
| 161 |
|
|---|
| 162 | /*!
|
|---|
| 163 | \fn void QAbstractItemDelegate::sizeHintChanged(const QModelIndex &index)
|
|---|
| 164 | \since 4.4
|
|---|
| 165 |
|
|---|
| 166 | This signal must be emitted when the sizeHint() of \a index changed.
|
|---|
| 167 |
|
|---|
| 168 | Views automatically connect to this signal and relayout items as necessary.
|
|---|
| 169 | */
|
|---|
| 170 |
|
|---|
| 171 |
|
|---|
| 172 | /*!
|
|---|
| 173 | Creates a new abstract item delegate with the given \a parent.
|
|---|
| 174 | */
|
|---|
| 175 | QAbstractItemDelegate::QAbstractItemDelegate(QObject *parent)
|
|---|
| 176 | : QObject(parent)
|
|---|
| 177 | {
|
|---|
| 178 |
|
|---|
| 179 | }
|
|---|
| 180 |
|
|---|
| 181 | /*!
|
|---|
| 182 | \internal
|
|---|
| 183 |
|
|---|
| 184 | Creates a new abstract item delegate with the given \a parent.
|
|---|
| 185 | */
|
|---|
| 186 | QAbstractItemDelegate::QAbstractItemDelegate(QObjectPrivate &dd, QObject *parent)
|
|---|
| 187 | : QObject(dd, parent)
|
|---|
| 188 | {
|
|---|
| 189 |
|
|---|
| 190 | }
|
|---|
| 191 |
|
|---|
| 192 | /*!
|
|---|
| 193 | Destroys the abstract item delegate.
|
|---|
| 194 | */
|
|---|
| 195 | QAbstractItemDelegate::~QAbstractItemDelegate()
|
|---|
| 196 | {
|
|---|
| 197 |
|
|---|
| 198 | }
|
|---|
| 199 |
|
|---|
| 200 | /*!
|
|---|
| 201 | \fn void QAbstractItemDelegate::paint(QPainter *painter, const QStyleOptionViewItem &option, const QModelIndex &index) const = 0;
|
|---|
| 202 |
|
|---|
| 203 | This pure abstract function must be reimplemented if you want to
|
|---|
| 204 | provide custom rendering. Use the \a painter and style \a option to
|
|---|
|
|---|