Bug 103217 - Configure toolbars (any KDE app): select Available Action - after move to Current Actions, the Current Actions list does not update
Summary: Configure toolbars (any KDE app): select Available Action - after move to Cur...
Status: RESOLVED DUPLICATE of bug 101735
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-04 19:15 UTC by Nick T
Modified: 2005-04-04 20:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick T 2005-04-04 19:15:50 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

Seems to apply to all KDE apps.  Relates to the "Configure Toolbars" dialog.

When you select an Action not in the current toolbar and click the arrow to add it to the Current Actions list, the action disappears from the Available Actions list, but does not get added to the Current Actions list.

When you close the dialog, the action _has_ been added to the toolbar, but if you want to reposition it you have to re-open the dialog.  The action is then in the Current Actions list.

This same problem is present in KDE 3.4.0 compiled from source on Slackware 10.0.
Comment 1 Thiago Macieira 2005-04-04 19:42:23 UTC
It had been some time since this was reported...

It was the first hit on the duplicate list. People don't check duplicates?

*** This bug has been marked as a duplicate of 101735 ***
Comment 2 Nick T 2005-04-04 20:09:59 UTC
Hi

On Monday 04 Apr 2005 6:42 pm, you wrote:
> It had been some time since this was reported...
>
> It was the first hit on the duplicate list. People don't check duplicates?
>
> *** This bug has been marked as a duplicate of 101735 ***


Apologies.  I did check through for duplicates - it was such an obvious bug I 
was expecting to find it already reported.  Maybe I didn't go about searching 
for duplicates the best way. :(

- Nick