https://bugs.documentfoundation.org/show_bug.cgi?id=101211
--- Comment #19 from V Stuart Foote <vstuart.foote@utsa.edu> ---
(In reply to Heiko Tietze from comment #18)
Not a fan of too many UNO commands...
The issue we run into is that PgUp (.uno:PageUp) / PgDown (.uno:PageDown) are
scrolling commands useful for adjusting the "view port" of the VCL canvas as a
scrolling increment--controlled by os/DE--and integral in selection actions.
As scroll controls, they do not reposition the "edit cursor", nor should they.
Nor do they work against page objects--just a view of the VCL canvas.
What users are asking is the ability to position by document page increment.
Key being the repositioning of the edit cursor and the view port (as needed) on
the current VCL canvas.
Our UI for page movement has been lacking compared to navigating other objects.
We provide for "edit cursor" movement with UNO control by logical word,
sentence, line, paragraph, frame, section. For example <Ctrl>+<Up>
(.uno:GoToPrevPara) / <Ctrl>+<Down> (.uno:GoToNextPara),
or the <Ctrl>+<Home> (.uno:GoToStartOfDoc) / <Ctrl>+<End> (.uno:GoToEndOfDoc).
There has been no effective way to reposition to a previous page or next page
object. Providing it requires a new UNO command for each for inclusion in the
UI as Keyboard or Toolbar button actions.
Legacy, and common, <PgUp> (uno.PageUp)/<PgDown> (uno.PageDown) are used for
scrolling the view of our VCL canvas and making interactive selections, we
can't change that--too much push back.
On the other hand, <Ctrl>+<PgUp> (.uno:JumpToHeader) / <Ctrl>+<PgDown>
(.uno:JumpToFooter) have been used to reposition the "edit cursor" into the
nearest Header or Footer if present--or to top or bottom of page if not. And
that usage could be shifted without major UX complaints.
My suggestion would be:
1. retain the <PgUp> (.uno:PageUp) / <PgDown> (uno.PageDown) scroll,
way to much disruption/grief from users to "hijack" an os/DE staple
2. use Jim's new UNO controls for the <Ctr>+<PgUp>, <Ctrl>+<PgDown>
but rename them to "To Previous Page", "To Next Page" with better UNO names
3. shift the To Header / To Footer jump movements to be the <Ctrl>+<Shift>
actions
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 101211] "Previous page" and "Next page" functions in navigator not available for keyboard binding · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.