https://bugs.documentfoundation.org/show_bug.cgi?id=119665
Jim Raykowski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Jim Raykowski <[email protected]> --- Here are steps that can be used to add UNO commands and hook them up to the core functions for this request: 1. Decide on names for the UNO commands. Perhaps .uno:GoToNextHeading and .uno:GoToPrevHeading 2. Add the commands to the commands section in the WriterCommands.xcu file[1][2] These commands will be used to connect the UI element (menu item, toolbar item) to code base functions through the framework Dispatch API[3] 3. Define slot IDs for the new commands[3][4]. The end of the "Region: Traveling & Selection" section seems to be the appropriate place for these. 4. Add method slot definitions and interface definitions to the sdi (slot definition interface)? files[5][6]. 5. Add cases for the defined commands in the SwTextShell::ExecMoveMisc function[7]. Core functions that move the cursor to the previous/next heading are SwCursorShell::GotoPrevOutline and SwCursorShell::GotoNextOutline[8]. 6. "How to add, replace or remove a User Interface Command" and "Images" sections[9]. [1] officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu [2] officecfg/registry/schema/org/openoffice/Office/UI/Commands.xcs [3] https://wiki.openoffice.org/wiki/Framework/Article/Implementation_of_the_Dispatch_API_In_SFX2 [4] sw/inc/cmdid.h [5] sw/sdi/_textsh.sdi [6] sw/sdi/swriter.sdi [7] sw/source/uibase/shells/txtcrsr.cxx [8] sw/source/core/crsr/crstrvl.cxx [9] https://wiki.openoffice.org/wiki/Framework/Article/General_Architecture_Of_The_Framework_User_Interface_Implementation#Maintenance_of_Menus.2C_Toolbars_and_User_Interface_Commands -- You are receiving this mail because: You are the assignee for the bug.
