From 8b032fe423e854428c1c8324dcd0f8c6150b3503 Mon Sep 17 00:00:00 2001 From: Giuseppe D'Angelo Date: Thu, 13 Sep 2012 19:23:10 +0100 Subject: Make QSignalTransition take a pointer-to-const QObject The obvious idea is that a connect() happens behind the scenes. As QObject::connect takes a pointer-to-const, QSignalTransition should do that as well. TODO: the API becomes asymmetric in that it takes a "const QObject *" but returns a "QObject *". Reasoning is needed. Change-Id: I18d0436e7036eee851fd36d5b8ccda4a4757938f Reviewed-by: Thiago Macieira Reviewed-by: Stephen Kelly Reviewed-by: Eskil Abrahamsen Blomfeldt --- src/corelib/statemachine/qstate.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/corelib/statemachine/qstate.cpp') diff --git a/src/corelib/statemachine/qstate.cpp b/src/corelib/statemachine/qstate.cpp index 126fa3adf7..7d4081f2c3 100644 --- a/src/corelib/statemachine/qstate.cpp +++ b/src/corelib/statemachine/qstate.cpp @@ -348,7 +348,7 @@ void QState::addTransition(QAbstractTransition *transition) object, and returns the new QSignalTransition object. The transition has this state as the source, and the given \a target as the target state. */ -QSignalTransition *QState::addTransition(QObject *sender, const char *signal, +QSignalTransition *QState::addTransition(const QObject *sender, const char *signal, QAbstractState *target) { if (!sender) { -- cgit v1.2.3