[Libreoffice-bugs] [Bug 140702] It disappeared "To page" item from Anchor drop-down widget on Frame toolbar in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1091 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141091] No Anchor to Page in pop up menu for images and objects in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=141091 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0702 Blocks||135836 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135836 [Bug 135836] UI: Discourage usage of the to page anchor by hiding it from toolbar/context menu -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84456] Installer Warning 1946 on creating shortcuts on upgrade
https://bugs.documentfoundation.org/show_bug.cgi?id=84456 --- Comment #12 from gwi60...@bigpond.net.au --- 2021-18-03 downloaded LibreOffice 7.1.1.2 for windows x86_64 (windows 7) and had the message: Warning 1946 Property 'System.AppUserModel.ID' for shortcut 'LibreOffice Writer.ink' could not be set. Acknowledged warning and install continued OK. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141081] Unwanted lines around images inserted into ODT documents
https://bugs.documentfoundation.org/show_bug.cgi?id=141081 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG CC||vstuart.fo...@utsa.edu -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141083] writer problem with Keyscramler
https://bugs.documentfoundation.org/show_bug.cgi?id=141083 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||vstuart.fo...@utsa.edu Resolution|--- |NOTOURBUG --- Comment #1 from V Stuart Foote --- You use third party (non-MS) apps encrypting keyboard entry at your own risk. Take it up with QFX (supp...@qfxsoftware.com); no idea if their Pro version would have support for norm win32 MFC program like LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135929] Increasing image size, makes a part of the text vanish from canvas (anchor to character is especially error prone)
https://bugs.documentfoundation.org/show_bug.cgi?id=135929 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135944] Selected table can't with splitted and merged cells can't be overwritten/ nor does it past in the cells as what happens with regular table
https://bugs.documentfoundation.org/show_bug.cgi?id=135944 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140772] Crash in: swlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=140772 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135849] Image shuffle around when moving an image (another example)
https://bugs.documentfoundation.org/show_bug.cgi?id=135849 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135901] Missing space suggestion has an exception, where i would expect it too
https://bugs.documentfoundation.org/show_bug.cgi?id=135901 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135869] Anchor a chart behaves differently/wonky compared to an image
https://bugs.documentfoundation.org/show_bug.cgi?id=135869 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140777] Password protection conflicts with Autosave
https://bugs.documentfoundation.org/show_bug.cgi?id=140777 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140770] Extention-icons create new toolbar in Print Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=140770 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140553] FIXED Function Documentation is not up to date
https://bugs.documentfoundation.org/show_bug.cgi?id=140553 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140683] Shift of view, after export of the document to xml (Writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=140683 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141081] Unwanted lines around images inserted into ODT documents
https://bugs.documentfoundation.org/show_bug.cgi?id=141081 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141081] Unwanted lines around images inserted into ODT documents
https://bugs.documentfoundation.org/show_bug.cgi?id=141081 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141061] Images are not working properly in LibreOffice Writer with .docx
https://bugs.documentfoundation.org/show_bug.cgi?id=141061 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141061] Images are not working properly in LibreOffice Writer with .docx
https://bugs.documentfoundation.org/show_bug.cgi?id=141061 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141041] Validity Cell Range Visibility Problem (can't increase the width of the drop down menu)
https://bugs.documentfoundation.org/show_bug.cgi?id=141041 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141041] Validity Cell Range Visibility Problem (can't increase the width of the drop down menu)
https://bugs.documentfoundation.org/show_bug.cgi?id=141041 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136865] Toolbar icons looking broken/currupted on
https://bugs.documentfoundation.org/show_bug.cgi?id=136865 --- Comment #3 from QA Administrators --- Dear oidiegosan...@protonmail.com, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136511] Writer eats all the CPU after a while until the user saves on older hardware
https://bugs.documentfoundation.org/show_bug.cgi?id=136511 --- Comment #5 from QA Administrators --- Dear rimrunner, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136315] LibreOffice 7.0.0 Refuses to Open After Using It Once on a Windows Session
https://bugs.documentfoundation.org/show_bug.cgi?id=136315 --- Comment #2 from QA Administrators --- Dear bhiskins.1984.2, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128993] Annoying delay of 10 seconds when opening Libreoffice Writer files
https://bugs.documentfoundation.org/show_bug.cgi?id=128993 --- Comment #12 from QA Administrators --- Dear schregenb.u, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135520] new install of 7.0.0 causes endless restarts
https://bugs.documentfoundation.org/show_bug.cgi?id=135520 --- Comment #9 from QA Administrators --- Dear cbolin, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98412] SIDEBAR: Line properties not always updated
https://bugs.documentfoundation.org/show_bug.cgi?id=98412 --- Comment #8 from QA Administrators --- Dear Laurent BP, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 82117] Improve shortcut key list for German keyboard layout
https://bugs.documentfoundation.org/show_bug.cgi?id=82117 --- Comment #19 from QA Administrators --- Dear Kü, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 78955] Other: pasting composite selections with graphs from ods to odt-file does not preserve lines in charts linear and logarithmic
https://bugs.documentfoundation.org/show_bug.cgi?id=78955 --- Comment #11 from QA Administrators --- Dear ErikMAkkerman, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76785] User-defined colors in Excel not loaded properly from xls
https://bugs.documentfoundation.org/show_bug.cgi?id=76785 --- Comment #10 from QA Administrators --- Dear M Welinder, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72514] VaryColorsbyPoint changes legend colors, not point colors
https://bugs.documentfoundation.org/show_bug.cgi?id=72514 --- Comment #13 from QA Administrators --- Dear Dorien James, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68679] Bar charts do not allow timestamps
https://bugs.documentfoundation.org/show_bug.cgi?id=68679 --- Comment #8 from QA Administrators --- Dear pinus, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66617] chart2 unoapi test fails on sch.ChXDiagram::com::sun::star::chart::ChartStatistics::RegressionCurves
https://bugs.documentfoundation.org/show_bug.cgi?id=66617 --- Comment #11 from QA Administrators --- Dear Michael Stahl (CIB), 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 66217] Wrong formatting when pasting as HTML for a text copied from Notepad++ (win only)
https://bugs.documentfoundation.org/show_bug.cgi?id=66217 --- Comment #12 from QA Administrators --- Dear access2godzilla, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 65925] FILESAVE: Ugly HTML code when changing capital letters and bold text
https://bugs.documentfoundation.org/show_bug.cgi?id=65925 --- Comment #15 from QA Administrators --- Dear matta2006, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 57642] Gradient lost when FILEOPEN .xls (MSO97)
https://bugs.documentfoundation.org/show_bug.cgi?id=57642 --- Comment #9 from QA Administrators --- Dear Rainer Bielefeld Retired, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124140] Vector graphics are incorrectly shown in Impress.
https://bugs.documentfoundation.org/show_bug.cgi?id=124140 --- Comment #6 from QA Administrators --- Dear sebastian.severin, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116439] OS/2 multi-image bitmap does not display correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=116439 --- Comment #5 from QA Administrators --- Dear Chris Sherlock, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116435] XML Form Document: Impossible to rename default-value "instanceData"
https://bugs.documentfoundation.org/show_bug.cgi?id=116435 --- Comment #4 from QA Administrators --- Dear Robert Großkopf, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 101611] pdfimport filter does not honor page cropping (masking) as set in a PDF document, resulting pages in LO document are oversize (comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=101611 --- Comment #10 from QA Administrators --- Dear E.Mi, 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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141091] New: No Anchor to Page in pop up menu for images and objects in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=141091 Bug ID: 141091 Summary: No Anchor to Page in pop up menu for images and objects in Writer Product: LibreOffice Version: 7.1.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pasi...@gmail.com Description: Version 7.1.1.2, upgrade from 7.0.? on Windows 10 Pro Build 19041 Laptop. Paste image in Writer document. Right click image > Anchor. Options listed: To Paragraph, To Character, As Character. Option 'To Page' missing (omitted). Right Click image > Properties > Type tab > Anchor includes 'To Page' option, and it works. Steps to Reproduce: 1.Paste an image in Writer document. 2.Right click image. 3.Hover or click on Anchor to view options. Actual Results: 1.Paste an image in Writer document. 2.Right click image. 3.Hover or click on Anchor to view list of options. 4.List: To Paragraph, To Character, As Character. Expected Results: 4.List: To Page, To Paragraph, To Character, As Character. Reproducible: Always User Profile Reset: No Additional Info: 4.List: To Page, To Paragraph, To Character, As Character. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: vcl/CppunitTest_vcl_bitmap_test.mk vcl/inc vcl/qa vcl/source vcl/workben
vcl/CppunitTest_vcl_bitmap_test.mk |1
vcl/qa/cppunit/XpmFilterTest.cxx| 76 ++
vcl/qa/cppunit/data/XPM_1.xpm | 15 ++
vcl/qa/cppunit/data/XPM_4.xpm | 23 +++
vcl/qa/cppunit/data/XPM_8.xpm | 263
vcl/source/filter/graphicfilter.cxx |2
vcl/source/filter/ixpm/xpmread.cxx |3
vcl/workben/fftester.cxx|2
vcl/workben/xpmfuzzer.cxx |2
9 files changed, 383 insertions(+), 4 deletions(-)
New commits:
commit 80da19ae298b4b4d8802906f88fde0c0f9348765
Author: Tomaž Vajngerl
AuthorDate: Wed Mar 17 14:20:43 2021 +0900
Commit: Tomaž Vajngerl
CommitDate: Thu Mar 18 04:02:36 2021 +0100
vcl: test for reading the XPM format
Change-Id: I416a1c02d737dba716b55a7eb902181c3cff22b6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112598
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/vcl/CppunitTest_vcl_bitmap_test.mk
b/vcl/CppunitTest_vcl_bitmap_test.mk
index 187bb6871845..3e28b96b62e9 100644
--- a/vcl/CppunitTest_vcl_bitmap_test.mk
+++ b/vcl/CppunitTest_vcl_bitmap_test.mk
@@ -17,6 +17,7 @@ $(eval $(call
gb_CppunitTest_add_exception_objects,vcl_bitmap_test, \
vcl/qa/cppunit/BitmapScaleTest \
vcl/qa/cppunit/BitmapFilterTest \
vcl/qa/cppunit/BmpFilterTest \
+vcl/qa/cppunit/XpmFilterTest \
))
$(eval $(call gb_CppunitTest_use_externals,vcl_bitmap_test,\
diff --git a/vcl/source/filter/ixpm/xpmread.hxx b/vcl/inc/filter/XpmReader.hxx
similarity index 100%
rename from vcl/source/filter/ixpm/xpmread.hxx
rename to vcl/inc/filter/XpmReader.hxx
diff --git a/vcl/qa/cppunit/XpmFilterTest.cxx b/vcl/qa/cppunit/XpmFilterTest.cxx
new file mode 100644
index ..121dc62a4fd6
--- /dev/null
+++ b/vcl/qa/cppunit/XpmFilterTest.cxx
@@ -0,0 +1,76 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include
+
+#include
+#include
+#include
+#include
+
+class XpmFilterTest : public test::BootstrapFixture
+{
+public:
+OUString maDataUrl;
+OUString getFullUrl(std::u16string_view sFileName)
+{
+return m_directories.getURLFromSrc(maDataUrl) + sFileName;
+}
+XpmFilterTest()
+: maDataUrl(u"/vcl/qa/cppunit/data/")
+{
+}
+};
+
+CPPUNIT_TEST_FIXTURE(XpmFilterTest, testXPM_8bit)
+{
+SvFileStream aFileStream(getFullUrl(u"XPM_8.xpm"), StreamMode::READ);
+Graphic aGraphic;
+CPPUNIT_ASSERT(ImportXPM(aFileStream, aGraphic));
+auto aBitmap = aGraphic.GetBitmapEx();
+CPPUNIT_ASSERT_EQUAL(tools::Long(4), aBitmap.GetSizePixel().Width());
+CPPUNIT_ASSERT_EQUAL(tools::Long(4), aBitmap.GetSizePixel().Height());
+CPPUNIT_ASSERT_EQUAL(sal_uInt16(8), aBitmap.GetBitCount());
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTBLUE, aBitmap.GetPixelColor(0, 0));
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTRED, aBitmap.GetPixelColor(2, 0));
+CPPUNIT_ASSERT_EQUAL(COL_YELLOW, aBitmap.GetPixelColor(0, 2));
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTGREEN, aBitmap.GetPixelColor(2, 2));
+}
+
+CPPUNIT_TEST_FIXTURE(XpmFilterTest, testXPM_4bit)
+{
+SvFileStream aFileStream(getFullUrl(u"XPM_4.xpm"), StreamMode::READ);
+Graphic aGraphic;
+CPPUNIT_ASSERT(ImportXPM(aFileStream, aGraphic));
+auto aBitmap = aGraphic.GetBitmapEx();
+CPPUNIT_ASSERT_EQUAL(tools::Long(4), aBitmap.GetSizePixel().Width());
+CPPUNIT_ASSERT_EQUAL(tools::Long(4), aBitmap.GetSizePixel().Height());
+CPPUNIT_ASSERT_EQUAL(sal_uInt16(4), aBitmap.GetBitCount());
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTBLUE, aBitmap.GetPixelColor(0, 0));
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTRED, aBitmap.GetPixelColor(2, 0));
+CPPUNIT_ASSERT_EQUAL(COL_YELLOW, aBitmap.GetPixelColor(0, 2));
+CPPUNIT_ASSERT_EQUAL(COL_LIGHTGREEN, aBitmap.GetPixelColor(2, 2));
+}
+
+CPPUNIT_TEST_FIXTURE(XpmFilterTest, testXPM_1bit)
+{
+SvFileStream aFileStream(getFullUrl(u"XPM_1.xpm"), StreamMode::READ);
+Graphic aGraphic;
+CPPUNIT_ASSERT(ImportXPM(aFileStream, aGraphic));
+auto aBitmap = aGraphic.GetBitmapEx();
+CPPUNIT_ASSERT_EQUAL(tools::Long(10), aBitmap.GetSizePixel().Width());
+CPPUNIT_ASSERT_EQUAL(tools::Long(10), aBitmap.GetSizePixel().Height());
+CPPUNIT_ASSERT_EQUAL(sal_uInt16(1), aBitmap.GetBitCount());
+CPPUNIT_ASSERT_EQUAL(Color(0xff), aBitmap.GetPixelColor(0, 0));
+CPPUNIT_ASSERT_EQUAL(Color(0x72d1c8), aBitmap.GetPixelColor(1, 1));
+CPPUNIT_ASSERT_EQUAL(Color(0x72d1c8), aBitmap.GetPixelColor(8, 8));
+CPPUNIT_ASSERT_EQUAL(Color(0xff), aBitmap.GetPixelColor(9, 9));
+}
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/vcl/qa/cppunit/data/XPM_1.xpm b/vcl/qa/cppunit/data/XPM_1.xpm
new file mode 100644
index
[Libreoffice-bugs] [Bug 141090] New: Direct Cursor causes instant slowdown in v7.xx of Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=141090 Bug ID: 141090 Summary: Direct Cursor causes instant slowdown in v7.xx of Writer Product: LibreOffice Version: 7.1.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@macktek.com Description: Enabling Direct Cursor automatically creates severe lag in writer. In prior versions I have used Direct Cursor for all my documents. Resetting my Profile removed Direct Cursor. Lag was not present since Direct Cursor was unchecked. Upon re-activating direct cursor, the problem is very noticeable. There is a lot of cursor lag and delay in typing especially with images in the document. Steps to Reproduce: 1.Open any doc with images. 2. Go into tools/options/Libre Office Writer/Formatting Aids, and check Direct Cursor under the Direct Cursor section. 3. Try moving and repositioning your cursor. Actual Results: VERY slow when Direct Cursor is on. Expected Results: If Direct Cursor is not active, then it works fine. The expected result is that it should work well when Direct Cursor is checked... Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 32; OS: Windows 10.0 Build 17763; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL This explains why "resetting" my profile works... because direct cursor gets unchecked when you reset. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 137741] Fields objects should be navigable in Navigator and the Find bar
https://bugs.documentfoundation.org/show_bug.cgi?id=137741 --- Comment #9 from Jim Raykowski --- Created attachment 170541 --> https://bugs.documentfoundation.org/attachment.cgi?id=170541=edit demo of navigator field category Hi All, Here is effort to realize the Navigator Field category part of this enhancement request. It would be great if someone could provide a test document that is more realistic than what is used in the demo. https://gerrit.libreoffice.org/c/core/+/112560 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140752] .uno.DefaultNumbering and .uno:defaultBullet (on Formatting bar) modify a list style -- should it?
https://bugs.documentfoundation.org/show_bug.cgi?id=140752 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #2) > Cannot follow. What I do is > > 1. Add some lines of text a,b,c > 2. Apply list style "Numbering 123" via stylist to these lines > 3. Per "Toggle Ordered List" on the toolbar I switch to round brackets 4. Open Styles deck and edit list style Numbering 123 to confirm in the style dialog that the change has also been registered for Numbering 123 List style. Whether it was the developers intention or not (comment 4), it also seems like a UI/UX problem. If you (by mistake) used the dropdown box in the Formatting toolbar to change the numbering scheme of your list style, as in your example (or even worse, choose the lower right corner in the Outline tab of B dialog), then any formatting that you did with position and customize is lost in your Numbering 123 list style. Afaict, all operations in the Bullets and Numbering dialog (including Outline) will modify the settings in a list style. This is not consistent with the usual style interactions (i.e., with character and paragraph, using character or paragraph dialog or using Formatting bar does not modify CS or PS). My aim with this bug report is to highlight this issue -- in the belief that others will find it problematic - and might try to address the problem. Even if the existing underlying implementation of lists is not changed, there are probably a number of UI changes that could be done to preserve the "mythic" beliefs around significant differences between DF and List Styles. Bug 140612 was one small UI suggestion in that direction. But now I think my aim is achieved, so I will leave the matter to more qualified persons. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 140752] .uno.DefaultNumbering and .uno:defaultBullet (on Formatting bar) modify a list style -- should it?
https://bugs.documentfoundation.org/show_bug.cgi?id=140752 --- Comment #5 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #2) > Cannot follow. What I do is > > 1. Add some lines of text a,b,c > 2. Apply list style "Numbering 123" via stylist to these lines > 3. Per "Toggle Ordered List" on the toolbar I switch to round brackets 4. Open Styles deck and edit list style Numbering 123 to confirm in the style dialog that the change has also been registered for Numbering 123 List style. Whether it was the developers intention or not (comment 4), it also seems like a UI/UX problem. If you (by mistake) used the dropdown box in the Formatting toolbar to change the numbering scheme of your list style, as in your example (or even worse, choose the lower right corner in the Outline tab of B dialog), then any formatting that you did with position and customize is lost in your Numbering 123 list style. Afaict, all operations in the Bullets and Numbering dialog (including Outline) will modify the settings in a list style. This is not consistent with the usual style interactions (i.e., with character and paragraph, using character or paragraph dialog or using Formatting bar does not modify CS or PS). My aim with this bug report is to highlight this issue -- in the belief that others will find it problematic - and might try to address the problem. Even if the existing underlying implementation of lists is not changed, there are probably a number of UI changes that could be done to preserve the "mythic" beliefs around significant differences between DF and List Styles. Bug 140612 was one small UI suggestion in that direction. But now I think my aim is achieved, so I will leave the matter to more qualified persons. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/content.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit 005adbefc746f9024adcf572c287dc061acbcf00
Author: Jim Raykowski
AuthorDate: Tue Mar 9 12:06:20 2021 -0900
Commit: Jim Raykowski
CommitDate: Thu Mar 18 01:50:50 2021 +0100
Sw Navigator: fix table selection
Fixes table selection from the Navigator not selecting the whole table.
Change-Id: If6a9161d011a056aad02c3bd99c19e62802288c7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112254
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/source/uibase/utlui/content.cxx
b/sw/source/uibase/utlui/content.cxx
index d70494d64cc7..fe9da9cfc0e1 100644
--- a/sw/source/uibase/utlui/content.cxx
+++ b/sw/source/uibase/utlui/content.cxx
@@ -3953,7 +3953,7 @@ void SwContentTree::ExecuteContextMenuAction(const
OString& rSelectedPopupEntry)
case 804:
ExecCommand("demote", true);
break;
-case 805:
+case 805: // select document content
{
m_pActiveShell->KillPams();
m_pActiveShell->ClearMark();
@@ -3973,7 +3973,7 @@ void SwContentTree::ExecuteContextMenuAction(const
OString& rSelectedPopupEntry)
else if (eTypeId == ContentTypeId::TABLE)
{
m_pActiveShell->GotoTable(pCnt->GetName());
-m_pActiveShell->SelAll();
+
m_pActiveShell->GetView().GetViewFrame()->GetDispatcher()->Execute(FN_TABLE_SELECT_ALL);
}
else if (eTypeId == ContentTypeId::REGION)
{
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'distro/lhm/libreoffice-6-4+backports' - dbaccess/source xmlsecurity/CppunitTest_xmlsecurity_signing.mk xmlsecurity/qa
dbaccess/source/core/dataaccess/ModelImpl.cxx | 11 -
xmlsecurity/CppunitTest_xmlsecurity_signing.mk |1
xmlsecurity/qa/unit/signing/data/odb_signed_macros.odb |binary
xmlsecurity/qa/unit/signing/signing2.cxx | 127 +
4 files changed, 135 insertions(+), 4 deletions(-)
New commits:
commit 5a25faaa27cfed40bb6a9406146719599ba99e47
Author: Samuel Mehrbrodt
AuthorDate: Thu May 7 12:03:48 2020 +0200
Commit: Thorsten Behrens
CommitDate: Thu Mar 18 01:15:54 2021 +0100
tdf#97694 Add test for macro signature preservation in Base
Conflicts:
dbaccess/source/core/dataaccess/ModelImpl.cxx
Change-Id: I35fb8d499eed66f9a5e208a4778a1f0f12637079
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93630
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112638
Tested-by: Thorsten Behrens
Reviewed-by: Thorsten Behrens
diff --git a/dbaccess/source/core/dataaccess/ModelImpl.cxx
b/dbaccess/source/core/dataaccess/ModelImpl.cxx
index d5c3b9b3e086..21e45033ea4f 100644
--- a/dbaccess/source/core/dataaccess/ModelImpl.cxx
+++ b/dbaccess/source/core/dataaccess/ModelImpl.cxx
@@ -856,14 +856,17 @@ bool
ODatabaseModelImpl::commitStorageIfWriteable_ignoreErrors( const Reference<
aTempFile.EnableKillingFile();
OUString m_sTmpFileUrl = aTempFile.GetURL();
SignatureState aSignatureState = getScriptingSignatureState();
-if (aSignatureState == SignatureState::OK
-|| aSignatureState == SignatureState::NOTVALIDATED
-|| aSignatureState == SignatureState::INVALID)
+OUString sLocation = getDocFileLocation();
+bool bIsEmbedded = sLocation.startsWith("vnd.sun.star.pkg:") &&
sLocation.endsWith("/EmbeddedDatabase");
+if (!bIsEmbedded && !sLocation.isEmpty()
+&& (aSignatureState == SignatureState::OK || aSignatureState ==
SignatureState::NOTVALIDATED
+|| aSignatureState == SignatureState::INVALID
+|| aSignatureState == SignatureState::UNKNOWN))
{
bTryToPreserveScriptSignature = true;
// We need to first save the file (which removes the macro signature),
then add the macro signature again.
// For that, we need a temporary copy of the original file.
-osl::File::RC rc = osl::File::copy(getDocFileLocation(),
m_sTmpFileUrl);
+osl::File::RC rc = osl::File::copy(sLocation, m_sTmpFileUrl);
if (rc != osl::FileBase::E_None)
throw uno::RuntimeException("Could not create temp file");
}
diff --git a/xmlsecurity/CppunitTest_xmlsecurity_signing.mk
b/xmlsecurity/CppunitTest_xmlsecurity_signing.mk
index 84e7a76c043b..7d0c5200ff27 100644
--- a/xmlsecurity/CppunitTest_xmlsecurity_signing.mk
+++ b/xmlsecurity/CppunitTest_xmlsecurity_signing.mk
@@ -13,6 +13,7 @@ $(eval $(call gb_CppunitTest_CppunitTest,xmlsecurity_signing))
$(eval $(call gb_CppunitTest_add_exception_objects,xmlsecurity_signing, \
xmlsecurity/qa/unit/signing/signing \
+ xmlsecurity/qa/unit/signing/signing2 \
))
$(eval $(call gb_CppunitTest_use_libraries,xmlsecurity_signing, \
diff --git a/xmlsecurity/qa/unit/signing/data/odb_signed_macros.odb
b/xmlsecurity/qa/unit/signing/data/odb_signed_macros.odb
new file mode 100644
index ..3e90f4514599
Binary files /dev/null and
b/xmlsecurity/qa/unit/signing/data/odb_signed_macros.odb differ
diff --git a/xmlsecurity/qa/unit/signing/signing2.cxx
b/xmlsecurity/qa/unit/signing/signing2.cxx
new file mode 100644
index ..152d62a18974
--- /dev/null
+++ b/xmlsecurity/qa/unit/signing/signing2.cxx
@@ -0,0 +1,127 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include
+
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+using namespace css;
+
+namespace
+{
+char const DATA_DIRECTORY[] = "/xmlsecurity/qa/unit/signing/data/";
+}
+
+/// Testsuite for the document signing feature.
+class SigningTest2 : public test::BootstrapFixture, public
unotest::MacrosTest, public XmlTestTools
+{
+protected:
+uno::Reference mxComponentContext;
+uno::Reference mxComponent;
+uno::Reference mxSEInitializer;
+uno::Reference mxSecurityContext;
+
+public:
+SigningTest2();
+virtual void setUp() override;
+virtual void tearDown() override;
+void registerNamespaces(xmlXPathContextPtr& pXmlXpathCtx) override;
+};
+
+SigningTest2::SigningTest2() {}
+
+void SigningTest2::setUp()
+{
+test::BootstrapFixture::setUp();
+
+// Initialize crypto after setting up the
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 7053ec94b47432aad6c5d1d82dd85e41bc08d2ac Author: Seth Chaiklin AuthorDate: Thu Mar 18 01:05:07 2021 +0100 Commit: Gerrit Code Review CommitDate: Thu Mar 18 01:05:07 2021 +0100 Update git submodules * Update helpcontent2 from branch 'master' to 367a4f5cf3d78adaeec36715a37286a6a2cea694 - tdf#139667 update numbering paragraphs; joining lists; chapter numbering ( swriter/01/0606.xhp ) + variable to tip about using Chapter Numbering dialog to add numbering to headings, so that it can be embedded in other help pages. + add links in tip to Tools - Chapter Numbering and other icons, toolbars, and dialogs mentioned in the tip. + Emphasize in the tip to use the Chapter Numbering dialog instead of direct formatting, when adding numbering to Headings. ( swriter/guide/join_numbered_lists.xhp ) * "numbered" -> "ordered" * "Numbering On/Off" -> "Toggle Ordered List" * In paragraphs with changes, update to + add a about "Add to List", with link to relevant page. * update to ,, ( swriter/guide/numbering_paras.xhp ) * "numbered" -> "ordered" * replace tip about chapter numbering with embed from swriter/01/0606.xhp * "Numbering On/Off" -> "No List" Change-Id: I242bfef2535d5fbcd95355d79e77403ce0071679 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/112518 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index 5ed37664620c..367a4f5cf3d7 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 5ed37664620c9e664b06c4660529ad0f200bbc5e +Subproject commit 367a4f5cf3d78adaeec36715a37286a6a2cea694 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/0606.xhp |2 +- source/text/swriter/guide/join_numbered_lists.xhp | 17 + source/text/swriter/guide/numbering_paras.xhp | 16 3 files changed, 18 insertions(+), 17 deletions(-) New commits: commit 367a4f5cf3d78adaeec36715a37286a6a2cea694 Author: Seth Chaiklin AuthorDate: Mon Mar 15 17:42:29 2021 +0100 Commit: Adolfo Jayme Barrientos CommitDate: Thu Mar 18 01:05:07 2021 +0100 tdf#139667 update numbering paragraphs; joining lists; chapter numbering ( swriter/01/0606.xhp ) + variable to tip about using Chapter Numbering dialog to add numbering to headings, so that it can be embedded in other help pages. + add links in tip to Tools - Chapter Numbering and other icons, toolbars, and dialogs mentioned in the tip. + Emphasize in the tip to use the Chapter Numbering dialog instead of direct formatting, when adding numbering to Headings. ( swriter/guide/join_numbered_lists.xhp ) * "numbered" -> "ordered" * "Numbering On/Off" -> "Toggle Ordered List" * In paragraphs with changes, update to + add a about "Add to List", with link to relevant page. * update to ,, ( swriter/guide/numbering_paras.xhp ) * "numbered" -> "ordered" * replace tip about chapter numbering with embed from swriter/01/0606.xhp * "Numbering On/Off" -> "No List" Change-Id: I242bfef2535d5fbcd95355d79e77403ce0071679 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/112518 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/swriter/01/0606.xhp b/source/text/swriter/01/0606.xhp index 677c488e1..8fef88075 100644 --- a/source/text/swriter/01/0606.xhp +++ b/source/text/swriter/01/0606.xhp @@ -39,7 +39,7 @@ Chapter numbering is linked to paragraph styles. By default, the "Heading" paragraph styles (1-10) are assigned to the corresponding chapter and outline number levels (1-10). If you want, you can assign different paragraph styles to the outline number level. -If you want numbered headings, use the Chapter Numbering dialog. Do not use the Toggle Ordered List icon on the Formatting bar. +If you want numbered headings, choose Tools - Chapter Numbering. This command opens a dialog where numbering schemes can be assigned to paragraph styles used for headings. Do not use the Toggle Ordered List icon on the Formatting Bar or the Format - Bullets and Numbering dialog. diff --git a/source/text/swriter/guide/join_numbered_lists.xhp b/source/text/swriter/guide/join_numbered_lists.xhp index 7fa6db49e..f343d4a52 100644 --- a/source/text/swriter/guide/join_numbered_lists.xhp +++ b/source/text/swriter/guide/join_numbered_lists.xhp @@ -35,22 +35,21 @@ paragraphs;numbering non-consecutive +Combining Ordered Lists +You can combine two ordered lists into a single list. -Combining Numbered Lists -You can combine numbered lists into a single consecutively numbered list. - -To Combine Consecutive Numbered Lists +To Combine Two Ordered Lists Select all of the paragraphs in the lists. -On the Formatting Bar, click the Numbering On/Off icon twice. +On the Formatting Bar, click the Toggle Ordered List icon twice. -To Create a Numbered List From Non-consecutive Paragraphs: +To Create a Ordered List From Non-consecutive Paragraphs @@ -60,16 +59,18 @@ Continue to hold down CommandCtrl, and drag a selection in each numbered paragraph of the lists you want to combine. -On the Formatting Bar, click the Numbering On/Off icon twice. +On the Formatting Bar, click the Toggle Ordered List icon twice. - +To add selected paragraphs to an existing list, use Format - Lists - Add to List. + + diff --git a/source/text/swriter/guide/numbering_paras.xhp b/source/text/swriter/guide/numbering_paras.xhp index 4bf7f70de..ddf4c84e8 100644 --- a/source/text/swriter/guide/numbering_paras.xhp +++ b/source/text/swriter/guide/numbering_paras.xhp @@ -20,7 +20,7 @@ -Modifying Numbering in a Numbered List +Modifying Numbering in an Ordered List /text/swriter/guide/numbering_paras.xhp @@ -37,11 +37,11 @@ MW changed "removing;..." to "deleting;...", and deleted "modifying;..." -Modifying Numbering in a Numbered List -You can remove the numbering from a paragraph in a numbered list or change the number that a numbered list starts with. -If you want numbered headings, use the Tools - Chapter Numbering menu command to assign a numbering to a paragraph style. Do not use the Numbering icon on the Formatting toolbar. +Modifying Numbering in an Ordered List +You can remove the numbering from a paragraph in an ordered list or change the number that an ordered list starts with. +
[Libreoffice-bugs] [Bug 140321] Fontwork: Change in surface has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=140321 --- Comment #4 from Regina Henschel --- It seems, that this four materials correspond to the OOXML material presets legacyMatte, legacyMetal, legacyPlastic and legacyWireframe, which are specified in section 20.1.10.50 ST_PresetMaterialType (Preset Material Type) in ISO/IEC 29500-1:2016(E). But in case someone really wants to implement it, I suggest to use material presets, which are currently available in the UI of MS Office. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141081] Unwanted lines around images inserted into ODT documents
https://bugs.documentfoundation.org/show_bug.cgi?id=141081 --- Comment #6 from david.c@virgin.net --- Wow. Granted, not a bug. It vanished when switched off. That being said, add some hovering tooltip - I would _never_ have thought to equate a random line around an image with "text boundary" visibility. Just looks like a random image aberration. Hence the bug report. Thanks for explaining. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127463] FILEOPEN DOCX Table made from grouped shapes shows up in the table
https://bugs.documentfoundation.org/show_bug.cgi?id=127463 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8693| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96640] FORMATTING: (Grouped) drawing objects are rendered in a wrong way (.docx file)
https://bugs.documentfoundation.org/show_bug.cgi?id=96640 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8693| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127370] FILEOPEN DOCX Images in header and footer lose alignment settings
https://bugs.documentfoundation.org/show_bug.cgi?id=127370 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8693| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122717] FILEOPEN Horizontal line in DOCX has wrong size/position
https://bugs.documentfoundation.org/show_bug.cgi?id=122717 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |8693| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140854] Base VIEWING - darkened columns for Memo [LONGVARCHAR]
https://bugs.documentfoundation.org/show_bug.cgi?id=140854 --- Comment #8 from Yannick Chiron --- Bug still present in LibreOffice 7.1.2 RC1. Bug not present in LibreOffice 7.0.5, so I reverted to it while a fix is found. Let me know if I can be of further assistance. Thanks for your work. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127555] Formatting, regression. Grouped drawing object on a wrong page and overlaps another drawing object
https://bugs.documentfoundation.org/show_bug.cgi?id=127555 --- Comment #8 from Aron Budea --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141089] Chart does not get inserted in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=141089 An-Kh changed: What|Removed |Added CC||anshukhar...@gmail.com --- Comment #1 from An-Kh --- Created attachment 170540 --> https://bugs.documentfoundation.org/attachment.cgi?id=170540=edit Chart Insertion -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141089] New: Chart does not get inserted in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=141089 Bug ID: 141089 Summary: Chart does not get inserted in LibreOffice Calc Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: anshukhar...@gmail.com Description: If we insert a chart (let say bar chart), in calc it does not get inserted. Please have a look at the attachment Steps to Reproduce: 1.Open spreadsheet in LibreOffice Calc 2.Menubar -> Insert -> Chart Actual Results: Chart does not get inserted Expected Results: Chart should be inserted Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d809066ff7cd2f75d1f8569085ae39f375a783fa CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: default; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138706] [META] Regressions from "tdf106792 Get rid of SvxShapePolyPolygonBezier"
https://bugs.documentfoundation.org/show_bug.cgi?id=138706 Bug 138706 depends on bug 96640, which changed state. Bug 96640 Summary: FORMATTING: (Grouped) drawing objects are rendered in a wrong way (.docx file) https://bugs.documentfoundation.org/show_bug.cgi?id=96640 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Bug 136328 depends on bug 96640, which changed state. Bug 96640 Summary: FORMATTING: (Grouped) drawing objects are rendered in a wrong way (.docx file) https://bugs.documentfoundation.org/show_bug.cgi?id=96640 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96640] FORMATTING: (Grouped) drawing objects are rendered in a wrong way (.docx file)
https://bugs.documentfoundation.org/show_bug.cgi?id=96640 Xisco Faulí changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #13 from Xisco Faulí --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138706] [META] Regressions from "tdf106792 Get rid of SvxShapePolyPolygonBezier"
https://bugs.documentfoundation.org/show_bug.cgi?id=138706 Bug 138706 depends on bug 127370, which changed state. Bug 127370 Summary: FILEOPEN DOCX Images in header and footer lose alignment settings https://bugs.documentfoundation.org/show_bug.cgi?id=127370 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Bug 136328 depends on bug 127370, which changed state. Bug 127370 Summary: FILEOPEN DOCX Images in header and footer lose alignment settings https://bugs.documentfoundation.org/show_bug.cgi?id=127370 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104522] [META] DOCX (OOXML) header & footer-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104522 Bug 104522 depends on bug 127370, which changed state. Bug 127370 Summary: FILEOPEN DOCX Images in header and footer lose alignment settings https://bugs.documentfoundation.org/show_bug.cgi?id=127370 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127370] FILEOPEN DOCX Images in header and footer lose alignment settings
https://bugs.documentfoundation.org/show_bug.cgi?id=127370 Xisco Faulí changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Xisco Faulí --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138706] [META] Regressions from "tdf106792 Get rid of SvxShapePolyPolygonBezier"
https://bugs.documentfoundation.org/show_bug.cgi?id=138706 Bug 138706 depends on bug 127463, which changed state. Bug 127463 Summary: FILEOPEN DOCX Table made from grouped shapes shows up in the table https://bugs.documentfoundation.org/show_bug.cgi?id=127463 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Bug 136328 depends on bug 127463, which changed state. Bug 127463 Summary: FILEOPEN DOCX Table made from grouped shapes shows up in the table https://bugs.documentfoundation.org/show_bug.cgi?id=127463 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127463] FILEOPEN DOCX Table made from grouped shapes shows up in the table
https://bugs.documentfoundation.org/show_bug.cgi?id=127463 Xisco Faulí changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #7 from Xisco Faulí --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138706] [META] Regressions from "tdf106792 Get rid of SvxShapePolyPolygonBezier"
https://bugs.documentfoundation.org/show_bug.cgi?id=138706 Bug 138706 depends on bug 139651, which changed state. Bug 139651 Summary: FILEOPEN Object layout shifts after import from docx into libreoffice https://bugs.documentfoundation.org/show_bug.cgi?id=139651 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104442] [META] OOXML shape (DrawingML and VML) related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104442 Bug 104442 depends on bug 139651, which changed state. Bug 139651 Summary: FILEOPEN Object layout shifts after import from docx into libreoffice https://bugs.documentfoundation.org/show_bug.cgi?id=139651 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139651] FILEOPEN Object layout shifts after import from docx into libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=139651 Xisco Faulí changed: What|Removed |Added CC||xiscofa...@libreoffice.org Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Xisco Faulí --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138706] [META] Regressions from "tdf106792 Get rid of SvxShapePolyPolygonBezier"
https://bugs.documentfoundation.org/show_bug.cgi?id=138706 Bug 138706 depends on bug 131275, which changed state. Bug 131275 Summary: Fileopen DOCX: Organigram wrong again https://bugs.documentfoundation.org/show_bug.cgi?id=131275 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Bug 136328 depends on bug 131275, which changed state. Bug 131275 Summary: Fileopen DOCX: Organigram wrong again https://bugs.documentfoundation.org/show_bug.cgi?id=131275 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 131275] Fileopen DOCX: Organigram wrong again
https://bugs.documentfoundation.org/show_bug.cgi?id=131275 Xisco Faulí changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Xisco Faulí --- *** This bug has been marked as a duplicate of bug 118693 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141086] Password asked in a loop when open a file on a WebDav Server
https://bugs.documentfoundation.org/show_bug.cgi?id=141086 --- Comment #2 from Uwe Auer --- repro Version: 7.1.1.2 / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118693] FILEOPEN: Drawing has incorrect size
https://bugs.documentfoundation.org/show_bug.cgi?id=118693 Xisco Faulí changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |xiscofa...@libreoffice.org |desktop.org | --- Comment #14 from Xisco Faulí --- I think I know how to fix this... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140579] It's unclear, how "Continue previous numbering" should work
https://bugs.documentfoundation.org/show_bug.cgi?id=140579 --- Comment #42 from sdc.bla...@youmail.dk --- Created attachment 170539 --> https://bugs.documentfoundation.org/attachment.cgi?id=170539=edit Possible final version for "Add to List" help (In reply to Dieter from comment #41) > So perhaps "target list" could be a solution? But it's up to you > to decide. Left as is. Seems less problematic than other "solutions". "target" introduces a new undefined term. (btw, this difficulty is related to the query in comment 23 about the necessity of a first step to "choose a list") See attached for new version. > We should use it as a starting point and we will see if some > modifications are needed later. Agree. This page is supposed to explain the operation of the command. But there are many interesting and useful ways that the command can be used. For example, to add items "before" the list (see Test 2 in comment 33 for one example). Perhaps you also imagine a "guide" page, that gives some examples of typical "use cases", that shows what the command can be used for, rather than explaining the basic procedure for how the command works (which is still only formulated empirically by induction from experiment - have not tried to find the source code). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141081] Unwanted lines around images inserted into ODT documents
https://bugs.documentfoundation.org/show_bug.cgi?id=141081 --- Comment #5 from Uwe Auer --- This looks like option View -> [ ] Text Boundaries visual aid and not a bug. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Unit Tests failing when built with clang 12
Sounds like there is a headless or distro dependent aspect of this bug too. I can reproduce this on both my i686 openSUSE Tumbleweed (32-bit) laptop and on my x86-64 openSUSE Tumbleweed desktop. This issue has not been fixed in clang 13 as today's build 402f2cae7dcab also fails. I also was able to reproduce the failures with this autogen.input: --enable-optimized --disable-debug --disable-dbgutil CC=clang CXX=clang++ What distro is this working on? I can try that in a VM. -Luke ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 134236] Enable Writer in "Web View" to keep focus on text cursor when resizing program window
https://bugs.documentfoundation.org/show_bug.cgi?id=134236 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval --- Comment #4 from V Stuart Foote --- Holding the Writer edit cursor position focus when moving between Normal view and Web view would really be helpful. But kind of expect that calculating the position in document reliably between the two modes requires new dev effort. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 134236] Enable Writer in "Web View" to keep focus on text cursor when resizing program window
https://bugs.documentfoundation.org/show_bug.cgi?id=134236 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval --- Comment #4 from V Stuart Foote --- Holding the Writer edit cursor position focus when moving between Normal view and Web view would really be helpful. But kind of expect that calculating the position in document reliably between the two modes requires new dev effort. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 141086] Password asked in a loop when open a file on a WebDav Server
https://bugs.documentfoundation.org/show_bug.cgi?id=141086 --- Comment #1 from Uwe Auer --- *** Bug 141087 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141087] Password asked in a loop when open a file on a WebDav Server
https://bugs.documentfoundation.org/show_bug.cgi?id=141087 Uwe Auer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Uwe Auer --- *** This bug has been marked as a duplicate of bug 141086 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141077] Writer Web mode should be one-column, instead it shows meaningless page breaks and column jumps
https://bugs.documentfoundation.org/show_bug.cgi?id=141077 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval --- Comment #2 from V Stuart Foote --- much like the requests to make the pagination in Web view relate to its Normal view layout--eliminating the otherwise functional page layout in columns offers no real benefit. If you want to use the uncluttered Web view layout to write in, great. Just accept that its VCL handling is calculated against an unisized page (10 meters tall, at the current app frame width minus controls). Reflowing from Web view to Normal view, or reverse, will otherwise honor the page settings of the document. If you don't want columns in Web view reformat the page style for the document to single column--you can't have it both ways. Single column in Web view and multicolumn in Normal view. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 141077] Writer Web mode should be one-column, instead it shows meaningless page breaks and column jumps
https://bugs.documentfoundation.org/show_bug.cgi?id=141077 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Keywords||needsUXEval --- Comment #2 from V Stuart Foote --- much like the requests to make the pagination in Web view relate to its Normal view layout--eliminating the otherwise functional page layout in columns offers no real benefit. If you want to use the uncluttered Web view layout to write in, great. Just accept that its VCL handling is calculated against an unisized page (10 meters tall, at the current app frame width minus controls). Reflowing from Web view to Normal view, or reverse, will otherwise honor the page settings of the document. If you don't want columns in Web view reformat the page style for the document to single column--you can't have it both ways. Single column in Web view and multicolumn in Normal view. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 67698] VIEWING: Implement 'Normal View' that includes the real page numbers in a 'Web Layout'-type view (comment #7)
https://bugs.documentfoundation.org/show_bug.cgi?id=67698 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu --- Comment #14 from V Stuart Foote --- Page numbers in Web view are recalculated against a 10 meter page size [1], while paragraphs reflow with no margins to extent of canvas exposed in the app frame at any selected zoom. =-ref-= [1] https://opengrok.libreoffice.org/xref/core/sw/source/core/inc/frmtool.hxx?r=ebe1f639#54 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140579] It's unclear, how "Continue previous numbering" should work
https://bugs.documentfoundation.org/show_bug.cgi?id=140579 --- Comment #41 from Dieter --- (In reply to sdc.blanco from comment #40) > Proposed alternative: > > Select paragraphs to be added to a list. Paragraphs can be in a different > list or no list at all. I was talking about the "target" list and not the list where parapgraphs are selected. So perhaps "target list" could be a solution? But it's up to you to decide. We don't have to go in deeper discussion from my side. > See top of help page (in attachment). Ok? Yes, O.K. I haven't seen this. Sorry for that. > Ok. Something like "Add Selected Paragraphs to a Previous List" from bug > 36220 attachment 169995 [details], but change title to: > "Add Consecutive List Entries to an Immediately Prior List" > 1. Select one or more consecutive list entries, starting from the first > entry, that you want to add to the immediately prior list. > 2. Right-click O.K. > Agree with both points. But what do you think is still missing? Don't know. We should use it as a starting point and we will see if some modifications are needed later. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 116983] Paste is sometimes deactivated in (context) menu even though text is copied to clipboard and CTRL+V functioning (steps: Comment 0 and Comment 13 and Comment 28 and Comm
https://bugs.documentfoundation.org/show_bug.cgi?id=116983 --- Comment #96 from Apt --- So far I can't replicate it in 7.2. Hopefully it stays that way! Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d97528da0c70c43fccd3239cbe8e064c3480bba8 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-ux-advise] [Bug 133786] enable Writer in its 'Web' view mode to display page numbering of its 'Normal' view
https://bugs.documentfoundation.org/show_bug.cgi?id=133786 V Stuart Foote changed: What|Removed |Added Resolution|WONTFIX |DUPLICATE --- Comment #12 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 67698 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 133786] enable Writer in its 'Web' view mode to display page numbering of its 'Normal' view
https://bugs.documentfoundation.org/show_bug.cgi?id=133786 V Stuart Foote changed: What|Removed |Added Resolution|WONTFIX |DUPLICATE --- Comment #12 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 67698 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 67698] VIEWING: Implement 'Normal View' that includes the real page numbers in a 'Web Layout'-type view (comment #7)
https://bugs.documentfoundation.org/show_bug.cgi?id=67698 V Stuart Foote changed: What|Removed |Added CC||tpy...@gmail.com --- Comment #13 from V Stuart Foote --- *** Bug 133786 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: include/vcl vcl/source
include/vcl/glyphitem.hxx | 13
vcl/source/gdi/impglyphitem.cxx | 61
2 files changed, 57 insertions(+), 17 deletions(-)
New commits:
commit d697e792c5b4b27aad8806694e1b8e22dcc70eae
Author: Luboš Luňák
AuthorDate: Tue Mar 16 16:28:02 2021 +0100
Commit: Luboš Luňák
CommitDate: Wed Mar 17 22:49:57 2021 +0100
optimize SalLayoutGlyphs for the common case
This should reduce memory usage (libstdc++ vector is 3 int's and
allocates dynamically). The usual case should be no font fallback.
Change-Id: I2e7981c0962f4f417fd024e3c27f01bc2a71127e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112591
Tested-by: Jenkins
Reviewed-by: Luboš Luňák
diff --git a/include/vcl/glyphitem.hxx b/include/vcl/glyphitem.hxx
index 02d783a3e166..d928bb954ee7 100644
--- a/include/vcl/glyphitem.hxx
+++ b/include/vcl/glyphitem.hxx
@@ -31,7 +31,11 @@ class SalLayoutGlyphsImpl;
class VCL_DLLPUBLIC SalLayoutGlyphs final
{
-std::vector m_pImpls;
+SalLayoutGlyphsImpl* m_pImpl = nullptr;
+// Extra items are in a dynamically allocated vector in order to save
memory.
+// The usual case should be that this stays unused (it should be only used
+// when font fallback takes place).
+std::vector* m_pExtraImpls = nullptr;
public:
SalLayoutGlyphs() = default;
@@ -42,11 +46,8 @@ public:
SalLayoutGlyphs& operator=(const SalLayoutGlyphs&) = delete;
SalLayoutGlyphs& operator=(SalLayoutGlyphs&&);
-SalLayoutGlyphsImpl* Impl(unsigned int nLevel) const
-{
-return nLevel < m_pImpls.size() ? m_pImpls[nLevel] : nullptr;
-}
-void AppendImpl(SalLayoutGlyphsImpl* pImpl) { m_pImpls.push_back(pImpl); }
+SalLayoutGlyphsImpl* Impl(unsigned int nLevel) const;
+void AppendImpl(SalLayoutGlyphsImpl* pImpl);
bool IsValid() const;
void Invalidate();
diff --git a/vcl/source/gdi/impglyphitem.cxx b/vcl/source/gdi/impglyphitem.cxx
index d271032e2ad6..e368305cdba1 100644
--- a/vcl/source/gdi/impglyphitem.cxx
+++ b/vcl/source/gdi/impglyphitem.cxx
@@ -25,35 +25,74 @@
SalLayoutGlyphs::~SalLayoutGlyphs()
{
-for (SalLayoutGlyphsImpl* impl : m_pImpls)
-delete impl;
+delete m_pImpl;
+if (m_pExtraImpls)
+for (SalLayoutGlyphsImpl* impl : *m_pExtraImpls)
+delete impl;
}
-SalLayoutGlyphs::SalLayoutGlyphs(SalLayoutGlyphs&& rOther) {
std::swap(m_pImpls, rOther.m_pImpls); }
+SalLayoutGlyphs::SalLayoutGlyphs(SalLayoutGlyphs&& rOther)
+{
+std::swap(m_pImpl, rOther.m_pImpl);
+std::swap(m_pExtraImpls, rOther.m_pExtraImpls);
+}
SalLayoutGlyphs& SalLayoutGlyphs::operator=(SalLayoutGlyphs&& rOther)
{
if (this != )
-std::swap(m_pImpls, rOther.m_pImpls);
+{
+std::swap(m_pImpl, rOther.m_pImpl);
+std::swap(m_pExtraImpls, rOther.m_pExtraImpls);
+}
return *this;
}
bool SalLayoutGlyphs::IsValid() const
{
-if (m_pImpls.empty())
+if (m_pImpl == nullptr)
+return false;
+if (!m_pImpl->IsValid())
return false;
-for (SalLayoutGlyphsImpl* impl : m_pImpls)
-if (!impl->IsValid())
-return false;
+if (m_pExtraImpls)
+for (SalLayoutGlyphsImpl* impl : *m_pExtraImpls)
+if (!impl->IsValid())
+return false;
return true;
}
void SalLayoutGlyphs::Invalidate()
{
// Invalidating is in fact simply clearing.
-for (SalLayoutGlyphsImpl* impl : m_pImpls)
-delete impl;
-m_pImpls.clear();
+delete m_pImpl;
+m_pImpl = nullptr;
+if (m_pExtraImpls)
+{
+for (SalLayoutGlyphsImpl* impl : *m_pExtraImpls)
+delete impl;
+delete m_pExtraImpls;
+m_pExtraImpls = nullptr;
+}
+}
+
+SalLayoutGlyphsImpl* SalLayoutGlyphs::Impl(unsigned int nLevel) const
+{
+if (nLevel == 0)
+return m_pImpl;
+if (m_pExtraImpls != nullptr && nLevel - 1 < m_pExtraImpls->size())
+return (*m_pExtraImpls)[nLevel - 1];
+return nullptr;
+}
+
+void SalLayoutGlyphs::AppendImpl(SalLayoutGlyphsImpl* pImpl)
+{
+if (m_pImpl == nullptr)
+m_pImpl = pImpl;
+else
+{
+if (m_pExtraImpls == nullptr)
+m_pExtraImpls = new std::vector;
+m_pExtraImpls->push_back(pImpl);
+}
}
SalLayoutGlyphsImpl* SalLayoutGlyphsImpl::clone() const { return new
SalLayoutGlyphsImpl(*this); }
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: include/vcl sc/source svtools/source sw/source vcl/inc vcl/qa vcl/source
include/vcl/glyphitem.hxx | 19 ++
include/vcl/outdev.hxx |6 ++-
include/vcl/vcllayout.hxx |6 +--
sc/source/ui/view/output2.cxx |4 +-
svtools/source/control/ruler.cxx|6 ---
sw/source/core/txtnode/fntcache.cxx |6 ---
vcl/inc/impglyphitem.hxx|7 +--
vcl/inc/sallayout.hxx | 13 --
vcl/qa/cppunit/complextext.cxx | 10 ++---
vcl/source/control/imp_listbox.cxx |6 ---
vcl/source/gdi/CommonSalLayout.cxx | 68 ++--
vcl/source/gdi/impglyphitem.cxx | 42 ++
vcl/source/gdi/sallayout.cxx| 64 +++--
vcl/source/outdev/font.cxx |9 ++--
vcl/source/outdev/text.cxx |4 +-
vcl/source/window/menuitemlist.cxx |6 ---
vcl/source/window/status.cxx| 16
17 files changed, 147 insertions(+), 145 deletions(-)
New commits:
commit 7439cabc643de2f07c18adc35056f802997f484a
Author: Luboš Luňák
AuthorDate: Tue Mar 16 15:04:08 2021 +0100
Commit: Luboš Luňák
CommitDate: Wed Mar 17 22:49:33 2021 +0100
make SalLayoutGlyphs work with MultiSalLayout
Code that needs to lay out texts repeatedly can cache the result
of SalLayout::GetGlyphs() can reuse it. But GetGlyphs() returns
nullptr for MultiSalLayout, so caching for it doesn't work. Worse
still, it actually increases the number of layout calls, because
there's the initial layout for caching and then each call
will need to do the layout again because of the nullptr that's
not cached.
This commit changes SalLayoutGlyphs to possibly include multiple
SalLayoutGlyphsImpl objects, one for each SalLayout handled
by MultiSalLayout. Changes include making GenericSalLayout
work directly with the Impl class, which avoids an indirection
and simplifies code.
Change-Id: Ic4b19934a8a06d4955b51527fe3777c5e91107b2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112590
Tested-by: Jenkins
Reviewed-by: Luboš Luňák
diff --git a/include/vcl/glyphitem.hxx b/include/vcl/glyphitem.hxx
index 7634bd3a4413..02d783a3e166 100644
--- a/include/vcl/glyphitem.hxx
+++ b/include/vcl/glyphitem.hxx
@@ -23,23 +23,30 @@
#include
#include
+#include
+
typedef sal_uInt16 sal_GlyphId;
class SalLayoutGlyphsImpl;
class VCL_DLLPUBLIC SalLayoutGlyphs final
{
-friend class SalLayoutGlyphsImpl;
-SalLayoutGlyphsImpl* m_pImpl;
+std::vector m_pImpls;
public:
-SalLayoutGlyphs();
-SalLayoutGlyphs(const SalLayoutGlyphs&);
+SalLayoutGlyphs() = default;
+SalLayoutGlyphs(const SalLayoutGlyphs&) = delete;
+SalLayoutGlyphs(SalLayoutGlyphs&&);
~SalLayoutGlyphs();
-SalLayoutGlyphs& operator=(const SalLayoutGlyphs&);
+SalLayoutGlyphs& operator=(const SalLayoutGlyphs&) = delete;
+SalLayoutGlyphs& operator=(SalLayoutGlyphs&&);
-SalLayoutGlyphsImpl* Impl() const { return m_pImpl; }
+SalLayoutGlyphsImpl* Impl(unsigned int nLevel) const
+{
+return nLevel < m_pImpls.size() ? m_pImpls[nLevel] : nullptr;
+}
+void AppendImpl(SalLayoutGlyphsImpl* pImpl) { m_pImpls.push_back(pImpl); }
bool IsValid() const;
void Invalidate();
diff --git a/include/vcl/outdev.hxx b/include/vcl/outdev.hxx
index a8d77c77b30e..ce7d54e75689 100644
--- a/include/vcl/outdev.hxx
+++ b/include/vcl/outdev.hxx
@@ -1352,11 +1352,13 @@ public:
SalLayoutFlags flags
= SalLayoutFlags::NONE,
vcl::TextLayoutCache
const* = nullptr) const;
SAL_DLLPRIVATE std::unique_ptr
-ImplGlyphFallbackLayout(
std::unique_ptr, ImplLayoutArgs& ) const;
+ImplGlyphFallbackLayout(
std::unique_ptr,
+ ImplLayoutArgs&,
+ const
SalLayoutGlyphs* ) const;
SAL_DLLPRIVATE std::unique_ptr
getFallbackLayout(
LogicalFontInstance* pLogicalFont, int
nFallbackLevel,
-ImplLayoutArgs& rLayoutArgs) const;
+ImplLayoutArgs& rLayoutArgs, const
SalLayoutGlyphs* ) const;
// Enabling/disabling RTL only makes sense for OutputDevices that use a
mirroring SalGraphicsLayout
diff --git a/include/vcl/vcllayout.hxx b/include/vcl/vcllayout.hxx
index 7d53d12bd40b..e09e54f59d65 100644
--- a/include/vcl/vcllayout.hxx
+++ b/include/vcl/vcllayout.hxx
@@ -24,13 +24,13 @@
#include
#include
#include
+#include
#include
class ImplLayoutArgs;
class PhysicalFontFace;
class SalGraphics;
class GlyphItem;
-class SalLayoutGlyphs;
// all positions/widths are in font units
// one exception: drawposition is in pixel
[Libreoffice-commits] core.git: sw/source
sw/source/core/txtnode/fntcache.cxx | 18 --
1 file changed, 18 deletions(-)
New commits:
commit 9d02d86e8a9111b7a689062eb9a856146a9e80b1
Author: Luboš Luňák
AuthorDate: Fri Mar 12 14:08:11 2021 +0100
Commit: Luboš Luňák
CommitDate: Wed Mar 17 22:49:05 2021 +0100
do not disable Writer font caching on zoom mismatch
This code disables font caching for some cases, e.g. when exporting
to PDF if the zoom is set to anything else than 100%, or also when
loading a document.
It unfortunately comes from the OOo initial import, so it's
impossible to find out why it should be needed. SwFntObj instances
are created only using SwFntAccess ctor, which checks any SwFntObj
it tries to reuse, so if this some additional factor to consider
when reusing SwFntObj, then it can be checked there. But when I
remove the code, I cannot see any breakage. Tests pass, normal
rendering is fine, document thumbnail is fine, printing is fine,
PDF export is fine, embedding in a spreadsheet is fine.
We had a look at this with Miklos and concluded that it is not
needed (until proven otherwise, in which case it'll be also known
why it would be needed).
Change-Id: I59d375229a265a4353c1da6dd067d892dd4ecfb6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112589
Tested-by: Jenkins
Reviewed-by: Luboš Luňák
diff --git a/sw/source/core/txtnode/fntcache.cxx
b/sw/source/core/txtnode/fntcache.cxx
index b0ed8eb4d72b..2327ce0de4ce 100644
--- a/sw/source/core/txtnode/fntcache.cxx
+++ b/sw/source/core/txtnode/fntcache.cxx
@@ -591,24 +591,6 @@ void SwFntObj::CreateScrFont( const SwViewShell& rSh,
const OutputDevice& rOut )
m_pScrFont = m_pPrtFont;
}
-// check zoom factor, e.g. because of PrtOle2 during export
-{
-// In case the zoom factor of the output device differs from the
-// one in the ViewOptions, this Font must not be cached,
-// hence set zoom factor to an invalid value
-tools::Long nTmp;
-if( pOut->GetMapMode().GetScaleX().IsValid() &&
-pOut->GetMapMode().GetScaleY().IsValid() &&
-pOut->GetMapMode().GetScaleX() == pOut->GetMapMode().GetScaleY() )
-{
-nTmp = tools::Long(100 * pOut->GetMapMode().GetScaleX());
-}
-else
-nTmp = 0;
-if( nTmp != m_nZoom )
-m_nZoom = USHRT_MAX - 1;
-}
-
m_nScrAscent = static_cast(pOut->GetFontMetric().GetAscent());
if ( USHRT_MAX == m_nScrHeight )
m_nScrHeight = static_cast(pOut->GetTextHeight());
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 140579] It's unclear, how "Continue previous numbering" should work
https://bugs.documentfoundation.org/show_bug.cgi?id=140579 --- Comment #40 from sdc.bla...@youmail.dk --- (In reply to Dieter from comment #39) > "1. Select ... added to a different list." Because selected paragraphs do not have to be in a list, "different list" would not always be meaningful. Proposed alternative: Select paragraphs to be added to a list. Paragraphs can be in a different list or no list at all. > After step 3: "Result: Selected paragraphs get the labelling and... See top of help page (in attachment). Ok? > I also propose to add a more simplier solution, Ok. Something like "Add Selected Paragraphs to a Previous List" from bug 36220 attachment 169995, but change title to: "Add Consecutive List Entries to an Immediately Prior List" 1. Select one or more consecutive list entries, starting from the first entry, that you want to add to the immediately prior list. 2. Right-click (that formulation will exclude the non-functional Technique D). > Perhaps we still don't have a 100% solution but better than no help. Agree with both points. But what do you think is still missing? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/source
sw/source/core/inc/fntcache.hxx | 23 ++
sw/source/core/txtnode/fntcache.cxx | 136 +---
2 files changed, 103 insertions(+), 56 deletions(-)
New commits:
commit 3f69ec9ab4236de13d229f675943123aeb42ea29
Author: Luboš Luňák
AuthorDate: Thu Mar 11 15:34:41 2021 +0100
Commit: Luboš Luňák
CommitDate: Wed Mar 17 22:48:45 2021 +0100
improve font caching in SwFntObj
The code previously cached only SalGlyphItems, but such caching
fails if SalLayout::GetGlyphs() does not return valid glyphs,
which is the case with MultiSalLayout. Worse, it not only fails,
but layout is once computed for caching, that fails, and is computed
a second time for actual use.
This improved cache caches the result of GetTextWidth(), which
itself improves the performance a bit, but it also allows caching
the value for GetGlyph() not returning valid glyphs. Moreover this
also caches failures to get valid glyphs from GetGlyphs().
There are quite some calls to GetTextArray(), I didn't cache those,
but it might be added if needed.
Change-Id: Ia2589fb1b778f4f154c88f65d9906584284239da
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112588
Tested-by: Jenkins
Reviewed-by: Luboš Luňák
diff --git a/sw/source/core/inc/fntcache.hxx b/sw/source/core/inc/fntcache.hxx
index 61564de93e72..848ad3611c10 100644
--- a/sw/source/core/inc/fntcache.hxx
+++ b/sw/source/core/inc/fntcache.hxx
@@ -60,19 +60,9 @@ void SwClearFntCacheTextGlyphs();
extern SwFntCache *pFntCache;
extern SwFntObj *pLastFont;
-/**
- * Defines a substring on a given output device, to be used as an std::map<>
- * key.
- */
-struct SwTextGlyphsKey
-{
-VclPtr m_pOutputDevice;
-OUString m_aText;
-sal_Int32 m_nIndex;
-sal_Int32 m_nLength;
-
-};
+struct SwTextGlyphsKey;
bool operator<(const SwTextGlyphsKey& l, const SwTextGlyphsKey& r);
+struct SwTextGlyphsData;
class SwFntObj : public SwCacheObj
{
@@ -95,8 +85,8 @@ class SwFntObj : public SwCacheObj
bool m_bSymbol : 1;
bool m_bPaintBlank : 1;
-/// Cache of already calculated layout glyphs.
-std::map m_aTextGlyphs;
+/// Cache of already calculated layout glyphs and text widths.
+std::map m_aTextGlyphs;
static tools::Long nPixWidth;
static MapMode *pPixMap;
@@ -125,7 +115,10 @@ public:
sal_uInt16 GetZoom() const { return m_nZoom; }
sal_uInt16 GetPropWidth() const { return m_nPropWidth; }
bool IsSymbol() const { return m_bSymbol; }
-std::map& GetTextGlyphs() { return
m_aTextGlyphs; }
+
+tools::Long GetCachedTextWidth(const SwTextGlyphsKey& key, const
vcl::TextLayoutCache* vclCache);
+SalLayoutGlyphs* GetCachedSalLayoutGlyphs(const SwTextGlyphsKey& key);
+void ClearCachedTextGlyphs();
void DrawText( SwDrawTextInfo );
/// determine the TextSize (of the printer)
diff --git a/sw/source/core/txtnode/fntcache.cxx
b/sw/source/core/txtnode/fntcache.cxx
index 5b8661b4cf5a..b0ed8eb4d72b 100644
--- a/sw/source/core/txtnode/fntcache.cxx
+++ b/sw/source/core/txtnode/fntcache.cxx
@@ -71,6 +71,28 @@ tools::Long SwFntObj::nPixWidth;
MapMode* SwFntObj::pPixMap = nullptr;
static vcl::DeleteOnDeinit< VclPtr > s_pFntObjPixOut( new
VclPtr );
+/**
+ * Defines a substring on a given output device, to be used as an std::map<>
+ * key.
+ */
+struct SwTextGlyphsKey
+{
+VclPtr m_pOutputDevice;
+OUString m_aText;
+sal_Int32 m_nIndex;
+sal_Int32 m_nLength;
+
+};
+
+/**
+ * Glyphs and text width for the given SwTextGlyphsKey.
+ */
+struct SwTextGlyphsData
+{
+SalLayoutGlyphs m_aTextGlyphs;
+tools::Long m_nTextWidth = -1; // -1 = not computed yet
+};
+
namespace
{
@@ -93,36 +115,6 @@ tools::Long EvalGridWidthAdd( const SwTextGridItem *const
pGrid, const SwDrawTex
return nGridWidthAdd;
}
-/**
- * Pre-calculates glyph items for the rendered subset of rKey's text, assuming
- * outdev state does not change between the outdev calls.
- */
-SalLayoutGlyphs* lcl_CreateLayout(const SwTextGlyphsKey& rKey,
SalLayoutGlyphs& rTextGlyphs)
-{
-// Use pre-calculated result.
-if (rTextGlyphs.IsValid())
-return
-
-if (rKey.m_nIndex >= rKey.m_aText.getLength())
-// Same as in OutputDevice::GetTextArray().
-return nullptr;
-
-// Calculate glyph items.
-std::unique_ptr pLayout
-= rKey.m_pOutputDevice->ImplLayout(rKey.m_aText, rKey.m_nIndex,
rKey.m_nLength, Point(0, 0), 0,
- nullptr,
SalLayoutFlags::GlyphItemsOnly);
-if (!pLayout)
-return nullptr;
-
-const SalLayoutGlyphs* pGlyphs = pLayout->GetGlyphs();
-if (!pGlyphs)
-return nullptr;
-
-// Remember the calculation result.
-rTextGlyphs = *pGlyphs;
-
-return
-}
}
bool operator<(const SwTextGlyphsKey& l, const SwTextGlyphsKey& r)
@@ -223,6 +215,72 @@ void SwFntObj::CreatePrtFont( const OutputDevice& rPrt )
[Libreoffice-bugs] [Bug 141088] New: Freeze rows and colums act like hide columns and rows with the frozen part
https://bugs.documentfoundation.org/show_bug.cgi?id=141088 Bug ID: 141088 Summary: Freeze rows and colums act like hide columns and rows with the frozen part Product: LibreOffice Version: 7.1.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: assamite4e...@gmail.com Home Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: hu-HU (en_GB); UI: en-GB Calc: CL Freeze rows and colums act like hide columns and rows if apply when the not all the columns and rows visible what i want too freeze. I don't know this is a valid behavior but unlogical. There isn't possibility to scroll back to make them visible . I experienced with columns but is the same with rows... Unhide columns or rows don't work because they really aren't hide. only solution the unfreeze and freeze again with the wanted screen position. The problem that as i see freeze work with selected row or column or cell if both but not position of the sheet. The problem appears at work computer x86 OS x86 libreoffice and home with x64 OS & Libreoffice. Screen Capture 2021-03-17 22-04-04.mkv 5,6 MB https://mega.nz/file/N1pygJyT#1FWPzYfS09f6eSQfmUOwEEReCYKMIx-ZTQUdWOIXboY -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88859] LO Writer math formulas disappear or shrink
https://bugs.documentfoundation.org/show_bug.cgi?id=88859 Vincent Bamps changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #15 from Vincent Bamps --- The problem still occurs with latest version: Version: 7.1.1.2 / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: fr-BE (en_US.UTF-8); UI: en-US Calc: CL The formula isn't editable anymore. The formula appaers squished to the new random size -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
