1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345
|
/****************************************************************************
**
** Copyright (C) 2017 The Qt Company Ltd.
** Contact: https://www.qt.io/licensing/
**
** This file is part of the QtContacts module of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:LGPL$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and The Qt Company. For licensing terms
** and conditions see https://www.qt.io/terms-conditions. For further
** information use the contact form at https://www.qt.io/contact-us.
**
** GNU Lesser General Public License Usage
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 3 as published by the Free Software
** Foundation and appearing in the file LICENSE.LGPL3 included in the
** packaging of this file. Please review the following information to
** ensure the GNU Lesser General Public License version 3 requirements
** will be met: https://www.gnu.org/licenses/lgpl-3.0.html.
**
** GNU General Public License Usage
** Alternatively, this file may be used under the terms of the GNU
** General Public License version 2.0 or (at your option) the GNU General
** Public license version 3 or any later version approved by the KDE Free
** Qt Foundation. The licenses are as published by the Free Software
** Foundation and appearing in the file LICENSE.GPL2 and LICENSE.GPL3
** included in the packaging of this file. Please review the following
** information to ensure the GNU General Public License requirements will
** be met: https://www.gnu.org/licenses/gpl-2.0.html and
** https://www.gnu.org/licenses/gpl-3.0.html.
**
** $QT_END_LICENSE$
**
****************************************************************************/
#include "qcontactfetchhint.h"
#include "qcontactfetchhint_p.h"
#ifndef QT_NO_DATASTREAM
#include <QtCore/qdatastream.h>
#endif
#ifndef QT_NO_DEBUG_STREAM
#include <QtCore/qdebug.h>
#endif
QT_BEGIN_NAMESPACE_CONTACTS
/*!
\class QContactFetchHint
\inmodule QtContacts
\brief The QContactFetchHint class provides hints to the manager about which contact
information needs to be retrieved in an asynchronous fetch request or a synchronous
function call.
All of the hints may be ignored at the discretion of the manager, however if a manager
is able to optimize retrieval of contacts due to hints, it may do so. If a manager
ignores a hint, it must retrieve the full set of data that the hint refers to.
The fetch hint contains:
\list
\li a list of detail types which the client is interested
in (empty if interested in all detail types)
\li a list of relationship types which the client is interested in
(empty if interested in all relationships)
\li some optimization flags which allow the client to tell the backend if they are
not interested in any relationships, any action preferences, or any binary blobs (images etc).
\li a preferred size for any images, if the backend supports multiple sizes or scaling
\endlist
Important note: a client should not make changes to a contact which has been retrieved
using a fetch hint other than the default fetch hint. Doing so can result in information
loss when saving the contact back to the manager (as the "new" restricted contact will
replace the previously saved contact in the backend).
*/
/*!
\enum QContactFetchHint::OptimizationHint
This enum defines flags which may be set to inform the backend that the client does
not require certain information. The backend may safely ignore the hint, but then
must return the full set of information relating to the optimization hint.
\value AllRequired Tells the backend that all information is required
\value NoRelationships Tells the backend that the client does not require retrieved contacts to include a cache of relationships
\value NoActionPreferences Tells the backend that the client does not require retrieved contacts to include a cache of action preferences
\value NoBinaryBlobs Tells the backend that the client does not require retrieved contacts to include binary blobs
*/
/*!
Constructs a new contact fetch hint which requests that the backend fetch all information
*/
QContactFetchHint::QContactFetchHint()
: d(new QContactFetchHintPrivate)
{
}
/*!
Constructs a new contact fetch hint as a copy of \a other
*/
QContactFetchHint::QContactFetchHint(const QContactFetchHint &other)
: d(other.d)
{
}
/*!
Frees any memory in use by the fetch hint
*/
QContactFetchHint::~QContactFetchHint()
{
}
/*!
Assigns this fetch hint to be equal to the \a other fetch hint
*/
QContactFetchHint& QContactFetchHint::operator=(const QContactFetchHint& other)
{
d = other.d;
return *this;
}
/*!
Returns the list of detail types that identify which detail type
the manager should (at a minimum) retrieve when fetching contacts.
This hint may be ignored by the backend, in which case it will return the full set of details for
each contact retrieved.
\sa setDetailTypesHint()
*/
QList<QContactDetail::DetailType> QContactFetchHint::detailTypesHint() const
{
return d.constData()->m_typesHint;
}
/*!
Sets the list of detail types that identify which detail type
the manager should (at a minimum) retrieve when fetching contacts to \a types.
This hint may be ignored by the backend, in which case it will return the full set of details for
each contact retrieved.
\sa detailTypesHint()
*/
void QContactFetchHint::setDetailTypesHint(const QList<QContactDetail::DetailType> &types)
{
d->m_typesHint = types;
}
/*!
Returns the list of relationship types that the manager should (at a minimum) retrieve
when fetching contacts.
This hint may be ignored by the backend, in which case it will return the full set of
relationships for each contact retrieved.
\sa setRelationshipTypesHint(), QContact::relationships()
*/
QStringList QContactFetchHint::relationshipTypesHint() const
{
return d.constData()->m_relationshipsHint;
}
/*!
Sets the list of relationship types that the manager should (at a minimum) retrieve
when fetching contacts to \a relationshipTypes.
This hint may be ignored by the backend, in which case it will return the full set of
relationships for each contact retrieved.
\sa relationshipTypesHint(), QContact::relationships()
*/
void QContactFetchHint::setRelationshipTypesHint(const QStringList& relationshipTypes)
{
d->m_relationshipsHint = relationshipTypes;
}
/*!
Returns the preferred pixel dimensions for any images returned
by the manager for a given request. This hint may be ignored
by the manager.
This is useful when the backend supports multiple sizes of an
image (or the image is natively scaleable) in order to get an
image that will look good at the indicated dimensions.
The caller should be prepared for images of any dimensions,
in any case.
*/
QSize QContactFetchHint::preferredImageSize() const
{
return d.constData()->m_preferredImageSize;
}
/*!
Sets the preferred pixel dimensions for any images returned
by the manager for the given request to \a size. This hint
may be ignored by the manager.
This is useful when the backend supports multiple sizes of an
image (or the image is natively scaleable) in order to get an
image that will look good at the indicated dimensions.
The caller should be prepared for images of any dimensions,
in any case.
*/
void QContactFetchHint::setPreferredImageSize(const QSize& size)
{
d->m_preferredImageSize = size;
}
/*!
Returns the optimization hint flags specified by the client.
These hints may be ignored by the backend, in which case it will return
the full set of information accessible in a contact, including
relationships, action preferences, and binary blobs.
\sa setOptimizationHints()
*/
QContactFetchHint::OptimizationHints QContactFetchHint::optimizationHints() const
{
return d.constData()->m_optimizationHints;
}
/*!
Sets the optimization hint flags specified by the client to \a hints.
These hints may be ignored by the backend, in which case it will return
the full set of information accessible in a contact, including
relationships, action preferences, and binary blobs.
\sa optimizationHints()
*/
void QContactFetchHint::setOptimizationHints(OptimizationHints hints)
{
d->m_optimizationHints = hints;
}
/*!
Returns the number of results which the client considers to be the
maximum number of useful results. The client is only interested
in this number of results, so returning any more results
would be superfluous to the client's requirements.
Note that this fetch hint only affects operations where the
backend would return a list of contacts; this hint specifies
the maximum number of contacts in the list which would be useful
to the client. The backend may ignore this hint, in which case it
must return all contacts which would otherwise have been returned
as a result of the operation.
A negative value for count denotes that the client wishes to
retrieve all results. The default value is -1.
*/
int QContactFetchHint::maxCountHint() const
{
return d.constData()->m_maxCount;
}
/*!
Sets the maximum number of results which the client is interested in
to \a count. The client is only interested in this number of results,
so returning any more results would be superfluous to the client's
requirements. Note that this fetch hint only affects operations where
the backend would return a list of contacts; this hint specifies
the maximum number of contacts in the list which would be useful
to the client. The backend may ignore this hint, in which case it
must return all contacts which would otherwise have been returned
as a result of the operation.
A negative value for count denotes that the client wishes to
retrieve all results. The default value is -1.
*/
void QContactFetchHint::setMaxCountHint(int count)
{
count < 0 ? (d->m_maxCount = -1) : (d->m_maxCount = count);
}
#ifndef QT_NO_DATASTREAM
QDataStream& operator<<(QDataStream& out, const QContactFetchHint& hint)
{
quint8 formatVersion = 2; // Version of QDataStream format for QContactFetchHint
QList<quint32> detailTypeHintHelper;
foreach (QContactDetail::DetailType hintType, hint.detailTypesHint())
detailTypeHintHelper.append(static_cast<quint32>(hintType));
return out << formatVersion
<< detailTypeHintHelper
<< hint.relationshipTypesHint()
<< static_cast<quint32>(hint.optimizationHints())
<< hint.preferredImageSize()
<< hint.maxCountHint();
}
QDataStream& operator>>(QDataStream& in, QContactFetchHint& hint)
{
hint = QContactFetchHint();
quint8 formatVersion;
in >> formatVersion;
if (formatVersion == 1 || formatVersion == 2) {
QList<quint32> detailTypeHintsHelper;
QList<QContactDetail::DetailType> detailTypeHints;
QStringList relationshipTypeHints;
quint32 optimizations;
QSize dimensions;
in >> detailTypeHintsHelper >> relationshipTypeHints >> optimizations >> dimensions;
foreach (quint32 hintType, detailTypeHintsHelper)
detailTypeHints.append(QContactDetail::DetailType(hintType));
hint.setDetailTypesHint(detailTypeHints);
hint.setRelationshipTypesHint(relationshipTypeHints);
hint.setOptimizationHints(QContactFetchHint::OptimizationHints(optimizations));
hint.setPreferredImageSize(dimensions);
// version two also has a maximum fetch count hint.
if (formatVersion == 2) {
int maxCountHint = -1;
in >> maxCountHint;
hint.setMaxCountHint(maxCountHint);
}
} else {
in.setStatus(QDataStream::ReadCorruptData);
}
return in;
}
#endif
#ifndef QT_NO_DEBUG_STREAM
/*!
Outputs \a hint to the debug stream \a dbg
*/
QDebug operator<<(QDebug dbg, const QContactFetchHint& hint)
{
dbg.nospace() << "QContactFetchHint("
<< "detailTypeHint=" << hint.detailTypesHint() << ","
<< "relationshipTypesHint=" << hint.relationshipTypesHint() << ","
<< "optimizationHints=" << static_cast<quint32>(hint.optimizationHints()) << ","
<< "preferredImageSize=" << hint.preferredImageSize()
<< "maxCountHint=" << hint.maxCountHint()
<< ")";
return dbg.maybeSpace();
}
#endif
QT_END_NAMESPACE_CONTACTS
|