Bug 196009 - please save shortcut with shift+tab as shift+tab and not as backtab
Summary: please save shortcut with shift+tab as shift+tab and not as backtab
Status: RESOLVED DUPLICATE of bug 125812
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 12:35 UTC by Matthias Heinz
Modified: 2009-06-11 18:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Heinz 2009-06-11 12:35:39 UTC 
Version:           svn rev 980159 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Hi,

I'm having problems with some special shortcut combinations. I use ctrl+tab to go to the next document and ctrl+shift+tab for the previous document. If I set those shortcuts with the shortcut editor just ctrl+tab works, but ctrl+shift+tab doesn't. When I looked in the kileui.rc I found out that the shortcut is saved (and interpreted?) as ctrl+backtab.

When I edit the file and change this entry to ctrl+shift+tab and restart kile the shortcuts works for the previous document function.

So please don't save and interpret shift+tab as backtab.

Thanks,
Matthias
Comment 1 Thomas Braun 2009-06-11 17:59:00 UTC 
Actually we don't do this ourselves here but kdelibs does this.
What key do you mean by backtab?
Does the shortcut editor show the correct shortcuts?
Comment 2 Matthias Heinz 2009-06-11 18:22:49 UTC 
Well, I dont know which key backtab should refer to, but shift+tab is "translated" to "backtab".

The shortcut editor translates it, and it gets saved as backtab. If I change backtab to shift+tab manually in the config file the editor displays it as shift+tab and the shortcut works.

I have noticed this behaviour in many other programs, too. Like kwin, konsole, konqueror... looks like this problem lies much deeper as I thought.
Comment 3 Thomas Braun 2009-06-11 18:42:13 UTC 
This bug is the same as #125812. And it is a kdelibs bug.

*** This bug has been marked as a duplicate of bug 125812 ***
Comment 4 Matthias Heinz 2009-06-11 18:55:46 UTC 
Please have a closer look at the bug reporter and what he uses:

"Version:            (using KDE KDE 3.5.2)"

This bug is a KDE4 bug and not related to kde 3.