<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - "Previous page" and "Next page" functions in navigator not available for keyboard binding" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101211#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - "Previous page" and "Next page" functions in navigator not available for keyboard binding" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101211">bug 101211</a> from <a class="email" href="mailto:raykowj@gmail.com" title="Jim Raykowski <raykowj@gmail.com>"> Jim Raykowski</a> <pre>(In reply to Kenneth Hanson from <a href="show_bug.cgi?id=101211#c21">comment #21</a>) > @V Stuart Foote > > Your proposed keybindings sound good to me. > I agree, so? .uno:GoToPrevPage 'To Previous Page' .uno:GoToNextPage 'To Next Page' > > I have some questions about UNO commands. > > 1. What is the UNO command for the "Next/Previous Page" commands? Are they > the PageUpCursor and PageDownCursor functions in the code Jim linked? > 'To Begining of Next Page' is .uno:GotoStartOfNextPage 'To Begining of Previous Page' is .uno:GotoStartOfPrevPage The linked functions in the code are what the Navigate By control uses for Page element navigation. They aren't used by any UNO command AFAIK. > 2. In the customize dialog, is there any difference between commands labeled > "Go to next X" vs simply "To next X"? > I think that is just an inconsistent naming difference. > Also, the names I proposed were all labels for the UI. So, if only the > "Page(Up/Down)Cursor" commands are made available to the, my proposed name > would (presumably) result in providing the C++/UNO "Page(Up/Down)Cursor" > command as "Page Up" in the UI. Sorry, you lost me. Regardless of what the UNO command name is you will be able to assign whatever shortcut key to it you wish.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>