Bug 110555 - dynamic filter actions - removed buttons won't come back etc.
Summary: dynamic filter actions - removed buttons won't come back etc.
Status: RESOLVED DUPLICATE of bug 97558
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-11 09:11 UTC by Martin Kant
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Kant 2005-08-11 09:11:12 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          gcc 3.3.5-20050130 
OS:                Linux

Something like this has already been discussed in http://bugs.kde.org/show_bug.cgi?id=89221, where I added a comment but didn't get noticed. I removed/deleted the buttons (mark as SPAM/HAM) generated through the wizard via the toolbar configuration screen. I wasn't able to bring them back so I checked bugs.kde.org and saw this is not new. In my case now I'm not able to add any filter action button to the toolbar - even filters not generated by any wizard. The filter action buttons are listed on the left hand side in the toolbar configuration screen and I can add them to the right hand side, so they may show up on the toolbar, but they simply don't show up. As well as any assigned shortcuts for these generated filter actions (e.g. mark as SPAM/HAM) won't trigger after a restart of Kmail - I have to reassign them. I'm no expert at all, but the action of removing buttons from a toolbar has never ever had a semantic meaning like deleting a file - even if there is a warning message, which hardly anyone reads since any message other than "Accept the changes?" isn't expected (just my 2c).
Comment 1 Stephan Binner 2005-08-11 15:53:08 UTC
kdelibs 3.5 introduces to reset the toolbars to their default, maybe a possible work-around then.
Comment 2 Andreas Gungl 2005-08-12 21:14:16 UTC

*** This bug has been marked as a duplicate of 97558 ***