1 | /****************************************************************************
|
---|
2 | **
|
---|
3 | ** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).
|
---|
4 | ** All rights reserved.
|
---|
5 | ** Contact: Nokia Corporation ([email protected])
|
---|
6 | **
|
---|
7 | ** This file is part of the QtCore module of the Qt Toolkit.
|
---|
8 | **
|
---|
9 | ** $QT_BEGIN_LICENSE:LGPL$
|
---|
10 | ** Commercial Usage
|
---|
11 | ** Licensees holding valid Qt Commercial licenses may use this file in
|
---|
12 | ** accordance with the Qt Commercial License Agreement provided with the
|
---|
13 | ** Software or, alternatively, in accordance with the terms contained in
|
---|
14 | ** a written agreement between you and Nokia.
|
---|
15 | **
|
---|
16 | ** GNU Lesser General Public License Usage
|
---|
17 | ** Alternatively, this file may be used under the terms of the GNU Lesser
|
---|
18 | ** General Public License version 2.1 as published by the Free Software
|
---|
19 | ** Foundation and appearing in the file LICENSE.LGPL included in the
|
---|
20 | ** packaging of this file. Please review the following information to
|
---|
21 | ** ensure the GNU Lesser General Public License version 2.1 requirements
|
---|
22 | ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
|
---|
23 | **
|
---|
24 | ** In addition, as a special exception, Nokia gives you certain additional
|
---|
25 | ** rights. These rights are described in the Nokia Qt LGPL Exception
|
---|
26 | ** version 1.1, included in the file LGPL_EXCEPTION.txt in this 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 have questions regarding the use of this file, please contact
|
---|
37 | ** Nokia at [email protected].
|
---|
38 | ** $QT_END_LICENSE$
|
---|
39 | **
|
---|
40 | ****************************************************************************/
|
---|
41 |
|
---|
42 | #include "qsignalmapper.h"
|
---|
43 | #ifndef QT_NO_SIGNALMAPPER
|
---|
44 | #include "qhash.h"
|
---|
45 | #include "qobject_p.h"
|
---|
46 |
|
---|
47 | QT_BEGIN_NAMESPACE
|
---|
48 |
|
---|
49 | class QSignalMapperPrivate : public QObjectPrivate
|
---|
50 | {
|
---|
51 | Q_DECLARE_PUBLIC(QSignalMapper)
|
---|
52 | public:
|
---|
53 | void _q_senderDestroyed() {
|
---|
54 | Q_Q(QSignalMapper);
|
---|
55 | q->removeMappings(q->sender());
|
---|
56 | }
|
---|
57 | QHash<QObject *, int> intHash;
|
---|
58 | QHash<QObject *, QString> stringHash;
|
---|
59 | QHash<QObject *, QWidget*> widgetHash;
|
---|
60 | QHash<QObject *, QObject*> objectHash;
|
---|
61 |
|
---|
62 | };
|
---|
63 |
|
---|
64 |
|
---|
65 | /*!
|
---|
66 | \class QSignalMapper
|
---|
67 | \brief The QSignalMapper class bundles signals from identifiable senders.
|
---|
68 |
|
---|
69 | \ingroup objectmodel
|
---|
70 |
|
---|
71 |
|
---|
72 | This class collects a set of parameterless signals, and re-emits
|
---|
73 | them with integer, string or widget parameters corresponding to
|
---|
74 | the object that sent the signal.
|
---|
75 |
|
---|
76 | The class supports the mapping of particular strings or integers
|
---|
77 | with particular objects using setMapping(). The objects' signals
|
---|
78 | can then be connected to the map() slot which will emit the
|
---|
79 | mapped() signal with the string or integer associated with the
|
---|
80 | original signalling object. Mappings can be removed later using
|
---|
81 | removeMappings().
|
---|
82 |
|
---|
83 | Example: Suppose we want to create a custom widget that contains
|
---|
84 | a group of buttons (like a tool palette). One approach is to
|
---|
85 | connect each button's \c clicked() signal to its own custom slot;
|
---|
86 | but in this example we want to connect all the buttons to a
|
---|
87 | single slot and parameterize the slot by the button that was
|
---|
88 | clicked.
|
---|
89 |
|
---|
90 | Here's the definition of a simple custom widget that has a single
|
---|
91 | signal, \c clicked(), which is emitted with the text of the button
|
---|
92 | that was clicked:
|
---|
93 |
|
---|
94 | \snippet doc/src/snippets/qsignalmapper/buttonwidget.h 0
|
---|
95 | \snippet doc/src/snippets/qsignalmapper/buttonwidget.h 1
|
---|
|
---|