[Libreoffice-bugs] [Bug 144933] Table changes from automatic alignment to 'from left' with relative unchecked when dragging the border of a merged cell (see comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=144933 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Summary|Table changes from |Table changes from |automatic alignment to |automatic alignment to |'from left' with relative |'from left' with relative |unchecked when dragging the |unchecked when dragging the |border of a merged cell |border of a merged cell ||(see comment 7) OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 --- Comment #8 from Mahmoud Alnaanah --- I think I made it clear that this report is about the order not the position, I didn't even mention the position. Again, the problem is with the order of the name taps. It was from right to left in a rtl page, now it is from left to right in rtl sheet, and it is counterintuitive and annoying. Also, keeping changing stuff that are not a problem instead of focusing on solving the real problem in libreoffice is another problem. I think libreoffice developers should focus on compatibility issues and fixing bugs instead of missing with things that users are used to. Best regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157940] The exported PDF document has incorrect links
https://bugs.documentfoundation.org/show_bug.cgi?id=157940 BogdanB changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #4 from BogdanB --- I will close this as not our bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157946] Issue of macros
https://bugs.documentfoundation.org/show_bug.cgi?id=157946 --- 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] [Bug 157950] Impress : animation in text box
https://bugs.documentfoundation.org/show_bug.cgi?id=157950 --- 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] [Bug 157950] Impress : animation in text box
https://bugs.documentfoundation.org/show_bug.cgi?id=157950 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157946] Issue of macros
https://bugs.documentfoundation.org/show_bug.cgi?id=157946 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] [Bug 154488] Clicking "About LibreOffice" crashes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=154488 --- Comment #3 from QA Administrators --- Dear Joao Farias, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157940] The exported PDF document has incorrect links
https://bugs.documentfoundation.org/show_bug.cgi?id=157940 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157940] The exported PDF document has incorrect links
https://bugs.documentfoundation.org/show_bug.cgi?id=157940 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] [Bug 157695] Menus are all blank on multi-monitor setup in the second monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=157695 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157695] Menus are all blank on multi-monitor setup in the second monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=157695 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154488] Clicking "About LibreOffice" crashes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=154488 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152673] docx/xlsx/pptx format can't read and write chart's descr property
https://bugs.documentfoundation.org/show_bug.cgi?id=152673 --- Comment #8 from QA Administrators --- Dear coffish, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153946] FreezePanes unlocks by self.
https://bugs.documentfoundation.org/show_bug.cgi?id=153946 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152673] docx/xlsx/pptx format can't read and write chart's descr property
https://bugs.documentfoundation.org/show_bug.cgi?id=152673 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153946] FreezePanes unlocks by self.
https://bugs.documentfoundation.org/show_bug.cgi?id=153946 --- Comment #3 from QA Administrators --- Dear mariorl67, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148829] open new install and immediately quitting leads to hanging document recovery screen
https://bugs.documentfoundation.org/show_bug.cgi?id=148829 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148829] open new install and immediately quitting leads to hanging document recovery screen
https://bugs.documentfoundation.org/show_bug.cgi?id=148829 --- Comment #10 from QA Administrators --- Dear ksdavidc, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148989] writer crash in LO 7.3.3.2 when use scroll page in master documente with 170 pg
https://bugs.documentfoundation.org/show_bug.cgi?id=148989 --- Comment #10 from QA Administrators --- Dear luisjosegarcia, 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] [Bug 155109] App crashes when scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=155109 --- Comment #4 from QA Administrators --- Dear mj.harri...@proton.me, 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] [Bug 57202] FORMATTING: Make Header/footer font size independent from scaling of the sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=57202 --- Comment #9 from QA Administrators --- Dear Yuri, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145106] Paint shows artifacts for <0, 5 second) when zoom in/out on a table
https://bugs.documentfoundation.org/show_bug.cgi?id=145106 --- Comment #9 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48546] PRINTING: Frames text isn't aligned right
https://bugs.documentfoundation.org/show_bug.cgi?id=48546 --- Comment #15 from QA Administrators --- Dear Michael Velten, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132473] Calc loses header background bitmap image on .xlsx files after closing and reopening the file
https://bugs.documentfoundation.org/show_bug.cgi?id=132473 --- Comment #4 from QA Administrators --- Dear Gerald, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106539] Headers/footers cut off in this XLS/XLSX when exported to PDF/printed
https://bugs.documentfoundation.org/show_bug.cgi?id=106539 --- Comment #14 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118734] FILEOPEN: Only one bookmark displayed in navigator instead of 2
https://bugs.documentfoundation.org/show_bug.cgi?id=118734 --- Comment #9 from QA Administrators --- Dear Dave Lovelace, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107774] FILESAVE: RTF: style format attribute \pagebb (start a new page before this paragraph) not exported or incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=107774 --- Comment #5 from QA Administrators --- Dear Christian Nieber, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157561] Invalid error message opening .mdb/.accdb file
https://bugs.documentfoundation.org/show_bug.cgi?id=157561 --- Comment #9 from garth.hutchin...@ca.inter.net --- OK - updated JRE, checked all needed options in place and connected successfully to hymns-backup.accdb file but not to hymns.mdb file. Have one idea as to the cause. There are two flavours of .mdb files - have run into this before in other connections (my memory is a little hazy where MS Access 2007 fits in the discussion below. Flavour 1 (or, Flavor 1, if you prefer): a file that has been created and/or updated only by MS Access 97/2000/2003 and MAYBE 2007 - this can be opened again and again by those versions. Flavour 2: a file that has been created by any of the above and then a. updated by MS Access 2010/13/16; will no longer be able to be opened by MS Access 1997/2000/2003 and MAYBE 2007 The MAYBE comes in that MS Access 2007 is neutral in all this or whether it falls in same catecory as 2010 plus; but I think it is neutral because I vaguely remember using to created a downward compatible version of a .mdb file I can research this later but need to set up a couple of VM's with old versions of MS Access on them. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 157930] MENU: Easily insert commonly used conditional formatting rules
https://bugs.documentfoundation.org/show_bug.cgi?id=157930 --- Comment #7 from Commit Notification --- Paris Oplopoios committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f8f8d5ec4568a10dc77144369f52b2dd165e66c5 tdf#157930 Add button to switch to range view in condformateasydlg It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 157930] MENU: Easily insert commonly used conditional formatting rules
https://bugs.documentfoundation.org/show_bug.cgi?id=157930 --- Comment #7 from Commit Notification --- Paris Oplopoios committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f8f8d5ec4568a10dc77144369f52b2dd165e66c5 tdf#157930 Add button to switch to range view in condformateasydlg It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/source sc/uiconfig
sc/source/ui/condformat/condformateasydlg.cxx |2 + sc/source/ui/inc/condformateasydlg.hxx|1 sc/uiconfig/scalc/ui/conditionaleasydialog.ui | 29 +- 3 files changed, 31 insertions(+), 1 deletion(-) New commits: commit f8f8d5ec4568a10dc77144369f52b2dd165e66c5 Author: Paris Oplopoios AuthorDate: Fri Oct 27 13:12:19 2023 +0300 Commit: Paris Oplopoios CommitDate: Sun Oct 29 01:05:30 2023 +0200 tdf#157930 Add button to switch to range view in condformateasydlg Add a button that minimizes the dialog to make it easier to choose the conditional formatting range in the condformateasydlg. Also added more spacing. Change-Id: Ibf90e1d44caf2ab7a5c7bdb0bb2fa6c11d58 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158555 Tested-by: Jenkins Reviewed-by: Paris Oplopoios diff --git a/sc/source/ui/condformat/condformateasydlg.cxx b/sc/source/ui/condformat/condformateasydlg.cxx index c371861ac355..7e07b1a1dc19 100644 --- a/sc/source/ui/condformat/condformateasydlg.cxx +++ b/sc/source/ui/condformat/condformateasydlg.cxx @@ -67,11 +67,13 @@ ConditionalFormatEasyDialog::ConditionalFormatEasyDialog(SfxBindings* pBindings, , mxNumberEntry(m_xBuilder->weld_spin_button("entryNumber")) , mxNumberEntry2(m_xBuilder->weld_spin_button("entryNumber2")) , mxRangeEntry(new formula::RefEdit(m_xBuilder->weld_entry("entryRange"))) +, mxButtonRangeEdit(new formula::RefButton(m_xBuilder->weld_button("rbassign"))) , mxStyles(m_xBuilder->weld_combo_box("themeCombo")) , mxDescription(m_xBuilder->weld_label("description")) , mxButtonOk(m_xBuilder->weld_button("ok")) , mxButtonCancel(m_xBuilder->weld_button("cancel")) { +mxButtonRangeEdit->SetReferences(this, mxRangeEntry.get()); mpTabViewShell = GetTabViewShell(pBindings); if (!mpTabViewShell) mpTabViewShell = dynamic_cast(SfxViewShell::Current()); diff --git a/sc/source/ui/inc/condformateasydlg.hxx b/sc/source/ui/inc/condformateasydlg.hxx index 469613d2f1c8..9ca15a11bda9 100644 --- a/sc/source/ui/inc/condformateasydlg.hxx +++ b/sc/source/ui/inc/condformateasydlg.hxx @@ -45,6 +45,7 @@ private: std::unique_ptr mxNumberEntry; std::unique_ptr mxNumberEntry2; std::unique_ptr mxRangeEntry; +std::unique_ptr mxButtonRangeEdit; std::unique_ptr mxStyles; std::unique_ptr mxDescription; std::unique_ptr mxButtonOk; diff --git a/sc/uiconfig/scalc/ui/conditionaleasydialog.ui b/sc/uiconfig/scalc/ui/conditionaleasydialog.ui index 8f3da05b2ce8..2bee383956a9 100644 --- a/sc/uiconfig/scalc/ui/conditionaleasydialog.ui +++ b/sc/uiconfig/scalc/ui/conditionaleasydialog.ui @@ -68,7 +68,7 @@ True False vertical -12 +24 True @@ -79,6 +79,10 @@ True False +12 +12 +6 +6 12 @@ -191,6 +195,11 @@ True False +12 +12 +6 +6 +12 True @@ -205,6 +214,24 @@ 0 + + +True +True +True +center + + +Click the Shrink icon to reduce the dialog to the size of the input field. It is then easier to mark the required reference in the sheet. The icons then automatically convert to the Maximize icon. Click it to restore the dialog to its original size. + + + + +False +True +1 + +
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sc/qa
sc/qa/unit/subsequent_export_test.cxx | 31 +++ 1 file changed, 31 insertions(+) New commits: commit 17bc207d3054b4cbecb56b4d1195c73db203f21f Author: Paris Oplopoios AuthorDate: Thu Oct 26 14:28:06 2023 +0300 Commit: Paris Oplopoios CommitDate: Sun Oct 29 01:04:53 2023 +0200 sc: Test numeric conditional format text rule exports correctly Change-Id: Ib57ea44912b4cb0be7cbdb127dd7ea6f08ec8392 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158540 Tested-by: Jenkins CollaboraOffice Reviewed-by: Paris Oplopoios diff --git a/sc/qa/unit/subsequent_export_test.cxx b/sc/qa/unit/subsequent_export_test.cxx index cbbc99de69d8..d3927c136677 100644 --- a/sc/qa/unit/subsequent_export_test.cxx +++ b/sc/qa/unit/subsequent_export_test.cxx @@ -2402,6 +2402,37 @@ void ScExportTest::testSheetProtectionXLSB() CPPUNIT_ASSERT(!pTabProtect->isOptionEnabled(ScTableProtection::SELECT_LOCKED_CELLS)); } +CPPUNIT_TEST_FIXTURE(ScExportTest, testConditionalFormatNumberInTextRule) +{ +createScDoc(); + +ScDocument* pDocument = getScDoc(); +ScAddress aAddress(0, 0, 0); + +auto pFormat = std::make_unique(0, pDocument); +ScRange aCondFormatRange(aAddress); +ScRangeList aRangeList(aCondFormatRange); +pFormat->SetRange(aRangeList); +ScCondFormatEntry* pEntry += new ScCondFormatEntry(ScConditionMode::BeginsWith, "15", "", *pDocument, aAddress, ""); +pFormat->AddEntry(pEntry); +pDocument->AddCondFormat(std::move(pFormat), 0); + +saveAndReload("Calc Office Open XML"); +pDocument = getScDoc(); + +ScConditionalFormat* pCondFormat = pDocument->GetCondFormat(0, 0, 0); +CPPUNIT_ASSERT(pCondFormat); +CPPUNIT_ASSERT_EQUAL(size_t(1), pCondFormat->size()); +const ScFormatEntry* pCondFormatEntry = pCondFormat->GetEntry(0); +CPPUNIT_ASSERT(pCondFormatEntry); +CPPUNIT_ASSERT_EQUAL(ScFormatEntry::Type::Condition, pCondFormatEntry->GetType()); +const ScConditionEntry* pConditionEntry += static_cast(pCondFormatEntry); +CPPUNIT_ASSERT_EQUAL(ScConditionMode::BeginsWith, pConditionEntry->GetOperation()); +CPPUNIT_ASSERT_EQUAL(OUString("\"15\""), pConditionEntry->GetExpression(aAddress, 0)); +} + namespace { const char* toBorderName(SvxBorderLineStyle eStyle)
[Libreoffice-bugs] [Bug 128907] Support for Hancom Office File Format (HWP)
https://bugs.documentfoundation.org/show_bug.cgi?id=128907 --- Comment #16 from iyagi --- I installed the latest version 7.6.2.1. Still unable to read hwp format. https://www.hancom.com/etc/hwpDownload.do Is the information incorrect? Other websites offer conversions. Why can't I read it in Libro? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61438] FILESAVE: Cannot remove password from a document
https://bugs.documentfoundation.org/show_bug.cgi?id=61438 --- Comment #6 from frances.med...@orangeandbronze.com --- Hi Sebastiano, I was not able to replicate the issue anymore in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Mac OS X 13.5.2; UI render: Skia/Metal; VCL: osx Locale: en-PH (en_PH.UTF-8); UI: en-US Calc: threaded Also not replicated in Version 7.6.2.1 in Windows 10 Following the steps given to reproduce and issue seems to be okay now. Steps to reproduce: 1. Create a document, Save it with a password and then close the document. 2. Re-open the document with a password. 3. Save the document using ‘Save as’ and uncheck the password and save it with the same name (overwrite) 4. Close the document. 5. Re-open the document again. Expected behavior: Password will not be required. Actual behavior: Password was not required. Also tried not to close the document but save and overwrite it anyway, and it still looks okay. Password was still removed from the document. Also tried testing it using safe mode and still came up with the same results. Also tried to ‘Save as’ and uncheck the password and save it with a different filename and still works. I have also tried the file from the duplicate bug Bug 71992, and it also works fine now. @yallabalagan, What OS were you using? Is it still reproducible now? I have also tried the same steps as above in Calc and was not able to reproduce the bug. Im using: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Mac OS X 13.5.2; UI render: default; VCL: osx Locale: en-PH (en_PH.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157961] Sheet tab selection area UI direction flipped based on sheet direction
https://bugs.documentfoundation.org/show_bug.cgi?id=157961 ady changed: What|Removed |Added Severity|normal |enhancement --- Comment #1 from ady --- (In reply to Eyal Rozenberg from comment #0) > keep the sheet tabs area in the same > direction as the rest of the Calc UI. IOW (IIUC), the worksheet name tabs should be located on the UI to the left on LTR UI, while the tabs should be located to the right side of the UI on RTL UI, disregarding: * whether the worksheet is set RTL or LTR; * whether the name of the worksheet uses LTR or RTL text direction; * whether the content of the worksheet has LTR or RTL text direction in any cell. I would probably agree that the suggestion makes sense, but I am worried about older or advance users; since the current "jumping" behavior has been the behavior for such a long time, changing it now could be either desirable or unwanted, depending on users' workflow. Perhaps feedback from RTL users is very relevant before the behavior is changed, and if/when it is, it should be promptly and clearly advertised beforehand. I also recall that there are other bugs related to the worksheet (name) tabs in RTL UI, such as moving by keyboard shortcuts. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 --- Comment #7 from ady --- According to attachment 190476, this report is not about the text direction of the name of the worksheet, and it is also not about the order of the worksheet tabs (tdf#100585). IIUC, this report is about the general location of the worksheet (name) tab(s) within the UI, shown usually aligned to the left on a LTR UI (and aligned to the right of the UI on RTL UI). Each worksheet tab location is changed when its respective worksheet is set to be RTL, then aligned to the right of the UI. AFAICR, this has been the behavior since LO 3.3 on LTR UI, so it is still not clear the "Please change it back as it was" phrase on comment 4, because we don't know to which version the reporter is referring. I have not tested this on RTL UI (on older versions). We may need an additional screenshot showing the behavior "as it was before" (according to the reporter), so as to make the problem clear and repeatable. Whichever the case, probably the switch from left to right alignment of the worksheet (name) tab is not always desirable. Since it has been the behavior for such a long time, changing it now could be either desirable or unwanted, depending on users' workflow. So this has to be considered, for example in tdf#157961. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #10 from bianca.chior...@altom.com --- Created attachment 190484 --> https://bugs.documentfoundation.org/attachment.cgi?id=190484=edit Scenario7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #9 from bianca.chior...@altom.com --- Created attachment 190483 --> https://bugs.documentfoundation.org/attachment.cgi?id=190483=edit Scenario6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #8 from bianca.chior...@altom.com --- Created attachment 190482 --> https://bugs.documentfoundation.org/attachment.cgi?id=190482=edit Scenario4_2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #7 from bianca.chior...@altom.com --- Created attachment 190481 --> https://bugs.documentfoundation.org/attachment.cgi?id=190481=edit Scenario4_1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #6 from bianca.chior...@altom.com --- Created attachment 190480 --> https://bugs.documentfoundation.org/attachment.cgi?id=190480=edit Scenario4_ScreenRecording -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #5 from bianca.chior...@altom.com --- Created attachment 190479 --> https://bugs.documentfoundation.org/attachment.cgi?id=190479=edit Scenario3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #4 from bianca.chior...@altom.com --- Created attachment 190478 --> https://bugs.documentfoundation.org/attachment.cgi?id=190478=edit Scenario2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144933] Table changes from automatic alignment to 'from left' with relative unchecked when dragging the border of a merged cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144933 --- Comment #10 from Mihai --- Created attachment 190477 --> https://bugs.documentfoundation.org/attachment.cgi?id=190477=edit Video for the above comment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144933] Table changes from automatic alignment to 'from left' with relative unchecked when dragging the border of a merged cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144933 --- Comment #9 from Mihai --- Hello! I was able to reproduce the behavior from Comment 7 only on Windows (10): Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Steps that I Followed: 1. Open a new Libre office writer document 2. Make sure that the paper format is Letter (Right click->Page Style -> in the Page tab you can see the paper format) 3. Insert a table with more than 2 colums (the table’s position will be Automatic by default) 4. Drag(left/right) a cell border that is inside the table 5. Check the table’s alignment (Go to the table toolbar -> Table properties-> In the table tab, check the alignment option) Actual result: The alignment of the table is changed to Left. Please take a look at the video attached. Expected result: Considering that the width of the table has not been changed, I would expect its alignment to stick to default, automatic (as in the case of the linux build). Additional info: - The bug is reproducible if the style of the page is: A4, B5(ISO), B4(ISO) Legal, Letter, Long Bond, Tabloid - The bug is not reproducible if the style of the page is: A6, A5, A3, B6(ISO), B6 (JIS), B5 (JIS), B4 (JIS), 16 Kai, 32 Kai, Big 32 Kai - The behavior is not reproducible on Linux (Ubuntu 22.04 LST) - The bug is not reproducible for a nested table - The bug is not reproducible if changing the width of the inner column (step 4) is done by right-clicking -> click on Size-> Column Width option -> Change the column width -> Click on OK - Other versions where the bug is reproducible: 7.3.0.0 alpha1 (Windows10) 7.5.0.0 alpha1 (Windows10) 7.0.0.1 (Windows10) 7.1.5.2 (Windows10) Note: I was not able to reproduce the bug from the first comment with the following versions: 7.3.0.0 alpha1 (Windows10) 7.6.2.1 (Ubuntu 22.04 & Windows 10) 7.1.5.2 (Windows10) 7.0.0.1 (Windows10) I looked for version 7.3.0.0.alpha0+ but could not find it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157863] List bullet/numbering using adjacent character formatting (colour, bold, italic) depends on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=157863 --- Comment #3 from bianca.chior...@altom.com --- Hello, I did some more investigating on the reported bug that might help in fixing it. The testing was done on the following configuration: Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Mac OS X 14.0; UI render: default; VCL: osx Locale: en-US (en_RO.UTF-8); UI: en-US Calc: threaded Scenario 1 Steps: Test the same set of steps listed by the reporter on MacOS Result: The bug is reproducible on MacOS as well Scenario 2 Steps: 1.Add 3 paragraphs in an empty Writer document 2.Change the Font Name for all of them 3.In the 1st paragraph: Place cursor anywhere in paragraph (no selection), then toggle ordered list 4.In 2nd paragraph: select part of the paragraph, then toggle ordered list 5.In 3rd paragraph: select the whole paragraph, then toggle ordered list Result: The numbering only uses the character formatting of the adjacent text if there is an active text selection. (screenshot attached) Scenario 3 Steps: 1.Add 3 paragraphs in an empty Writer document 2.Apply Strikethrough from the toolbar to all of the paragraphs 3.In the 1st paragraph: Place cursor anywhere in paragraph (no selection), then toggle ordered list 4.In 2nd paragraph: select part of the paragraph, then toggle ordered list 5.In 3rd paragraph: select the whole paragraph, then toggle ordered list Result: The numbering/bullets only uses the character formatting of the adjacent text if there is an active text selection (screenshot attached) Scenario 4 Steps: 1.Add 1 paragraph in an Empty Writer document 2.Apply character formatting (e.g color the text in red) 3.Place cursor anywhere in paragraph (no selection), then toggle ordered list 4.Move to a new row by pressing Enter key 5.Observe the numbering have the correct formatting (the numbering in the second row is colored in red) (screenshot attached) 6.Start typing something on the second row 7.Observe the numbering is changing the formatting (the numbering color is changed to black) (screenshot attached) Result: Inconsistent behavior of the numbering/bullets character formatting when moving to a new row Side Note: If on Step 6 instead of typing, the user taps on the ‘Backspace’ key, the cursor moves back to the first row and the color of the numbering turns red (screen recording attached) Scenario 5 Steps: 1.Add 1 paragraph in an Empty Writer document 2.Apply more than 1 formatting options (example: bold + italic at the same time) 3.In the 1st paragraph: Place cursor anywhere in paragraph (no selection), then toggle ordered list 4.In 2nd paragraph: select part of the paragraph, then toggle ordered list 5.In 3rd paragraph: select the whole paragraph, then toggle ordered list Result: Same result as written by the reporter Scenario 6 Steps: 1.Add 1 paragraph in an Empty Writer document 2.Apply character formatting (e.g color the text in red) 3.Place cursor anywhere in paragraph (no selection), then toggle ordered list 4.CTRL+Z 5.Select the whole paragraph, then toggle ordered list again Result: The numbering/bullets it’s not using anymore the character formatting of the adjacent text even if there is an active text selection (screen recording attached) Scenario 7 Steps: 1.Add 1 multiple rows paragraph in an Empty Writer document 2.Apply character formatting (e.g color the text in red) 3.Place cursor anywhere in paragraph (no selection), then toggle ordered list Result: Same result as written by the reporter. The fact that the paragraph is multiple row doesn’t affect the result Scenario 8 Reproduced the reporter’s steps on Google Docs Result: The numbering/bullets it’s using the character formatting of the adjacent text for all of the 3 paragraphs Hope these are helpful and please let me know if anything needs clarifications -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157939] SVG import/boxes instead of text (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157939 Dave Gilbert changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om Component|filters and storage |graphics stack --- Comment #14 from Dave Gilbert --- OK, so since it's FontConfig stuff, it's not related to the actual import filter I'd originally filed it against, so lets swing this to 'graphics stack' (is that right for fonts?) and cc Caolán -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/graphic/BinaryDataContainer.cxx |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit d63bcfe3dde8cf873c897dbbe73fe8db38aaa70f Author: Noel Grandin AuthorDate: Sat Oct 28 19:59:33 2023 +0200 Commit: Noel Grandin CommitDate: Sat Oct 28 22:56:30 2023 +0200 use more TempFileFast in BinaryDataContainer::Impl Change-Id: Iea16260cd152e1c495e7713ada812265dbb5b702 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158598 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/vcl/source/graphic/BinaryDataContainer.cxx b/vcl/source/graphic/BinaryDataContainer.cxx index c9e75bc4ef77..89ae5eb8da1e 100644 --- a/vcl/source/graphic/BinaryDataContainer.cxx +++ b/vcl/source/graphic/BinaryDataContainer.cxx @@ -18,7 +18,7 @@ struct BinaryDataContainer::Impl { // temp file to store the data out of RAM if necessary -std::unique_ptr mpFile; +std::unique_ptr mpFile; // the binary data std::shared_ptr> mpData; @@ -59,7 +59,7 @@ struct BinaryDataContainer::Impl if (!mpData || mpData->empty()) return; -mpFile.reset(new utl::TempFileNamed()); +mpFile.reset(new utl::TempFileFast()); auto pStream = mpFile->GetStream(StreamMode::READWRITE); pStream->WriteBytes(mpData->data(), mpData->size());
[Libreoffice-commits] core.git: vcl/skia
vcl/skia/salbmp.cxx |7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) New commits: commit 7a1250b17cb671d3f57f13842ee3df8c49f8af19 Author: Patrick Luby AuthorDate: Sat Oct 28 15:03:12 2023 -0400 Commit: Patrick Luby CommitDate: Sat Oct 28 22:45:34 2023 +0200 Fix testDelayedScaleAlphaImage unit test Do not return the alpha mask if it is awaiting pending scaling. Pending scaling has not yet been done at this point since the scaling is done in the code following this block. Change-Id: I995d7f7eca4190f0a8b2094928bd92f718f1d5bc Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158599 Tested-by: Jenkins Reviewed-by: Patrick Luby diff --git a/vcl/skia/salbmp.cxx b/vcl/skia/salbmp.cxx index fe92a7a44110..13cf8aa5a4b9 100644 --- a/vcl/skia/salbmp.cxx +++ b/vcl/skia/salbmp.cxx @@ -963,7 +963,12 @@ const sk_sp& SkiaSalBitmap::GetAlphaSkImage(DirectImage direct) const // be temporary. SkiaSalBitmap* thisPtr = const_cast(this); thisPtr->mAlphaImage = alphaImage; -return mAlphaImage; +// Fix testDelayedScaleAlphaImage unit test +// Do not return the alpha mask if it is awaiting pending scaling. +// Pending scaling has not yet been done at this point since the +// scaling is done in the code following this block. +if (!scaling) +return mAlphaImage; } // Move the R channel value to the alpha channel. This seems to be the only // way to reinterpret data in SkImage as an alpha SkImage without accessing the pixels.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sc/source sc/uiconfig
sc/source/ui/condformat/condformateasydlg.cxx |2 + sc/source/ui/inc/condformateasydlg.hxx|1 sc/uiconfig/scalc/ui/conditionaleasydialog.ui | 29 +- 3 files changed, 31 insertions(+), 1 deletion(-) New commits: commit 1373bacdb99caec73b1a534e534c758c26982324 Author: Paris Oplopoios AuthorDate: Fri Oct 27 13:12:19 2023 +0300 Commit: Paris Oplopoios CommitDate: Sat Oct 28 22:36:19 2023 +0200 tdf#157930 Add button to switch to range view in condformateasydlg Add a button that minimizes the dialog to make it easier to choose the conditional formatting range in the condformateasydlg. Also added more spacing. Change-Id: Ibf90e1d44caf2ab7a5c7bdb0bb2fa6c11d58 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158532 Tested-by: Jenkins CollaboraOffice Reviewed-by: Paris Oplopoios diff --git a/sc/source/ui/condformat/condformateasydlg.cxx b/sc/source/ui/condformat/condformateasydlg.cxx index 8ddb297269dc..41b8a31eafd3 100644 --- a/sc/source/ui/condformat/condformateasydlg.cxx +++ b/sc/source/ui/condformat/condformateasydlg.cxx @@ -60,11 +60,13 @@ ConditionalFormatEasyDialog::ConditionalFormatEasyDialog(SfxBindings* pBindings, , mxNumberEntry(m_xBuilder->weld_spin_button("entryNumber")) , mxNumberEntry2(m_xBuilder->weld_spin_button("entryNumber2")) , mxRangeEntry(new formula::RefEdit(m_xBuilder->weld_entry("entryRange"))) +, mxButtonRangeEdit(new formula::RefButton(m_xBuilder->weld_button("rbassign"))) , mxStyles(m_xBuilder->weld_combo_box("themeCombo")) , mxDescription(m_xBuilder->weld_label("description")) , mxButtonOk(m_xBuilder->weld_button("ok")) , mxButtonCancel(m_xBuilder->weld_button("cancel")) { +mxButtonRangeEdit->SetReferences(this, mxRangeEntry.get()); mpTabViewShell = GetTabViewShell(pBindings); if (!mpTabViewShell) mpTabViewShell = dynamic_cast(SfxViewShell::Current()); diff --git a/sc/source/ui/inc/condformateasydlg.hxx b/sc/source/ui/inc/condformateasydlg.hxx index 001414396522..856e5fe9463f 100644 --- a/sc/source/ui/inc/condformateasydlg.hxx +++ b/sc/source/ui/inc/condformateasydlg.hxx @@ -43,6 +43,7 @@ private: std::unique_ptr mxNumberEntry; std::unique_ptr mxNumberEntry2; std::unique_ptr mxRangeEntry; +std::unique_ptr mxButtonRangeEdit; std::unique_ptr mxStyles; std::unique_ptr mxDescription; std::unique_ptr mxButtonOk; diff --git a/sc/uiconfig/scalc/ui/conditionaleasydialog.ui b/sc/uiconfig/scalc/ui/conditionaleasydialog.ui index 8f3da05b2ce8..2bee383956a9 100644 --- a/sc/uiconfig/scalc/ui/conditionaleasydialog.ui +++ b/sc/uiconfig/scalc/ui/conditionaleasydialog.ui @@ -68,7 +68,7 @@ True False vertical -12 +24 True @@ -79,6 +79,10 @@ True False +12 +12 +6 +6 12 @@ -191,6 +195,11 @@ True False +12 +12 +6 +6 +12 True @@ -205,6 +214,24 @@ 0 + + +True +True +True +center + + +Click the Shrink icon to reduce the dialog to the size of the input field. It is then easier to mark the required reference in the sheet. The icons then automatically convert to the Maximize icon. Click it to restore the dialog to its original size. + + + + +False +True +1 + +
[Libreoffice-bugs] [Bug 100585] Ordering of sheets with different direction changes when switching between them (RTL UI, not with GTK3)
https://bugs.documentfoundation.org/show_bug.cgi?id=100585 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7961 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7961 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157961] Sheet tab selection area UI direction flipped based on sheet direction
https://bugs.documentfoundation.org/show_bug.cgi?id=157961 Eyal Rozenberg changed: What|Removed |Added Blocks||129661 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7784, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||0585 Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129661 [Bug 129661] [META] Right-To-Left (RTL) user interface issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Eyal Rozenberg changed: What|Removed |Added Depends on||157961 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157961 [Bug 157961] Sheet tab selection area UI direction flipped based on sheet direction -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157961] New: Sheet tab selection area UI direction flipped based on sheet direction
https://bugs.documentfoundation.org/show_bug.cgi?id=157961 Bug ID: 157961 Summary: Sheet tab selection area UI direction flipped based on sheet direction Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com LibreOffice UI language (and direction) are set independently of the documents one works on in LO. Thus, if one has chosen an English UI for LO, then opens an Arabic ODT file in Writer, with RTL pages and Arabic text - the UI will remain in English, with the menu bar ordered LTR, the sidebar on the right side of the window, etc; nothing will be flipped to become RTL. This is true, in particular, for Calc... with one significant exception. The sheet tab area, below the sheet horizontal scrollbar, has the _UI_ direction set to RTL or LTR based on the current sheet direction. This is wrong and inconsistent. It also creates jarring effects when sheets in different directions are used in the same Calc document; and gives rise to complaints such as bug 100585 and bug 157784. Let us put an end to this silliness and keep the sheet tabs area in the same direction as the rest of the Calc UI. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sc/source
sc/source/filter/excel/xecontent.cxx | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) New commits: commit a63bd448c84c8b337b099d3b0c027f40516bc603 Author: Paris Oplopoios AuthorDate: Thu Oct 26 12:35:23 2023 +0300 Commit: Paris Oplopoios CommitDate: Sat Oct 28 22:26:11 2023 +0200 sc: Export conditional formatting expression correctly for text rules Text rules like BeginsWith would discard the expression if it was a number when exporting, which is not what is supposed to happen - as something like a conditional formatting rule BeginsWith "1" should be valid. Change-Id: I2d53754c462403f20b1991fa201184fcab3616a8 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158440 Tested-by: Jenkins CollaboraOffice Reviewed-by: Paris Oplopoios diff --git a/sc/source/filter/excel/xecontent.cxx b/sc/source/filter/excel/xecontent.cxx index 316fe673c359..71bf09cc84f5 100644 --- a/sc/source/filter/excel/xecontent.cxx +++ b/sc/source/filter/excel/xecontent.cxx @@ -1057,7 +1057,22 @@ void XclExpCFImpl::SaveXml( XclExpXmlStream& rStrm ) // the token array for that std::unique_ptr pTokenArray(mrFormatEntry.CreateFlatCopiedTokenArray(0)); if(pTokenArray->GetLen()) -aText = pTokenArray->FirstToken()->GetString().getString().toUtf8(); +{ +formula::StackVar eType = pTokenArray->FirstToken()->GetType(); +switch (eType) +{ +case formula::svDouble: +{ +aText = OString::number(pTokenArray->FirstToken()->GetDouble()); +break; +} +default: +{ +aText = pTokenArray->FirstToken()->GetString().getString().toUtf8(); +break; +} +} +} } sax_fastparser::FSHelperPtr& rWorksheet = rStrm.GetCurrentStream();
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 --- Comment #6 from Mahmoud Alnaanah --- Created attachment 190476 --> https://bugs.documentfoundation.org/attachment.cgi?id=190476=edit Screenshot that describe the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Bug 129661 depends on bug 157784, which changed state. Bug 157784 Summary: In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying. https://bugs.documentfoundation.org/show_bug.cgi?id=157784 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 ady changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- --- Comment #5 from ady --- (In reply to Mahmoud Alnaanah from comment #4) > First of all, I don't think anyone complained about switching the direction > of sheet names to rtl when a sheet is rtl. And logically, someone who change > the sheet to rtl will have rtl mindset, and prefer to see the names of the > sheets as rtl. > > Please change it back as it was. >From comment 4, I think the report is not clear, or it is not understood clearly enough. @Mahmoud Alnaanah, Are we talking about the location of the tabs (where the worksheet names are displayed)? Are we talking about the text direction within the worksheet name tab? Please open LibreOffice > Calc > menu Help > About, and click the icon to copy the version information; then paste that info in your next comment in the bug report page. It would also be helpful to know in which version the behavior changed for you, and other details of your system such as OS, DE... Perhaps you could add an attachment of a screenshot? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: download.lst external/libtiff
download.lst |4 external/libtiff/0001-WebP-decoder-validate-WebP-blob-width-height-band-co.patch | 79 -- external/libtiff/UnpackedTarball_libtiff.mk |1 3 files changed, 2 insertions(+), 82 deletions(-) New commits: commit 4273ebd28b9d3f50797f9e2dede0d9e8ce26e6f0 Author: Caolán McNamara AuthorDate: Sat Oct 28 17:16:27 2023 +0100 Commit: Caolán McNamara CommitDate: Sat Oct 28 21:57:28 2023 +0200 upgrade libtiff to 4.6.0 Change-Id: I839f78e5431caac378ce936aa5e34357144ae6b1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158593 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/download.lst b/download.lst index f1f1ed87e036..d83931988bdd 100644 --- a/download.lst +++ b/download.lst @@ -528,8 +528,8 @@ LIBPNG_TARBALL := libpng-1.6.40.tar.xz # three static lines # so that git cherry-pick # will not run into conflicts -LIBTIFF_SHA256SUM := 3c080867114c26edab3129644a63b708028a90514b7fe3126e38e11d24f9f88a -LIBTIFF_TARBALL := tiff-4.5.1.tar.xz +LIBTIFF_SHA256SUM := e178649607d1e22b51cf361dd20a3753f244f022eefab1f2f218fc62ebaf87d2 +LIBTIFF_TARBALL := tiff-4.6.0.tar.xz # three static lines # so that git cherry-pick # will not run into conflicts diff --git a/external/libtiff/0001-WebP-decoder-validate-WebP-blob-width-height-band-co.patch b/external/libtiff/0001-WebP-decoder-validate-WebP-blob-width-height-band-co.patch deleted file mode 100644 index 68353bd9ed20.. --- a/external/libtiff/0001-WebP-decoder-validate-WebP-blob-width-height-band-co.patch +++ /dev/null @@ -1,79 +0,0 @@ -From 350ff161c8a61b6483a1e4689e09cd47dd0dd5f9 Mon Sep 17 00:00:00 2001 -From: Even Rouault -Date: Sat, 17 Jun 2023 16:22:38 +0200 -Subject: [PATCH] WebP decoder: validate WebP blob width, height, band count - against TIFF parameters - -to avoid use of uninitialized variable, or decoding corrupted content -without explicit error - -Fixes #581, fixes #582 - libtiff/tif_webp.c | 51 ++ - 1 file changed, 51 insertions(+) - -diff --git a/libtiff/tif_webp.c b/libtiff/tif_webp.c -index 07db7cce..ce15391e 100644 a/libtiff/tif_webp.c -+++ b/libtiff/tif_webp.c -@@ -149,6 +149,57 @@ static int TWebPDecode(TIFF *tif, uint8_t *op, tmsize_t occ, uint16_t s) - segment_height = td->td_rowsperstrip; - } - -+int webp_width, webp_height; -+if (!WebPGetInfo(tif->tif_rawcp, -+ tif->tif_rawcc > UINT32_MAX ? UINT32_MAX -+ : (uint32_t)tif->tif_rawcc, -+ _width, _height)) -+{ -+TIFFErrorExtR(tif, module, "WebPGetInfo() failed"); -+return 0; -+} -+if ((uint32_t)webp_width != segment_width || -+(uint32_t)webp_height != segment_height) -+{ -+TIFFErrorExtR( -+tif, module, "WebP blob dimension is %dx%d. Expected %ux%u", -+webp_width, webp_height, segment_width, segment_height); -+return 0; -+} -+ -+#if WEBP_DECODER_ABI_VERSION >= 0x0002 -+WebPDecoderConfig config; -+if (!WebPInitDecoderConfig()) -+{ -+TIFFErrorExtR(tif, module, "WebPInitDecoderConfig() failed"); -+return 0; -+} -+ -+const bool bWebPGetFeaturesOK = -+WebPGetFeatures(tif->tif_rawcp, -+tif->tif_rawcc > UINT32_MAX -+? UINT32_MAX -+: (uint32_t)tif->tif_rawcc, -+) == VP8_STATUS_OK; -+ -+WebPFreeDecBuffer(); -+ -+if (!bWebPGetFeaturesOK) -+{ -+TIFFErrorExtR(tif, module, "WebPInitDecoderConfig() failed"); -+return 0; -+} -+ -+const int webp_bands = config.input.has_alpha ? 4 : 3; -+if (webp_bands != sp->nSamples) -+{ -+TIFFErrorExtR(tif, module, -+ "WebP blob band count is %d. Expected %d", webp_bands, -+ sp->nSamples); -+return 0; -+} -+#endif -+ - buffer_size = segment_width * segment_height * sp->nSamples; - if (occ == (tmsize_t)buffer_size) - { --- -2.41.0 - diff --git a/external/libtiff/UnpackedTarball_libtiff.mk b/external/libtiff/UnpackedTarball_libtiff.mk index 32ed699b7491..f7eeb6ace868 100644 --- a/external/libtiff/UnpackedTarball_libtiff.mk +++ b/external/libtiff/UnpackedTarball_libtiff.mk @@ -16,7 +16,6 @@ $(eval $(call gb_UnpackedTarball_set_patchlevel,libtiff,1)) $(eval $(call gb_UnpackedTarball_add_patches,libtiff,\ external/libtiff/libtiff.linknolibs.patch \ external/libtiff/0001-ofz-54685-Timeout.patch \ -
[Libreoffice-bugs] [Bug 157939] SVG import/boxes instead of text (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157939 --- Comment #13 from خالد حسني --- This is happening on Linux, so it is probably either a FontConfig issue or an issue on how we use FontConfig, so Caolán McNamara is probably the one most familure with this code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: starmath/inc starmath/source
starmath/inc/document.hxx|4 starmath/inc/view.hxx| 19 -- starmath/source/document.cxx | 314 ++ starmath/source/unomodel.cxx | 13 - starmath/source/view.cxx | 317 --- 5 files changed, 322 insertions(+), 345 deletions(-) New commits: commit e7aa16be823877f2273e75a4e8fe646c28b73731 Author: Mike Kaganski AuthorDate: Sat Oct 28 20:23:00 2023 +0300 Commit: Mike Kaganski CommitDate: Sat Oct 28 21:41:24 2023 +0200 Move Impl_Print from SmViewShell to SmDocShell All functionality is in the latter, anyway. This move allows to exclude dependency on existing views from SmModel::render. Change-Id: I3dff855b7f25089439c8afc57904a25a48fd127b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158594 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/starmath/inc/document.hxx b/starmath/inc/document.hxx index ca36a6138a32..e7c767d12df7 100644 --- a/starmath/inc/document.hxx +++ b/starmath/inc/document.hxx @@ -61,6 +61,7 @@ inline constexpr OUString MATHML_XML = u"MathML XML (Math)"_ustr; class SmDocShell; class EditEngine; class SmEditEngine; +class SmPrintUIOptions; class SmPrinterAccess { @@ -224,6 +225,9 @@ public: } void SetRightToLeft(bool bRTL); + +void Impl_Print(OutputDevice& rOutDev, const SmPrintUIOptions& rPrintUIOptions, +tools::Rectangle aOutRect); }; /* vim:set shiftwidth=4 softtabstop=4 expandtab: */ diff --git a/starmath/inc/view.hxx b/starmath/inc/view.hxx index a896cd41bf2d..8b17744d6171 100644 --- a/starmath/inc/view.hxx +++ b/starmath/inc/view.hxx @@ -37,6 +37,9 @@ class SmPrintUIOptions; class SmGraphicAccessible; class SmGraphicWidget; +#define MINZOOM sal_uInt16(25) +#define MAXZOOM sal_uInt16(800) + class SmGraphicWindow final : public InterimItemWindow { private: @@ -253,19 +256,6 @@ class SmViewShell final : public SfxViewShell DECL_LINK( DialogClosedHdl, sfx2::FileDialogHelper*, void ); virtual voidNotify( SfxBroadcaster& rBC, const SfxHint& rHint ) override; -static Size GetTextLineSize(OutputDevice const & rDevice, - const OUString& rLine); -static Size GetTextSize(OutputDevice const & rDevice, - std::u16string_view rText, - tools::Long MaxWidth); -static void DrawTextLine(OutputDevice& rDevice, - const Point& rPosition, - const OUString& rLine); -static void DrawText(OutputDevice& rDevice, - const Point& rPosition, - std::u16string_view rText, - sal_uInt16MaxWidth); - virtual SfxPrinter *GetPrinter(bool bCreate = false) override; virtual sal_uInt16 SetPrinter(SfxPrinter *pNewPrinter, SfxPrinterChangeFlags nDiffFlags = SFX_PRINTER_ALL) override; @@ -331,9 +321,6 @@ public: void Execute( SfxRequest& rReq ); void GetState(SfxItemSet &); -void Impl_Print( OutputDevice , const SmPrintUIOptions , -tools::Rectangle aOutRect ); - static bool IsInlineEditEnabled(); // Opens the main help page for the Math module diff --git a/starmath/source/document.cxx b/starmath/source/document.cxx index 18cdc237944f..91bdcc601ec4 100644 --- a/starmath/source/document.cxx +++ b/starmath/source/document.cxx @@ -24,6 +24,7 @@ #include #include +#include #include #include #include @@ -1270,4 +1271,317 @@ void SmDocShell::SetRightToLeft(bool bRTL) Repaint(); } +static Size GetTextLineSize(OutputDevice const& rDevice, const OUString& rLine) +{ +Size aSize(rDevice.GetTextWidth(rLine), rDevice.GetTextHeight()); +const tools::Long nTabPos = rLine.isEmpty() ? 0 : rDevice.approximate_digit_width() * 8; + +if (nTabPos) +{ +aSize.setWidth(0); +sal_Int32 nPos = 0; +do +{ +if (nPos > 0) +aSize.setWidth(((aSize.Width() / nTabPos) + 1) * nTabPos); + +const OUString aText = rLine.getToken(0, '\t', nPos); +aSize.AdjustWidth(rDevice.GetTextWidth(aText)); +} while (nPos >= 0); +} + +return aSize; +} + +static Size GetTextSize(OutputDevice const& rDevice, std::u16string_view rText, +tools::Long MaxWidth) +{ +Size aSize; +Size aTextSize; +if (rText.empty()) +return aTextSize; + +sal_Int32 nPos = 0; +do +{ +OUString aLine(o3tl::getToken(rText, 0, '\n', nPos)); +aLine = aLine.replaceAll("\r", ""); + +aSize = GetTextLineSize(rDevice, aLine); + +if (aSize.Width() > MaxWidth) +{ +do +{ +OUString aText; +sal_Int32 m = aLine.getLength(); +sal_Int32 nLen = m; + +for (sal_Int32 n = 0; n < nLen; n++) +
[Libreoffice-commits] core.git: starmath/source
starmath/source/unomodel.cxx | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) New commits: commit 8dda6270f8b9af6fcfba2a3a935612ab5a81c247 Author: Mike Kaganski AuthorDate: Sat Oct 28 18:06:34 2023 +0300 Commit: Mike Kaganski CommitDate: Sat Oct 28 21:40:43 2023 +0200 pPrinter may be nullptr E.g., calling storeToURL, generating a PDF, on an embedded formula. Change-Id: If74af90f9c3dfd54a328782ddecd0adf52b51a5a Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158591 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/starmath/source/unomodel.cxx b/starmath/source/unomodel.cxx index 96e41599ddad..114fb29e43d7 100644 --- a/starmath/source/unomodel.cxx +++ b/starmath/source/unomodel.cxx @@ -958,8 +958,9 @@ uno::Sequence< beans::PropertyValue > SAL_CALL SmModel::getRenderer( throw RuntimeException(); SmPrinterAccess aPrinterAccess( *pDocSh ); -Printer *pPrinter = aPrinterAccess.GetPrinter(); -SizeaPrtPaperSize ( pPrinter->GetPaperSize() ); +Size aPrtPaperSize; +if (Printer *pPrinter = aPrinterAccess.GetPrinter()) +aPrtPaperSize = pPrinter->GetPaperSize(); // if paper size is 0 (usually if no 'real' printer is found), // guess the paper size @@ -1029,11 +1030,16 @@ void SAL_CALL SmModel::render( return; SmPrinterAccess aPrinterAccess( *pDocSh ); -Printer *pPrinter = aPrinterAccess.GetPrinter(); -SizeaPrtPaperSize ( pPrinter->GetPaperSize() ); -SizeaOutputSize ( pPrinter->GetOutputSize() ); -Point aPrtPageOffset( pPrinter->GetPageOffset() ); +Size aPrtPaperSize; +Size aOutputSize; +Point aPrtPageOffset; +if (Printer *pPrinter = aPrinterAccess.GetPrinter()) +{ +aPrtPaperSize = pPrinter->GetPaperSize(); +aOutputSize = pPrinter->GetOutputSize(); +aPrtPageOffset = pPrinter->GetPageOffset(); +} // no real printer ?? if (aPrtPaperSize.IsEmpty())
[Libreoffice-bugs] [Bug 147892] Corrupt DOCX document after saving (track changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=147892 --- Comment #29 from Roman --- stdContent line 2 and ins(del) stdContent line 2 and p hyperlink -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/sdi sc/source
sc/sdi/scalc.sdi |4 - sc/source/ui/view/cellsh1.cxx | 155 ++ 2 files changed, 143 insertions(+), 16 deletions(-) New commits: commit 50abd90d739410ed34de5e7cd9c4308dc75f9ab6 Author: Szymon Kłos AuthorDate: Wed Oct 25 18:23:06 2023 +0200 Commit: Szymon Kłos CommitDate: Sat Oct 28 21:31:16 2023 +0200 Introduce easy to apply cond format styles UNO commands for Data bars and Color scale conditional formatting now can be called with parameter to apply few predefined themes. In the future it could be moved somewhere so it could be configured from the UI maybe... Change-Id: I080709709fcc0886dcaf6050a6c1ae621b6728c9 (cherry picked from commit c8d4a99082269c7008df5765232a93d19e7a3d84) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158539 Tested-by: Jenkins Reviewed-by: Szymon Kłos diff --git a/sc/sdi/scalc.sdi b/sc/sdi/scalc.sdi index 4da6e21b162e..614293cc90bb 100644 --- a/sc/sdi/scalc.sdi +++ b/sc/sdi/scalc.sdi @@ -787,7 +787,7 @@ SfxVoidItem CurrentConditionalFormatDialog SID_OPENDLG_CURRENTCONDFRMT SfxVoidItem ColorScaleFormatDialog SID_OPENDLG_COLORSCALE -() +(SfxInt16Item IconSet FN_PARAM_1) [ AutoUpdate = FALSE, FastCall = FALSE, @@ -805,7 +805,7 @@ SfxVoidItem ColorScaleFormatDialog SID_OPENDLG_COLORSCALE SfxVoidItem DataBarFormatDialog SID_OPENDLG_DATABAR -() +(SfxInt16Item IconSet FN_PARAM_1) [ AutoUpdate = FALSE, FastCall = FALSE, diff --git a/sc/source/ui/view/cellsh1.cxx b/sc/source/ui/view/cellsh1.cxx index b35796ff0c2e..1b307963dc01 100644 --- a/sc/source/ui/view/cellsh1.cxx +++ b/sc/source/ui/view/cellsh1.cxx @@ -2186,27 +2186,154 @@ void ScCellShell::ExecuteEdit( SfxRequest& rReq ) // do we have a parameter with the conditional formatting type? const SfxInt16Item* pParam = rReq.GetArg(FN_PARAM_1); -if (pParam && nSlot == SID_OPENDLG_ICONSET) +if (pParam) { auto pFormat = std::make_unique(0, ); pFormat->SetRange(aRangeList); -ScIconSetType eIconSetType = limit_cast(pParam->GetValue(), IconSet_3Arrows, IconSet_5Boxes); -const int nSteps = ScIconSetFormat::getIconSetElements(eIconSetType); +if (nSlot == SID_OPENDLG_ICONSET) +{ +ScIconSetType eIconSetType = limit_cast(pParam->GetValue(), IconSet_3Arrows, IconSet_5Boxes); +const int nSteps = ScIconSetFormat::getIconSetElements(eIconSetType); + +ScIconSetFormat* pEntry = new ScIconSetFormat(); +ScIconSetFormatData* pIconSetFormatData = new ScIconSetFormatData(eIconSetType); + +pIconSetFormatData->m_Entries.emplace_back(new ScColorScaleEntry(0, COL_RED, COLORSCALE_PERCENT)); +pIconSetFormatData->m_Entries.emplace_back(new ScColorScaleEntry(round(100. / nSteps), COL_BROWN, COLORSCALE_PERCENT)); +pIconSetFormatData->m_Entries.emplace_back(new ScColorScaleEntry(round(200. / nSteps), COL_YELLOW, COLORSCALE_PERCENT)); +if (nSteps > 3) +pIconSetFormatData->m_Entries.emplace_back(new ScColorScaleEntry(round(300. / nSteps), COL_WHITE, COLORSCALE_PERCENT)); +if (nSteps > 4) +pIconSetFormatData->m_Entries.emplace_back(new ScColorScaleEntry(round(400. / nSteps), COL_GREEN, COLORSCALE_PERCENT)); + +pEntry->SetIconSetData(pIconSetFormatData); +pFormat->AddEntry(pEntry); +} +else if (nSlot == SID_OPENDLG_COLORSCALE) +{ +typedef std::tuple ScaleEntry; +static std::vector> aScaleThemes = +{ +{ +{ 0, Color(0xF8696B), COLORSCALE_MIN }, +{ 0, Color(0x63BE7B), COLORSCALE_MAX }, +{ 50, Color(0xFFEB84), COLORSCALE_PERCENTILE } +}, +{ +{ 0, Color(0x63BE7B), COLORSCALE_MIN }, +{ 0, Color(0xF8696B), COLORSCALE_MAX }, +{ 50, Color(0xFFEB84), COLORSCALE_PERCENTILE } +}, +{ +{ 0, Color(0xF8696B), COLORSCALE_MIN }, +{ 0, Color(0x63BE7B), COLORSCALE_MAX }, +{ 50, Color(0xFCFCFF), COLORSCALE_PERCENTILE } +}, +
[Libreoffice-bugs] [Bug 147450] Mouse cursor jumps when going over drawing points (kf5 on Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=147450 Michael Weghorn changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #10 from Michael Weghorn --- Is this still an issue? I cannot reproduce with the current development version (git master) of LibreOffice on Debian testing, s. screencast attachment 190474 taken with sample doc attachment 190475. Are the steps shown in the screencast the right steps to reproduce? If not, can you please attach a sample doc and more detailed instructions? Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b7d2a9c824aca1a4dfd1b857a3620e73ade6bc0d CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: qt6 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b7d2a9c824aca1a4dfd1b857a3620e73ade6bc0d CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147450] Mouse cursor jumps when going over drawing points (kf5 on Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=147450 --- Comment #9 from Michael Weghorn --- Created attachment 190475 --> https://bugs.documentfoundation.org/attachment.cgi?id=190475=edit Sample file used for screencast on Debian testing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147450] Mouse cursor jumps when going over drawing points (kf5 on Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=147450 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #8 from Michael Weghorn --- Created attachment 190474 --> https://bugs.documentfoundation.org/attachment.cgi?id=190474=edit Screencast not being able to reproduce on Debian testing with mast as of 2023-10-28 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157784] In libreoffice calc, the names of the sheets are displayed in opposite direction now, which is annoying.
https://bugs.documentfoundation.org/show_bug.cgi?id=157784 --- Comment #4 from Mahmoud Alnaanah --- First of all, I don't think anyone complained about switching the direction of sheet names to rtl when a sheet is rtl. And logically, someone who change the sheet to rtl will have rtl mindset, and prefer to see the names of the sheets as rtl. Please change it back as it was. regards, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157946] Issue of macros
https://bugs.documentfoundation.org/show_bug.cgi?id=157946 --- Comment #7 from hugoferna...@gmail.com --- I get the following (I am translating the error messages from Portuguese): - Error in executing BASIC on line '73' Not implemented - Error in executing BASIC '1' An exception happened. Type: con.sun.star.uno.RuntimeException Message: The procedure doesn't exist -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157911] Wrong borders for tables splitted in multiple pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157911 --- Comment #5 from Philipp --- Created attachment 190473 --> https://bugs.documentfoundation.org/attachment.cgi?id=190473=edit Table over 2 pages with the bug showing -> Follow up from Base File -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157911] Wrong borders for tables splitted in multiple pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157911 --- Comment #4 from Philipp --- Created attachment 190472 --> https://bugs.documentfoundation.org/attachment.cgi?id=190472=edit Settings Table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157911] Wrong borders for tables splitted in multiple pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157911 --- Comment #3 from Philipp --- Created attachment 190471 --> https://bugs.documentfoundation.org/attachment.cgi?id=190471=edit Table over 3 pages -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157911] Wrong borders for tables splitted in multiple pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157911 --- Comment #2 from Philipp --- Created attachment 190470 --> https://bugs.documentfoundation.org/attachment.cgi?id=190470=edit Base File -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157911] Wrong borders for tables splitted in multiple pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157911 --- Comment #1 from Philipp --- In my understanding the bug reported is, that the “outer border” formatting effects the borderlines within the table, when the table crosses over 2 pages. That is, what I tried to replicate. I replicated the bug with: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Steps to replicate: 1. Open empty document 2. Create a table via Table > Insert Table 3. In the wizard klick “Insert” →Now you have a 2x2 Table with two rows width 4. Enlarge the table over a pagebreak (I placed cursor inside and pressed enter repeatedly (see attachment 157911_0_Table_no_formatting.odt) 6.Right klick on the table → Table properties → Borders 7. A) Give a border to the left and the bottom line (see attached screenshot for an example), when your table breaks with the second row over the page B) Give a border to the left and the top line, when your table breaks with the first row over the page 8. Hit enter Expected result: The left and the bottom line are formatted according to the settings Actual result: The two lines + the middle line are formatted, see example file 2 It seems as it works as a page setting, instead of a table setting. And either colours the bottom of one page or the top of the next. If the cells are expanded to further pages, the behaviour stays coherent. In another test I used “Simple List shaded” - See file 157911_3_Table_3pages.odt: Here the table spans 3 pages and only on the third page are bottom and top horizontal line coloured. If you colour the top line, the top and bottom of the first page will be coloured. As my replication is not 100% accurate if I compare it with the OP's screenshot, where only a cell after the pagebreak looks wrongly formatted, I'd like to ask Nicola to provide the sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/filter/xml/xmlimp.cxx |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) New commits: commit 7269df74824bdea31b9d42d1e2d77b77e702b3ab Author: Caolán McNamara AuthorDate: Sat Oct 28 17:11:00 2023 +0100 Commit: Caolán McNamara CommitDate: Sat Oct 28 19:51:00 2023 +0200 ofz#63646 avoid Timeout when document fails to load Change-Id: I84db71486c42b74bd2bf7ff2c5469938802ee113 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158592 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/sw/source/filter/xml/xmlimp.cxx b/sw/source/filter/xml/xmlimp.cxx index c84a3a3a3392..55415f12a6f4 100644 --- a/sw/source/filter/xml/xmlimp.cxx +++ b/sw/source/filter/xml/xmlimp.cxx @@ -1847,12 +1847,11 @@ extern "C" SAL_DLLPUBLIC_EXPORT bool TestPDFExportFODT(SvStream ) uno::Reference xFODTFilter(xInterface, uno::UNO_QUERY_THROW); bool ret = xFODTFilter->filter(aArgs); -css::uno::Reference xController(xModel->createDefaultViewController(xTargetFrame), UNO_SET_THROW); - -utl::ConnectFrameControllerModel(xTargetFrame, xController, xModel); - if (ret) { +css::uno::Reference xController(xModel->createDefaultViewController(xTargetFrame), UNO_SET_THROW); +utl::ConnectFrameControllerModel(xTargetFrame, xController, xModel); + utl::TempFileNamed aTempFile; aTempFile.EnableKillingFile();
[Libreoffice-bugs] [Bug 152571] Very slow save (macOS, ARM)
https://bugs.documentfoundation.org/show_bug.cgi?id=152571 --- Comment #18 from Michael Meeks --- Why do we bother with the checksumming ? =) Surely when we save we just dump the PNG data we have from disk to zip file - but if we save time here fine; I'm just curious as to why we bother CRC'ing. Is it possible we had that at load (can we get it from the zip?), but then we swapped and (somehow) then bogusly forced a re-calculate of the CRC on swapping back in or ? =) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157695] Menus are all blank on multi-monitor setup in the second monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=157695 --- Comment #3 from Richard Blazek --- Version information below (Not relevant because LibreOffice has been exhibiting this bug for some years): Version: 7.6.2.1 (x86) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded --- I am using the PortableApps portable version of LO at the moment. In the past, I downloaded and installed the normal version and got the same behaviour. To reproduce the bug: I opened LO on Display-1 by double-clicking on a file in WindowsExplorer in Display-1. I clicked File/New/Document (NB: menus were visible on this document). I clicked the menu, File, on the New Document. The new document is shown in the attached screenshot with the blank menu. I closed the new document. The menus in the first document were now blank. I moved the first document to Display-2. The menus reappeared. I didn't know there was a tabbed UI - thanks! Display-1, 100% magnification, normal monitor. Display-2, 125% magnification, Wacom One tablet. I hope this helps! I was able to reproduce this bug on my system recently for the first time by following a thread regarding a different bug on a two-monitor setup on the software Krita (what I use the Wacom One tablet for). Putting the two displays at the same magnification eliminates the bug (I think). Kind regards, Richard. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157960] New: The handles of connectors in a group are reset to default, when the group is resized
https://bugs.documentfoundation.org/show_bug.cgi?id=157960 Bug ID: 157960 Summary: The handles of connectors in a group are reset to default, when the group is resized Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 190469 --> https://bugs.documentfoundation.org/attachment.cgi?id=190469=edit connectors in group with non-default handles Open the attached document. Click on the drawing and resize the group. Notice, that the routing of the connectors changes because the handles are reset to default positions. This is like caused by https://opengrok.libreoffice.org/xref/core/svx/source/svdraw/svdoedge.cxx?r=93c5885d#2317 The behavior for resizing needs to be reconsidered. It is not enough to adapt the handle position proportionally to the resizing. The padding around the connected objects (UI Connector -> Line spacing) would need to be adapted too. I see the problem in Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99649] [META] Improve Connector handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99649 Regina Henschel changed: What|Removed |Added Depends on||144309 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144309 [Bug 144309] GALLERY: Flow chart elements are not connected properly after save/load or zoom in/out -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144309] GALLERY: Flow chart elements are not connected properly after save/load or zoom in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=144309 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de Blocks||99649 --- Comment #11 from Regina Henschel --- It might be the same problem as in bug 56949. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99649 [Bug 99649] [META] Improve Connector handling -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sd/qa
sd/qa/unit/PNGExportTests.cxx |5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) New commits: commit 2a302e143d4c6b1fc26aee6fdb53e876166d0340 Author: Xisco Fauli AuthorDate: Sat Oct 28 09:33:22 2023 +0200 Commit: Xisco Fauli CommitDate: Sat Oct 28 18:51:18 2023 +0200 CppunitTest_sd_png_export_tests: relax test a bit See https://gerrit.libreoffice.org/c/core/+/158341 Change-Id: I8a5b326063bef0cbd2d2c71a0f0650c8298c6514 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158583 Tested-by: Jenkins Reviewed-by: Xisco Fauli diff --git a/sd/qa/unit/PNGExportTests.cxx b/sd/qa/unit/PNGExportTests.cxx index 513d7a1e8cf9..da435ae971f1 100644 --- a/sd/qa/unit/PNGExportTests.cxx +++ b/sd/qa/unit/PNGExportTests.cxx @@ -1,4 +1,3 @@ - /* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /* * This file is part of the LibreOffice project. @@ -496,9 +495,9 @@ CPPUNIT_TEST_FIXTURE(SdPNGExportTest, testTdf157793) } // Without the fix in place, this test would have failed with -// - Expected greater than: 8500 +// - Expected greater than: 7800 // - Actual : 0 -CPPUNIT_ASSERT_GREATER(8500, nLightGrayCount); +CPPUNIT_ASSERT_GREATER(7800, nLightGrayCount); } CPPUNIT_TEST_FIXTURE(SdPNGExportTest, testTdf157635)
[Libreoffice-bugs] [Bug 143029] [PPT] FILEOPEN incorrect 'connectors'
https://bugs.documentfoundation.org/show_bug.cgi?id=143029 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #6 from Regina Henschel --- The shapes have a 180deg rotation in LibreOffice but not in PowerPoint 365. Why? The import is still wrong with Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157695] Menus are all blank on multi-monitor setup in the second monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=157695 --- Comment #2 from Richard Blazek --- Created attachment 190468 --> https://bugs.documentfoundation.org/attachment.cgi?id=190468=edit LibreOffice showing blank menus -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130937] Mouse-hold preview differs from result when changing a connector via dragging
https://bugs.documentfoundation.org/show_bug.cgi?id=130937 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6531 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99649] [META] Improve Connector handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99649 Regina Henschel changed: What|Removed |Added Depends on||126531 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126531 [Bug 126531] Connector Behavior Broken since 6.2.x -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126531] Connector Behavior Broken since 6.2.x
https://bugs.documentfoundation.org/show_bug.cgi?id=126531 Regina Henschel changed: What|Removed |Added Blocks||99649 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||0937 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99649 [Bug 99649] [META] Improve Connector handling -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120539] Position of adjusted middle line on connectors is randomly changed when copying the drawing to a writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=120539 --- Comment #12 from Regina Henschel --- It is an error with using the leaving direction of the diagonal gluepoint of the ellipse. The error still exists in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b0e7f76820d467dd0d98962b01f84cb38a3a985 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101325] FORMATTING: Connector type is not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=101325 Regina Henschel changed: What|Removed |Added URL||https://docs.oasis-open.org ||/office/OpenDocument/v1.3/o ||s/part3-schema/OpenDocument ||-v1.3-os-part3-schema.html# ||element-draw_connector --- Comment #6 from Regina Henschel --- With current ODF 1.3 we have this: The type of a connector is not a style but an attribute of the individual connector shape. Thus it is not possible to store it in a style. Implementing a style attribute for the connector type will require an addition to the ODF standard. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157721] SimpleCommandMail: subject and body truncated at the comma (Ubuntu + Thunderbird)
https://bugs.documentfoundation.org/show_bug.cgi?id=157721 --- Comment #10 from TISSENDIER Pierre --- (In reply to Stéphane Guillou (stragu) from comment #4) > (In reply to TISSENDIER Pierre from comment #3) > > Thé problem is not in attachement ! > > Thé problem is in SUBJECT and MESSAGE TEXT! > I did see that, but my understanding is that the root issue is the same. > > See also: https://bugzilla.mozilla.org/show_bug.cgi?id=258887 > So, regardless of if the two issues should be kept separate or not, the root > cause is in Thunderbird's handling of commas in the command line. No WHY it is GOOD with SimpleSystemMail on Windows10 ? For : https://bugzilla.mozilla.org/show_bug.cgi?id=900117 and : https://bugzilla.mozilla.org/show_bug.cgi?id=258887 If you respect http://kb.mozillazine.org/Command_line_arguments_-_Thunderbird Every arguments must be framed by simple quote ! no double quote (258887-900117) Arguments "to","cc","bcc","attachment" accept arrays (with comma separator) i mean is normal for attachment that a comma in file name failed. Arguments "subject" and "bodytext" shouldn't be arrays ! In any case, it must be informed (in help, in API SDK ) that SimpleCommandMail is INCOMPATIBLE with Thunderbird ;( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56949] FILEOPEN: Connectors lose their connections with the shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=56949 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #12 from Regina Henschel --- It is still a problem in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b0e7f76820d467dd0d98962b01f84cb38a3a985 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54355] VIEWING: Connector copied from Draw horizontally shifted and disconnected after zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=54355 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #17 from Regina Henschel --- Still reproducible in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b0e7f76820d467dd0d98962b01f84cb38a3a985 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sfx2/source
sfx2/source/doc/sfxbasemodel.cxx | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) New commits: commit dd278812a456148e6d4326f6013b738b48140bb0 Author: Mike Kaganski AuthorDate: Sat Oct 28 18:04:42 2023 +0300 Commit: Mike Kaganski CommitDate: Sat Oct 28 18:09:43 2023 +0200 Simplify a bit Change-Id: I50b7ec4a38a9489f2712bbe99fd3377c78f579b1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158590 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/sfx2/source/doc/sfxbasemodel.cxx b/sfx2/source/doc/sfxbasemodel.cxx index 03a511fc2fe4..52436ef8d4d6 100644 --- a/sfx2/source/doc/sfxbasemodel.cxx +++ b/sfx2/source/doc/sfxbasemodel.cxx @@ -3060,9 +3060,11 @@ void SfxBaseModel::impl_store( const OUString& sURL if( sURL.isEmpty() ) throw frame::IllegalArgumentIOException(); -bool bSaved = false; +if (!m_pData->m_pObjectShell) +return; + ::comphelper::SequenceAsHashMap aArgHash(seqArguments); -if ( !bSaveTo && m_pData->m_pObjectShell.is() && !sURL.isEmpty() +if ( !bSaveTo && !sURL.isEmpty() && !sURL.startsWith( "private:stream" ) && ::utl::UCBContentHelper::EqualURLs( getLocation(), sURL ) ) { @@ -3095,7 +3097,7 @@ void SfxBaseModel::impl_store( const OUString& sURL try { storeSelf( aArgHash.getAsConstPropertyValueList() ); -bSaved = true; +return; } catch( const lang::IllegalArgumentException& ) { @@ -3131,9 +3133,6 @@ void SfxBaseModel::impl_store( const OUString& sURL } } -if ( bSaved || !m_pData->m_pObjectShell.is() ) -return; - SfxGetpApp()->NotifyEvent( SfxEventHint( bSaveTo ? SfxEventHintId::SaveToDoc : SfxEventHintId::SaveAsDoc, GlobalEventConfig::GetEventName( bSaveTo ? GlobalEventId::SAVETODOC : GlobalEventId::SAVEASDOC ), m_pData->m_pObjectShell.get() ) );
[Libreoffice-bugs] [Bug 157959] Can't export some images from an .odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=157959 --- Comment #1 from Tomislav Nakic-Alfirevic --- Created attachment 190467 --> https://bugs.documentfoundation.org/attachment.cgi?id=190467=edit .odt containing 2 images, only one of them being exportable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157653] (Not Responding) Message appears constantly when using Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=157653 --- Comment #3 from m.a.riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157959] New: Can't export some images from an .odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=157959 Bug ID: 157959 Summary: Can't export some images from an .odt document Product: LibreOffice Version: 6.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: na...@gmx.com Description: Observed: Created an .odt document with images. Right-click on upper image, the context menu includes the "Save" option. Right-click the lower image, there is no "Save" option. Expected: The "Save" option is available for all images. Workarounds: Rename .odt to .zip, open .zip using any tool, navigate to the appropriate subdir containing images, copy any image you need. Does not work very well when an .odt contains hundreds or thousands of images, but is usable for up to tens of images. Note: I'm not sure why there's a "JPG Options" dialogue when saving a JPG file from an .odt to disk as a separate image. I'd expect the image to be saved in the original format the image was in when it was added to the document. Steps to Reproduce: See description. Actual Results: See description. Expected Results: See description. Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153953] Switching direction of a list paragraph changes numbering alignment of other paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=153953 --- Comment #7 from Eyal Rozenberg --- (In reply to judd from comment #6) First, I must commend the thoroughness... but do remember that one can perhaps be a little too thorough, with very long comments making it easier to miss important observations. Anyway, regarding your point (6.): Of course you couldn't find mention of this in the Write Guide, since this is not intended behavior, it's just a bug :-P -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157939] SVG import/boxes instead of text (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157939 --- Comment #12 from Dave Gilbert --- (In reply to خالد حسني from comment #11) > That would explain why the font updates trigger this, since the previous > Noto Naskh Arabic version we were bundling didn’t have any Latin glyphs, > like the system version on the broken systems. I bet this bug rehappens every few years as fonts change. Who is the person who knows about the font paths and caching stuff? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157653] (Not Responding) Message appears constantly when using Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=157653 --- Comment #2 from Deanna --- I removed and added Libre Office per recommendation but am still receiving Not Responding notification when open document, whether by clicking on document from USB drive, c drive, or through Open function directly in program. -- You are receiving this mail because: You are the assignee for the bug.