dfaure added a comment.
Hmm that's not how this is supposed to work, no need to look up actions. Look at the connect in kparts browserextension.cpp. The basic idea is: the part derives from BrowserExtension and provides a print slot, the shell calls it. Then the question became "but how does the shell know when to enable/disable the action", which is what actionSlotMapPtr() and isActionEnabled() are about, see KonqMainWindow::connectExtension for sample code. REPOSITORY R223 Okular REVISION DETAIL https://phabricator.kde.org/D12067 To: broulik, #okular, aacid Cc: dfaure, ngraham, aacid
