Created attachment 171923 [details] Example file from Impress Attached example file has three slides and the second is set as the starting point in the Slide Show Settings dialog. This affects the Start from First Slide and Start from Current Slide commands: - Start from First Slide starts the slideshow from the first slide as if nothing happened - Start from Current Slide starts the slideshow from the second slide as it is set in the dialog. This behavior is the opposite of what a naive user or a former PowerPoint user would expect. It would be more natural if the Range setting would influence the Start from First Slide command. Steps to reproduce: 1. Open attached file 2. Select the third slide in the Slides pane 3. Slide Show - Start from First Slide 4. Select the third slide in the Slides pane 5. Slide Show - Start from Current Slide Actual results: Start from First Slide starts from the actual first slide. Start from Current Slide starts from the second slide. Expected results: Start from First Slide should start from the second slide. Start from Current Slide should start from the selected third slide. This would emulate PowerPoints behavior, as in: starting from the current slide always means the selected slide, and starting from the first slide means the first or the one defined in the Slide Show Settings dialog. LibreOffice details: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5d7251c7121cee8885fa9f2387c4a0625dd4ecee CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL Also in 7.0, 6.0, 5.0, 4.1 In 4.0 there was only one Slide Show command to start the slideshow, which started it from the currently selected one regardless of the Range setting.
Accepted, "Start from Current Slide" should always start with the current slide while "Start from First Slide" should take the setting into account and ideally get renamed to "Start Slideshow". The issue seems to apply also for Custom Slide Show.
Dear NISZ LibreOffice Team, 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