In regard to the question
I've suggested some ideas to improve control over presentation
We have Prior, Next, Last, First, and so forth
We could have assigned special page 0~9, as "ctrl + 0~9" like in RTS game, up to 10 special pages to be called up at any point.
Also the "back" to last page, could we have the behaviour, better work like in the web browsers, either backspace or alt+left(arrow)?
Operating System: All
Version: 188.8.131.52 release
Please keep bug reports separate, we'll only address 1 bug per report.
I'll address first one and edit title here:
Valid enhancement request.
Low - makes going to certain slide a bit easier but not sure how/if most users would get much out of this. Normal flow is not to jump back and forth in a presentation, it's to move forward 1 by 1 or go back/forward by one slide.
Potential easy hack, marking as such
Thanks for your report!
Removing comma from whiteboard (please use a space to delimit values in this field)
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.
Thank you and apologies for the noise
Hmm. So this does not really help with the original ask.libreoffice question. I'd propose the 'Go to page or object' action in Slideshow->Interaction instead.
The feature itself is rather very obscure, and the limit to 10 'special slides' is annoying and arbitrary. Also, it needs UI changes in Impress, to somehow specify which slides of your slidedeck should be 'special'. With that, not really EasyHackable, and I'd prefer some UX insight here as well.
Finally, if you know the slide number you want to jump to, during presentation mode, simply type that number and press enter, and voila.
Does the above solve your problem sufficiently well?
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker
-- The LibreOffice QA Team
This INVALID Message was generated on: 2015-05-06