[Libreoffice-ux-advise] [Bug 38781] LOCALHELP for WRITER Navigation Toolbar ('View -> Toolbars -> Navigation') missing
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Sun Feb 18 21:52:52 UTC 2018
https://bugs.documentfoundation.org/show_bug.cgi?id=38781
V Stuart Foote <vstuart.foote at utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vstuart.foote at utsa.edu
See Also| |https://bz.apache.org/ooo/s
| |how_bug.cgi?id=5608
--- Comment #13 from V Stuart Foote <vstuart.foote at utsa.edu> ---
The source [1][2] is reasonably well documented. And the Greenberg & Cockburn
[3] "recency with temporal ordering" based back and forward history navigation
remains. But, if fully functional would expect the feature to be less about
navigating hyperlinks (internal or external) and for the control to provide
more generic Back and Forward movements within a document.
A GoToMark, GoToFLy, GotoINetAttr, GotoOutline (index), GotoOutline (string),
GotoRegion, GotoRefMark, GotoNextTOXBase, GotoTable,GotoFld, and GotoRedline
action were linked as history navigation targets.
Unfortunately, not clear the "recency with temporal ordering" of the navigation
history is still implemented correctly. I couldn't identify where in UI a user
could "add" a mark to trigger inclusion of a SwUnoCsr position to the
m_entries[] list and _activate_ the control. And while inserting an internal
hyperlink--reference, bookmark, header, footer, etc. the Cusor is registered
into the navigation history, and activates the Navigation toolbar
controls--other actions for cursor/focus movement do not. For example a
Go-to-End of document should provide a Navigation toolbar action to return
from.
=-ref-=
[1]
https://opengrok.libreoffice.org/xref/core/sw/source/uibase/wrtsh/navmgr.cxx?a=true
[2] https://opengrok.libreoffice.org/xref/core/sw/source/uibase/inc/navsh.hxx
[3] https://prism.ucalgary.ca/bitstream/handle/1880/45977/1999-641-04.pdf
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Libreoffice-ux-advise
mailing list