I'm a bit lost, can you explain what's the problem with a bit more verbosity?

In D14936#313721, @aacid wrote:

I'm a bit lost, can you explain what's the problem with a bit more verbosity?

I have updated the description with the bug report descriptions.
Each tab has its own KActionCollection, so the shortcut dialog only maps the shortcuts to these KAction instances.

The thing is that to me it doesn't feel like guiClient()->reloadXML(); manually, i would expect KXmlGui & friends just to handle this properly.

I'm going to add @dfaure that knows a lot about xmlgui and may be able to give a hint if we're solving this the right way or not.

So each tab has its own KActionCollection, but with the same action names as the other tabs?

In that case, having a single KActionCollection (and dispatching in the slots) might be closer to what KXMLGUI was designed for.

So if we don't go for that redesign, we do need a way to update the shortcuts in all actioncollections indeed. Reloading the XML file is one way. Another way would be to implement propagation of shortcuts from one actioncollection to the others after the dialog changed shortcuts in the current collection.

In D14936#320638, @dfaure wrote:

So each tab has its own KActionCollection, but with the same action names as the other tabs?

Yes

In that case, having a single KActionCollection (and dispatching in the slots) might be closer to what KXMLGUI was designed for.

That was my understanding as well, I can probably do that once I have a better understanding of the app.

Another way would be to implement propagation of shortcuts from one actioncollection to the others after the dialog changed shortcuts in the current collection.

I tried that first and failed to do it, it doesn't look easier to implement than redoing a unique kactioncollection