Bug 102651 - KMail toolbar shouldn't be reset to the default selection of buttons after update
Summary: KMail toolbar shouldn't be reset to the default selection of buttons after up...
Status: RESOLVED DUPLICATE of bug 99123
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-28 10:51 UTC by Christian Boltz
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 Christian Boltz 2005-03-28 10:51:50 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs

After updating  from KDE 3.3 KDE 3.4, the KMail toolbar was reset to the default selection of buttons. I had to add some non-default buttons again. 
 
It would be nice if the toolbar setup would be preserved when doing an update.

I already had a discussion about this in
https://bugzilla.novell.com/show_bug.cgi?id=73748

For those without access to Novell Bugzilla, here's a summary:

Coolo explained me why this can't be done currently (no three-way-merge available).

My suggestion:

Perhaps a 95%-solution could be done with less effort ;-) 
 
I assume if users change the toolbar, they mostly _add_ buttons. 
 
Not many users will remove existing buttons since the default selection is not that bad ;-) 
 
Suggestion: On update, ... 
- make sure the default buttons are contained in the toolbar 
  (add them if they are missing) 
- don't remove additional buttons (which probably the user has 
  added) 
 
What about that? It wouldn't be perfect, but ways better than the current state. 

Coolo's reply:
you can't differ between toolbar buttons removed by application developers and buttons added by user in your concept

Me again:
I know. The buttons removed by the developers are the missing 5 percent ;-) 
But better a 95% working solution than a 0% one...


PS: Yes, I've seen bug 80570, but I hope you can change this ;-)
Comment 1 Stephan Binner 2005-03-31 10:49:44 UTC

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