Bug 94038

Summary:	Shortcut key of filter action isn't saved
Product:	[Applications] kmail	Reporter:	Hasso Tepper <hasso>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED LATER
Severity:	normal
Priority:	NOR
Version:	1.7.50
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Hasso Tepper 2004-11-27 17:39:12 UTC

Version:           1.7.50 (using KDE 3.3.89 (CVS >= 20041104), compiled sources)
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-2)
OS:                Linux (i686) release 2.6.10-rc2-bk8

In current HEAD version there is two possibilities to assign shortcut key to the filter action: 1) in the filters configuration dialog 2) in the shortcuts configuration dialog. In first case shortcut is saved (ie. if you exit the kmail and start it again you can still use shortcut), but in second case it isn't. Same bug is there in the 3.3 branch, but as there isn't way to configure shortcuts in the filters configuration dialog, there isn't way to save it all.

Comment 1 Andreas Gungl 2004-11-27 22:12:02 UTC

On Samstag 27 November 2004 17:39, Hasso Tepper wrote:
> In current HEAD version there is two possibilities to assign shortcut key
> to the filter action: 1) in the filters configuration dialog 2) in the
> shortcuts configuration dialog. In first case shortcut is saved (ie. if
> you exit the kmail and start it again you can still use shortcut), but in
> second case it isn't. Same bug is there in the 3.3 branch, but as there
> isn't way to configure shortcuts in the filters configuration dialog,
> there isn't way to save it all.

Well, 2) is a problem in the way of how dynamic actions are implemented in 
KDE 3. The only way to work around it was 1) which is in HEAD but can't be 
backported due to GUI / string changes.

IMO we should close the report as all we can do in KMail is done. 
Alternatively we should file it against kdelibs. There are related bug 
reports like http://bugs.kde.org/show_bug.cgi?id=89221 BTW. I hope we can 
have a real solution for this in KDE 4.

Comment 2 Andreas Gungl 2004-12-13 22:48:10 UTC

Closing as explained in comment #1.

Comment 3 Anthony Hepple 2007-04-24 11:43:32 UTC

I've been affected by this bug and am concerned that it may be overlooked.  Please do not forget about it for KDE 4.  Thanks