Created attachment 100769 [details] patch hacking out legacy stuff. This patch removes the SfxItemPool Load/Save - to SvStream - which gums up our code with a number of rather odd binary file format residue pieces. Nominally these are used for EditEng copy/paste - but - strangely, when compiled without them copying shapes from draw to/from another draw with style attributes etc. appears to work just fine. Unclear what's going on. A bit of surgery / debugging is needed in: ImpEditEngine::CreateTransferable I suspect, and also OutlinerView::Read( SvStream& rInput and similar places where I've done a partial cut. Nevertheless libreoffice compiles rather nicely with this, and (potentially) it frees us of some evil / old bloat. Thoughts appreciated; I guess its rather easy to accelerate SfxItemPool without having to wrestle with this mess ...
The thing to check is copying the text from inside one text box to another, with rich text especially
Ah - right; that fails as expected =) I get a completely empty text when pasted - even inside the same document; good. Well worth switching to RTF/ODF for that (I guess) if we can remove all that evil guff around the place there.
** 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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
yes that horrible code still exists, no it's not a regression let's set this to "enhancement"
oh, there was a bug for this?... Varun removed that stuff in last year's GSoC!