When showing a slideshow with the mouse (e.g. clicking the presentation to go to the next page), hidden slides stay hidden. But if I use Impress Remote, hidden slides are shown in the slideshow.
Hey Davide - So what I can see is that if you tap on your device (the one with the remote) then it skips the hidden slide. If you swipe it shows the hidden slide. For me this is kind of a feature since now you have the option to see the hidden slide if you choose, but you can skip by tapping. Your thoughts?
I think by default, a hidden slide should remain hidden. If we'd like to add a feature to the Android remote to allow hidden slides to be shown, that's fine with me, but I think that users won't expect the current behavior.
Hi, I agree with Robinson. A hidden slide should stay hidden whether you tap on it or you swipe. What you could do is showing *all* the slides, including the hidden ones, in the slideshow overview (maybe graying them out), and adding a togglable option in the action menu "Skip hidden slides", enabled by default.
David: What version of the Impress Remote are you using?
2.1.1 released on June 5, 2014, according to Google Play.
Moving bug to (new) 'Impress Remote' product.
There's an inconsistency in the LibreOffice Impress part of things - sometimes it doesn't tell the remote about hidden slides (they won't appear on the remote at all, not in slide overview either). As then the Remote doesn't see the hidden slides anymore, it cannot tell LibreOffice to "switch to <slide#x, that happens to be hidden/>" anymore, thus in this case → worksforme But this is somewhat inconsistent (or rather anything but straight-forward), and sometimes, even with the very same presentation, it sends all slides over to the remote. I didn't bother to track down the circumstances on when you get all and when you only get some (guess reading the code then is easier). But it seems that when you connect/start the presentation while in Impress you have one of the hidden slides selected (e.g. in the slidesorting view) or opened for editing in the normal view, the remote gets the shortened list, i.e. the one without the hidden slides, and when you are on a slide that is not hidden, you get the full list that includes the hidden ones. To me, this is the opposite way I'd expect that if it was a feature. It should work the other way, include the hidden ones when I select a hidden one, and restrict to the non-hidden ones, when I start with a regularly displayed one. But this would be a very obscure feature. but yes, swipe going directly to the next slide, and tap/volume button performing the next action (stepping through manually triggered animations and transitions) is expected behavior. ############## SUMMARY ################# * start presentation while LO Impress has a hidden slide selected/active → remote gets a stripped down list without the hidden slides (no way to show hidden slides via the remote) * start presentation while LO Impress has a regular slide selected/active → remotes gets full list of slides (you can display hidden slides via the gridview or by sliding to a hidden one) * currently there's no flagging of hidden slides defined in the protocol between the remote and LO impress → the remote needs to be extended to show hidden slides as such in the gridview → UI/UX for handling swiping re hidden slides need to be agreed upon (show dialog asking to confirm to show hidden slide or skip to next regular slide? just go to next slide and have an option "enable swipe to hidden slide",...) → Remote Protocol needs to be extended to send a message "hidden_slides" or similar that has the slide numbers as message data for the remotes to evaluate ###### THIS BUG ####### This bug is about the Android Remote part of the topic, namely: * handling display of hidden slides in the slides grid (shading or border or similar, maybe with a toggle to show/hide them completely) * implementing whatever UX to access/skip those hidden slides via the remote (propose ideas and assign to ux-advise for feedback) EasyHack, as the ImpressRemote in general is easy to hack on :-))
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillJava) [NinjaEdit]
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC) [NinjaEdit]
Missing code pointer (mandatory for easy hack)
Changing status: NEEDINFO -> NEW Adding keyword 'needsDevEval' [ninjaedit]
Removed easyHack since this bug doesn't seem to have been evaluated properly to be tagged as such and missing code pointers.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Davide Depau, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I read this article! I hope you will continue to have such articles to share with everyone! thank you!
Dear Davide Depau, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug