Bug 104101 - katepartui.rc defines too few groups for toolbar actions
Summary: katepartui.rc defines too few groups for toolbar actions
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2005-04-18 00:52 UTC by Alexander Dymo
Modified: 2018-09-19 14:30 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 Alexander Dymo 2005-04-18 00:52:58 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

katepartui.rc defines a reasonable amount of groups for menu actions but not for toolbar actions. 
For example, there are:
    <Action name="edit_undo" group="edit_undo_merge" />
    <Action name="edit_redo" group="edit_undo_merge" />
    <Separator group="edit_undo_merge" />
    <Action name="edit_cut" group="edit_paste_merge" />
    <Action name="edit_copy" group="edit_paste_merge" />
    <Action name="edit_paste" group="edit_paste_merge" />
but only
  <Action name="edit_undo" group="edit_operations" />
  <Action name="edit_redo" group="edit_operations" />
  <Action name="edit_cut" group="edit_operations" />
  <Action name="edit_copy" group="edit_operations" />
  <Action name="edit_paste" group="edit_operations" />
This prevents applications which embed kate part from filtering actions shown on toolbars. For example it's not possible to keep undo/redo and remove copy/paste from a toolbar.
Everything would be ok if toolbar actions had the same groups as menu actions.
Comment 1 Alexander Dymo 2010-04-19 23:50:53 UTC
With KDE 4.4 one can call KXMLGUIClient::replaceXMLFile() on a kate part to provide a custom katepartui.rc file. This is what we do in KDevelop now to customize menus/toolbars and that means this bug is no longer relevant.
Comment 2 Andrew Crouthamel 2018-09-19 14:30:10 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.