Bug 315430 - No way to configure toolbar order
Summary: No way to configure toolbar order
Status: RESOLVED DUPLICATE of bug 96209
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 312720 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-19 08:58 UTC by Nikola Kovacs
Modified: 2013-07-23 14:59 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nikola Kovacs 2013-02-19 08:58:19 UTC 
The kate toolbar is split into three toolbars:
Main Toolbar <kate>
Main Toolbar <katefiletreeplugin>
Main Toolbar <KatePartView>
But those three are then somehow merged into a single toolbar (and if I add a toolbar button, that's broken, see bug 64754), and there's no way to reorder them (e.g. I can't move the back and forward buttons, because they're in a separate list)

The current actions list should show everything and simply allow me to reorder the toolbar.

Reproducible: Always
Comment 1 Dominik Haumann 2013-02-20 12:08:04 UTC 
*** Bug 312720 has been marked as a duplicate of this bug. ***
Comment 2 Dominik Haumann 2013-02-20 12:10:34 UTC 
This is a problem of the KParts and KXMLGuiClient technology. So no, you cannot just have a simple list currently. Still this is a duplicate of bug #64754, isn't it?
Comment 3 Nikola Kovacs 2013-02-20 12:11:34 UTC 
No, because if the groups are set, the items don't reorder, but I still can't reorder them manually.
Comment 4 Christoph Cullmann 2013-04-07 09:57:21 UTC 
Anyway, in Kate application we can't fix that.
Comment 5 LaChenal 2013-04-07 17:35:55 UTC 
It needs fixing.
 It affects kate.
 Who, then should fix it?
Is there a layer that re-maps toolbars? It looks as if such a thing is needed.

Please excuse me, my technical knowledge of this area is poor.
Comment 6 Christoph Feck 2013-07-23 14:59:17 UTC 

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