Summary: | defining shortcuts: refresh problem | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Wolfgang Rohdewald <wolfgang> |
Component: | Mail Filter Agent | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | montel |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wolfgang Rohdewald
2011-09-26 14:00:28 UTC
Do you click on "Apply" ? I can't reproduce it after click on apply Regards no, I did not "Apply" - I would have expected that changes are respecting previous unapplied changes. Imagine renaming two different filters to the same new name. If the second rename ignores the first rename, you have two filters with the same name. Well - I just tried, this is a bad example, it seems to be legal for two filters having the same name. To me that seems like another bug. But anyway if a change ignores previous unapplied changes, you cannot have clean transactions. Are you sure this cannot lead to corruption - not even in the future when the source code is changed without thinking about this potential problem? BTW I am seeing lots of problems with searching mails in kmail2 (4.7.1), I could easily open half a dozen bug reports. Is that what I should do or should I first go to some IRC channel (which one?) For me if you want to change a filter you must apply. otherwise it's not change. For searching email there is still a lot of bug but you can create bug report. I will look at them. Regards. if I must apply between changing different filters, there should be a question like "There are unapplied changes. Do you want to apply them now or throw them away?" This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |