Bug 163356 - keyboard shortcuts: reference to the source setting (new mechanism)
Summary: keyboard shortcuts: reference to the source setting (new mechanism)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-06 13:01 UTC by Maciej Pilichowski
Modified: 2024-09-14 16:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-06-06 13:01:51 UTC
Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs

The most clear case is Kate here.

The problem with embedding external app is to being able to (or not) automatically follow any changes in the "source" application.

Today I changed the "move to matching bracket" from ctrl+6 to ctrl+(. In kate. 

Kdevelop, kile, (KMail in future I hope) use kate, but I have to go to all those apps and redefine this key again.

So the idea: reference to a setting. Let's say that by default in Kdevelop "move to..." was a reference, and in Kile it was not. So when I changed it in Kate, the change was "transferred" to Kdevelop but the flag "reference" was kept. In kile ctrl+6 would remained the same.

What's more, I could run Kile and set ctrl+( as in Kate, or I could turn on "reference". The shortcut would be the same but behaviour would be different -- in the former case any other change in Kate would not be seen in Kile, while in the latter -- it would be.

This would be extremely useful for changing shortcuts in one app (kate) but in such way that those changes are made to all apps that uses Kate.
Comment 1 Christoph Cullmann 2024-09-14 16:18:04 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