Slot is being called multiple times every time a signal is emittedQt slot from thread called more than onceClicking a button once gives multiple eventsHow to fix the Method multiplying issue in Pyside2QFileSystemWatcher directoryChanged signal emitted twice when file is deletedslot is called multiple times when signal is emittedHow different slots are being called by the same button?Order of slots called on QObjectQt 4.5 - Is emitting signal a function call, or a thread, and does it blocks?What are the basic rules and idioms for operator overloading?Adding signals/slots (QObject) to QGraphicsItem: performance hit?Using emit vs calling a signal as if it's a regular function in QtImage Processing: Algorithm Improvement for 'Coca-Cola Can' RecognitionIs it OK to emit a signal from an object's destructor in Qt?How can I emit a signal from another class?Signals and Slots help QTQt Signal/Slots in one class but emitted from different threads
Would nuclear bombs be effective against clouds of nanites?
Giving a talk on a different topic than what we discussed
A variation on Caesar
At what point in time would humans notice a 21st century satellite observing them?
What spells can be countered?
Why did a shuttle astronaut have an open book during ascent?
Is a Senate trial required after the House impeaches a president?
What to do with a bent but not broken aluminum seat stay
Is this a pure function?
How to communicate faster than the system clock
Diophantine equation in Laurent polynomials
My mysterious "ruins" wander around and change on their own, what'd be a rational way for them to do that?
Why are boost/buck converters never fully integrated/all-in-one?
how to make a twisted wrapper
Was there a clearly identifiable "first computer" to use or demonstrate the use of virtual memory?
What is the source for pushing away the convert three times?
Passport expiration requirement for Jordan Visa
Fitting a large equation with gathered in table cell
What are standard cryptographic assumptions?
"Ich habe Durst" vs "Ich bin durstig": Which is more common?
Iodine tablet correct use and efficiency
Do physicists understand why time slows down the faster the velocity of an object?
Translation Golf XLIX - An Accurate Shot
Total I/O cost of a process
Slot is being called multiple times every time a signal is emitted
Qt slot from thread called more than onceClicking a button once gives multiple eventsHow to fix the Method multiplying issue in Pyside2QFileSystemWatcher directoryChanged signal emitted twice when file is deletedslot is called multiple times when signal is emittedHow different slots are being called by the same button?Order of slots called on QObjectQt 4.5 - Is emitting signal a function call, or a thread, and does it blocks?What are the basic rules and idioms for operator overloading?Adding signals/slots (QObject) to QGraphicsItem: performance hit?Using emit vs calling a signal as if it's a regular function in QtImage Processing: Algorithm Improvement for 'Coca-Cola Can' RecognitionIs it OK to emit a signal from an object's destructor in Qt?How can I emit a signal from another class?Signals and Slots help QTQt Signal/Slots in one class but emitted from different threads
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I am using one signal and slot connection in a block. My code as follows
in a.cpp
QObject::connect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
m_ptheFlange2Details->get();// one function inside which i am emiting
// GetFlang1DimAfterAnalysis() signal ;
QObject::disconnect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
Inside the get() function when this emit statement executes, the slot is called lots of times. Where as according to me it should call only once.
c++ qt qt4
add a comment
|
I am using one signal and slot connection in a block. My code as follows
in a.cpp
QObject::connect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
m_ptheFlange2Details->get();// one function inside which i am emiting
// GetFlang1DimAfterAnalysis() signal ;
QObject::disconnect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
Inside the get() function when this emit statement executes, the slot is called lots of times. Where as according to me it should call only once.
c++ qt qt4
4
Have you make sure thatconnect
is not called multiple times??!!! Please show us a little bit more code. In which functionconnect
anddisconnect
has been written??
– Ammar
Jun 11 '12 at 6:24
2
How many times isemit
called inget()
?
– cmannett85
Jun 11 '12 at 6:31
2
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
Check ifQObject::disconnect(...)
returnstrue
. If it does, then this part of the code is OK. You may have trouble inget()
, or elsewhere.
– Kuba Ober
Jun 11 '12 at 16:10
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39
add a comment
|
I am using one signal and slot connection in a block. My code as follows
in a.cpp
QObject::connect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
m_ptheFlange2Details->get();// one function inside which i am emiting
// GetFlang1DimAfterAnalysis() signal ;
QObject::disconnect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
Inside the get() function when this emit statement executes, the slot is called lots of times. Where as according to me it should call only once.
c++ qt qt4
I am using one signal and slot connection in a block. My code as follows
in a.cpp
QObject::connect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
m_ptheFlange2Details->get();// one function inside which i am emiting
// GetFlang1DimAfterAnalysis() signal ;
QObject::disconnect(m_ptheFlange2Details,SIGNAL(GetFlang1DimAfterAnalysis()),
this,SLOT(GetFlang1DimAftrAnalysis()));
Inside the get() function when this emit statement executes, the slot is called lots of times. Where as according to me it should call only once.
c++ qt qt4
c++ qt qt4
edited Oct 1 '15 at 17:07
Rick Smith
6,9919 gold badges61 silver badges75 bronze badges
6,9919 gold badges61 silver badges75 bronze badges
asked Jun 11 '12 at 6:20
KentaKenta
1,2044 gold badges24 silver badges50 bronze badges
1,2044 gold badges24 silver badges50 bronze badges
4
Have you make sure thatconnect
is not called multiple times??!!! Please show us a little bit more code. In which functionconnect
anddisconnect
has been written??
– Ammar
Jun 11 '12 at 6:24
2
How many times isemit
called inget()
?
– cmannett85
Jun 11 '12 at 6:31
2
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
Check ifQObject::disconnect(...)
returnstrue
. If it does, then this part of the code is OK. You may have trouble inget()
, or elsewhere.
– Kuba Ober
Jun 11 '12 at 16:10
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39
add a comment
|
4
Have you make sure thatconnect
is not called multiple times??!!! Please show us a little bit more code. In which functionconnect
anddisconnect
has been written??
– Ammar
Jun 11 '12 at 6:24
2
How many times isemit
called inget()
?
– cmannett85
Jun 11 '12 at 6:31
2
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
Check ifQObject::disconnect(...)
returnstrue
. If it does, then this part of the code is OK. You may have trouble inget()
, or elsewhere.
– Kuba Ober
Jun 11 '12 at 16:10
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39
4
4
Have you make sure that
connect
is not called multiple times??!!! Please show us a little bit more code. In which function connect
and disconnect
has been written??– Ammar
Jun 11 '12 at 6:24
Have you make sure that
connect
is not called multiple times??!!! Please show us a little bit more code. In which function connect
and disconnect
has been written??– Ammar
Jun 11 '12 at 6:24
2
2
How many times is
emit
called in get()
?– cmannett85
Jun 11 '12 at 6:31
How many times is
emit
called in get()
?– cmannett85
Jun 11 '12 at 6:31
2
2
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
Check if
QObject::disconnect(...)
returns true
. If it does, then this part of the code is OK. You may have trouble in get()
, or elsewhere.– Kuba Ober
Jun 11 '12 at 16:10
Check if
QObject::disconnect(...)
returns true
. If it does, then this part of the code is OK. You may have trouble in get()
, or elsewhere.– Kuba Ober
Jun 11 '12 at 16:10
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39
add a comment
|
1 Answer
1
active
oldest
votes
As stated in some of the comments, this is usually caused by calling the connect more the once. The slot will be called once for every time the connection is made. For example, the following code will result in slot()
being called 3 times when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
If you are doing connects in code that may be run more than once, it is generally a good idea to use Qt::UniqueConnection
as the 5th parameter. The following code will result in slot()
being called 1 time when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
I'm guessing the reason your code is not working correctly is because you are omitting the 5th parameter and connect defaults to Qt::DirectConnection
(for single threaded programs). This immediately calls the slot as if it were a function call. This means that it is possible for connect to be called again before the disconnect happens (if there are loops in your program).
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
add a comment
|
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f10975247%2fslot-is-being-called-multiple-times-every-time-a-signal-is-emitted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As stated in some of the comments, this is usually caused by calling the connect more the once. The slot will be called once for every time the connection is made. For example, the following code will result in slot()
being called 3 times when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
If you are doing connects in code that may be run more than once, it is generally a good idea to use Qt::UniqueConnection
as the 5th parameter. The following code will result in slot()
being called 1 time when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
I'm guessing the reason your code is not working correctly is because you are omitting the 5th parameter and connect defaults to Qt::DirectConnection
(for single threaded programs). This immediately calls the slot as if it were a function call. This means that it is possible for connect to be called again before the disconnect happens (if there are loops in your program).
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
add a comment
|
As stated in some of the comments, this is usually caused by calling the connect more the once. The slot will be called once for every time the connection is made. For example, the following code will result in slot()
being called 3 times when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
If you are doing connects in code that may be run more than once, it is generally a good idea to use Qt::UniqueConnection
as the 5th parameter. The following code will result in slot()
being called 1 time when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
I'm guessing the reason your code is not working correctly is because you are omitting the 5th parameter and connect defaults to Qt::DirectConnection
(for single threaded programs). This immediately calls the slot as if it were a function call. This means that it is possible for connect to be called again before the disconnect happens (if there are loops in your program).
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
add a comment
|
As stated in some of the comments, this is usually caused by calling the connect more the once. The slot will be called once for every time the connection is made. For example, the following code will result in slot()
being called 3 times when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
If you are doing connects in code that may be run more than once, it is generally a good idea to use Qt::UniqueConnection
as the 5th parameter. The following code will result in slot()
being called 1 time when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
I'm guessing the reason your code is not working correctly is because you are omitting the 5th parameter and connect defaults to Qt::DirectConnection
(for single threaded programs). This immediately calls the slot as if it were a function call. This means that it is possible for connect to be called again before the disconnect happens (if there are loops in your program).
As stated in some of the comments, this is usually caused by calling the connect more the once. The slot will be called once for every time the connection is made. For example, the following code will result in slot()
being called 3 times when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()));
If you are doing connects in code that may be run more than once, it is generally a good idea to use Qt::UniqueConnection
as the 5th parameter. The following code will result in slot()
being called 1 time when signal()
is emitted once.
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
connect(obj, SIGNAL(signal()), obj2, SLOT(slot()), Qt::UniqueConnection);
I'm guessing the reason your code is not working correctly is because you are omitting the 5th parameter and connect defaults to Qt::DirectConnection
(for single threaded programs). This immediately calls the slot as if it were a function call. This means that it is possible for connect to be called again before the disconnect happens (if there are loops in your program).
edited Aug 27 '13 at 18:32
answered Jun 12 '12 at 17:48
Rick SmithRick Smith
6,9919 gold badges61 silver badges75 bronze badges
6,9919 gold badges61 silver badges75 bronze badges
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
add a comment
|
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
if you are emitting a signal , then only the slot is being called right ?? it does not matter how many times you have used the connect statement .. could you please describe something on Qt::uniqueconnection ..since i am new to qt , so dont have more idea on it ..
– Kenta
Jun 14 '12 at 7:29
1
1
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
It does matter how many times you call connect unless you use Qt::UniqueConnection. If you are doing connects in a function, and you call that function more than once, you need to use Qt::UniqueConnection or your slot will get called multiple times. I edited my post to try to show that a little better.
– Rick Smith
Jun 14 '12 at 21:37
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
@Rick--Thankxxx
– Kenta
Jun 15 '12 at 5:11
add a comment
|
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f10975247%2fslot-is-being-called-multiple-times-every-time-a-signal-is-emitted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
Have you make sure that
connect
is not called multiple times??!!! Please show us a little bit more code. In which functionconnect
anddisconnect
has been written??– Ammar
Jun 11 '12 at 6:24
2
How many times is
emit
called inget()
?– cmannett85
Jun 11 '12 at 6:31
2
This code looks good.Now post the ugly part of your code!
– ScarCode
Jun 11 '12 at 9:35
Check if
QObject::disconnect(...)
returnstrue
. If it does, then this part of the code is OK. You may have trouble inget()
, or elsewhere.– Kuba Ober
Jun 11 '12 at 16:10
i am using only one emit statement inside get() , then how can this slot invoke for lots of time ??QObject::disconnect(--) also returns true . i am not able to understand whats the problem ... shall i go for QObject::uniqueconnection()
– Kenta
Jun 12 '12 at 11:39