No, in my case the actions are absolutely the same. What I'm actually trying to do is to execute the same action on a different user/caller.
Here is my exact situation:
I have an action added in a context menu of some treeviews, that changes the icon of a treeviewitem.
So basically, what my action does is:
Qt Code: 
  1. treeItem->setIcon(0,QIcon(":/Icons/NewIcon.ico"))
To copy to clipboard, switch view to plain text mode 
Now in order to get to that "treeItem", I need to get the parent tree first. In my particular case, only one tree is visible at a time so I'm checking which tree is currently visible and then I'm working my way down to the "treeItem" and apply the action. But I don't like this approach. It seams logical to be able to determine who called the action and not relying on a visibility...
Maybe I'm not thinking in the right direction... I'm open to new suggestions.