problem in sender()

hi friends,

i got a small problem ..

i have a graphicsItem :- backButton (text: f7) and
a graphicsItem :- forwardButton(text f6)

so if the user clicks on backButton i am emitting a signal

Code:

---

connect(backitem6, SIGNAL(closeSignal()), this, SLOT(goMainPage()));
 
/*and slot*/
if(sender() == backitem){
                /** operation for backitem**/
        }else if(sender() == forwarditem){
               /** operation for forward item **/
        }

---

this works fine ...

now i try shortcuts f6 and f7 .. so i override keyevents on graphicsview()

now how can i integrate the keypress with that signal closeSignal()

means both clicking and pressing f7 i have to call goMainPage() ..
and sender() also i have to manage ..

please give me any suggestion to handle this situation ..

just use a flag and set it when its the key event... check it before the sender() check

like this ...

Code:

---

if(sender() == backitem7 || setFlag == 1)

---

may be like this

Code:

---

void keyPressEvent()
{
  if("key press is magic F7")
  {
    flag = true;
    callSlot();
    flag=false;
  }
}
 
/*and slot*/
if(flag==true)
{
  //key event
}
else if(sender() == backitem)
{
                /** operation for backitem**/
}
else if(sender() == forwarditem)
{
               /** operation for forward item **/
 }

---

If you want that approach, then better use a parameter for your slot. If it is empty, check the sender().

Quote:

---

Originally Posted by Lykurg

If you want that approach, then better use a parameter for your slot. If it is empty, check the sender().

---

ya i also thought that,, but if this slot is connected to other signals and used somewhere else than its a problem...we can have the default parameter,,, but i dont remeber if it can be connected to the signal of zero parameters, if it is so then its ok.

Quote:

---

Originally Posted by MrDeath

ya i also thought that,, but if this slot is connected to other signals and used somewhere else than its a problem...we can have the default parameter,,, but i dont remeber if it can be connected to the signal of zero parameters, if it is so then its ok.

---

yes that slot goMainPage() is already connected to a void signal ...
so parameter slot() is not possible unless signal mapping ... but its very tedious process ..

its better to follow mr.death's way .... horror way ...

Quote:

---

its better to follow mr.death's way .... horror way ...

---

LOL.. i like when ppl follow me...muhahahahaha... long live the horror !

Hey, it's no problem:

Code:

---

public slots:
  void test(int i = 0);
// works with
QObject::connect(button, SIGNAL(clicked()), this, SLOT(test())); // then with default '0'
//or
test(23); // with i == 23

---

ya.. it really works!!!... time for me to go back to school :(

whats more instresting is that clicked(bool) connects with slot(int) :)

Quote:

---

Originally Posted by MrDeath

whats more instresting is that clicked(bool) connects with slot(int) :)

---

It's because a type cast is performed to find any matching function "test"

Quote:

---

Originally Posted by Lykurg

It's because a type cast is performed to find any matching function "test"

---

thx for the info... btw isnt bool==int in c++?

Quote:

---

Originally Posted by MrDeath

thx for the info... btw isnt bool==int in c++?

---

As I know that was true in the early times of C (before C99). In C++ bool is a native data type with a lot of implicit conversions.

Now i really need to go back to primary school..
thx