I noticed that when I am paging through sheets, that when I get to the beginning or end it just loops around (this is GOOD!). However, when I am paging through sheets I am NOT watching the tabs but I am watching the contents of the sheets. I would like to be notified by a (bell / ding) that I am passing the end or the beginning and looping around again. Thanks, Tracey
Thanks for the suggestion. This looping of tabs can be done since the fix for bug 156311. Bug 160580 shows that users might like to be made aware when such wraparound happens. This reminds me of: - Windows audio feedback discussed in bug 145324 - Visual animation to draw attention to the Quick Find toolbar when it is opened, discussed in bug 151110 I wouldn't agree with adding a sound alert as a default, unless it's something that's tied to the operating system's accessibility API (for users needing sounds for many kinds of interactions / notifications). The Quick Find toolbar has a coloured message "Reached the beginning/end of the document" when wraparound happens. UX/Design team, what do you think?
(In reply to Tracey from comment #0) > I noticed that when I am paging through sheets, that when I get to the > beginning or end it just loops around (this is GOOD!). But not seen as good by everyone / in every scenario, see bug 160580. I suggested to keep the looping unconditional and introduce commands to jump to the first and last sheet. Which might be sufficient and we can resolve this idea as WF. If we decide to show a notification it could be something similar to the find/replace workflow where the quickfind toolbar bar or the F&R dialog show some (now infobar-like) information that the search starts from the beginning. Would be quite annoying in case of two sheets...
We discussed the topic in the design meeting. We pondered over an infobar on looping with "[x] Show this infobar", extra UNO commands "To First/Last Sheet", but suggest to introduce an (advanced) option to not loop, which should be off by default for compatibility reason. For code pointer, see https://gerrit.libreoffice.org/c/core/+/155449
I would be interested in taking this up, however, I'm still unclear what needs to be done. I understand the problem but if you could elaborate expected solution suggested by UX team that would be great. I can join a UX Team call if required.
(In reply to Aditya Sahu from comment #4) > ...elaborate expected solution suggested by UX team that would be great. Add an option (expert only, without UI control) to suppress the newly introduced cycling. The code pointer above is for the cycle part, prototype for an expert option could be https://gerrit.libreoffice.org/c/core/+/117414
Already done *** This bug has been marked as a duplicate of bug 160580 ***