Bug 128838

Summary:	multiple items with same hotkey no longer works
Product:	[Unmaintained] kdelibs	Reporter:	Michael Nix <mnix>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	wstephenson
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michael Nix 2006-06-08 16:42:17 UTC

Version:           0.7 (using KDE 3.5.3, compiled sources)
Compiler:          gcc version 3.4.6
OS:                Linux (i686) release 2.6.17-rc6

Some time back when I had a keyboard with web buttons, I used them to start menu entries for things like Konsole, Mozilla etc.
If several items had the same hotkey, I got a menu listing the items to pick from. This way I could use XF86Finance for a local konsole session, and CTRL-XF86Finance for a selection of other konsole sessions I used regularly.

In the meantime my keyboard died, and I used an old one, so I don't know when this happened, but now that I have a nice new G15 keyboard, I want to set up the same hotkey system.
KMenuedit no longer allows setting the same hotkey for multiple items.
I can still do it through the control centre, but when I hit the key, I just get one of the items, rather than a menu.

This was a really nice feature, and it would be nice to at least have the option to turn it on again.

Comment 1 Will Stephenson 2009-11-23 18:36:19 UTC

kglobalaccel would need to support this, reassigning to its maintainer

Comment 2 Michael Jansen 2009-12-08 03:05:47 UTC

This seems to be kde 3.5 so i don't know what happened. I never worked on 3.x.

It doesn't work in 4.x either. But that is a wontfix from my side for a long time because of some real outstanding problems. Unless someone else stands up.

Comment 3 Christoph Cullmann 2024-09-14 16:18:51 UTC

Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann