It is actually possible to save annotations made during presentation with the mouse pointer if the option "Mouse painter as pen" (in Slide Show Settings) has been enabled before starting the presentation.
The problem is however that the tool doesn't use the algorithm of the normal hand-writing tool used in slide editing mode: while in editing mode the hand-writing tool saves just a few dots and "builds" Bézier curves, in presentation mode the algorithm just save LOTS of micro points.
You can see an example in the attached screenshot and odp file: the curves in blue has been obtained with the handwriting tool in editing mode, those in red with the "same" (that is not) tool in the presentation mode.
The result is that even with a few annotations, the slides become unresponsive even on modern pc and generate other problems (e.g., annotation saved on the wrong slide)
Steps to Reproduce:
1. In Slide Show Settings choose the option "Mouse painter as pen"
2. Now starts a presentation and make a few annotations
3. Close (or end) the presentation
Annotation are now saved (as desired) with the slide but making too many points but are composed of way too many points that make instable LO (i.e., needs to be killed). Annotations may also appear on wrong slides.
The annotations made during presentation should have used the same algorithm of hand writing during slide edit.
User Profile Reset: No
A similar bug already exists (https://bugs.documentfoundation.org/show_bug.cgi?id=51928), but it focus on presentation annotations not being saved.
While this one observes that annotations can actually be saved, but the process of creating them is bugged.
There is no easy workaround, so I leave this bug report as normal.
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Created attachment 136561 [details]
Test slide with annotations
In the attachment lines in blue has been obtained using editing-mode hand-writing tool, while lines in red with presentation-mode hand-writing tool.
You can see the differences if you click on them "edit points"
Created attachment 136562 [details]
Screenshot of the same file
Screenshot of the same file. I am uploading this, as opening the original file is ok, but as soon you try to do something with the red lines, it may make your pc unresponsive, so opening instead this screenshot is a safer option ;-)
Repro from scratch.
Arch Linux 64-bit, KDE Plasma 5
Build ID: af318eeb4e23694e17b09b902afb98ddf9da9b7b
CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on November 1st 2017
Hello, I know it's not nice to ping a bug report without bringing any news, but this bug is pretty important for me as it would allow me to use LibreOffice for teaching in distant learning projects, and at the same time it should be fairly simple to solve for someone with knowledge of the internals of LO Draw, as it is a matter of applying an already know algorithm in the context of live slide annotations.
Is there any way I could investigate this bug further or be more precise in its description?
(In reply to Antonello from comment #4)
> Hello, I know it's not nice to ping a bug report without bringing any news,
> but this bug is pretty important for me as it would allow me to use
> LibreOffice for teaching in distant learning projects, and at the same time
> it should be fairly simple to solve for someone with knowledge of the
> internals of LO Draw, as it is a matter of applying an already know
> algorithm in the context of live slide annotations.
> Is there any way I could investigate this bug further or be more precise in
> its description?
I think the description is clear enough, so the only way you could help is to dig into the code and provide a better algorithm. I don't believe this is a regression, I assume it has always behaved like this.
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!
Still present in LO 126.96.36.199