[Bug 113412] RTL: Update message popup pointer doesnt show up on correct side
https://bugs.documentfoundation.org/show_bug.cgi?id=113412 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7521 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157521] "Update available" bubble appears on wrong side of window (gtk3, LTR)
https://bugs.documentfoundation.org/show_bug.cgi?id=157521 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|"Update available" bubble |"Update available" bubble |appears on wrong side of|appears on wrong side of |window (gtk3) |window (gtk3, LTR) See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3412 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138863] Superordinate object of cells should be sheet, not page
https://bugs.documentfoundation.org/show_bug.cgi?id=138863 --- Comment #2 from Stéphane Guillou (stragu) --- How about: * cell's Text Direction property has the option "Same as sheet direction" instead of the current superordinate setting; * Text Direction setting removed from the page style dialog (although this would be problematic for backward-compatibility) (In reply to Eyal Rozenberg from comment #0) > This can be verified when examining the effect of changes to Page > style on properties of cells which are inherited from the superordinate > object, like text direction; see bug 138862. Can you think of other cell properties inherited from the page style? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147333] Sheet Styles in Calc (Page style)
https://bugs.documentfoundation.org/show_bug.cgi?id=147333 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=41 ||316 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 41316] Page styles should support hierarchical parent-child relationships (like paragraph or character styles)
https://bugs.documentfoundation.org/show_bug.cgi?id=41316 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7333 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138863] Superordinate object of cells should be sheet, not page
https://bugs.documentfoundation.org/show_bug.cgi?id=138863 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Blocks||107332 --- Comment #1 from Stéphane Guillou (stragu) --- It is true that pages are a "foreign entity" in a spreadsheet, and that most of a page style's properties only apply to the output (print, PDF...) of the document. In fact, the only exception to that (that I can see) is the Text Direction: it's the only property that also affects what is displayed in-app, on canvas. And it looks like it's the only cell style property that can use the superordinate value. (Which adds to the fact that linking cell styles to page styles is an odd thing.) So I don't think this particular issue warrants an overhaul of how styles are handled in Calc. Maybe the first (and only?) step in resolving this is to dissociate the property Text Direction from Page Styles, so cell styles and page styles are two unrelated things. (A related discussion would be envisaging the creation of Sheet Styles, but I'm not actually sure this adds anything to what we already have with Cell Styles.) Would you agree to reframe this issue as "remove Text Direction superordinate linking between Cell and Page Styles"? Or am I missing something? (And if you agree, then the solution for bug 138862 would be to have a "Default (LTR)" cell style applied to LTR sheets.) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107332 [Bug 107332] [META] Calc cell and page styles bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107332] [META] Calc cell and page styles bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107332 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||138863 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=138863 [Bug 138863] Superordinate object of cells should be sheet, not page -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134869] LO Writer: Grey line at the right and bottom when pasting an image - not in Print - only in view
https://bugs.documentfoundation.org/show_bug.cgi?id=134869 --- Comment #19 from Buovjaga --- Yes, even with View - Boundaries selected, there are no lines Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: a9ad36ae46ff76c0d59b0d170314fdd3a9ee5d35 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Bug 103152 depends on bug 134869, which changed state. Bug 134869 Summary: LO Writer: Grey line at the right and bottom when pasting an image - not in Print - only in view https://bugs.documentfoundation.org/show_bug.cgi?id=134869 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134869] LO Writer: Grey line at the right and bottom when pasting an image - not in Print - only in view
https://bugs.documentfoundation.org/show_bug.cgi?id=134869 xtr806...@xtra.co.nz changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #18 from xtr806...@xtra.co.nz --- Bug not present in version 7.6.4.1 No lines showing to right and bottom of inserted image as they did in version 7.5.3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 81397] FORMATTING: When the Default cell style's font size is modified, new sheets do not use corresponding row height
https://bugs.documentfoundation.org/show_bug.cgi?id=81397 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||6042 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106042] Calc does not use all the default template formatting when creating new sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=106042 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=81 ||397 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106042] Calc does not use all the default template formatting when creating new sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=106042 Stéphane Guillou (stragu) changed: What|Removed |Added CC||blth...@yahoo.com --- Comment #7 from Stéphane Guillou (stragu) --- *** Bug 90629 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90629] Unable to set default worksheet
https://bugs.documentfoundation.org/show_bug.cgi?id=90629 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #5 from Stéphane Guillou (stragu) --- I think bug 106042 is a good match here. *** This bug has been marked as a duplicate of bug 106042 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134869] LO Writer: Grey line at the right and bottom when pasting an image - not in Print - only in view
https://bugs.documentfoundation.org/show_bug.cgi?id=134869 --- Comment #17 from xtr806...@xtra.co.nz --- Grey lines at right and bottom of inserted image not present in version 7.6.4.1 Bug seems to have been fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158622] CSV which contains #N/A, cannot read as #N/A(NaN, Not a Number)
https://bugs.documentfoundation.org/show_bug.cgi?id=158622 ady changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from ady --- When saving as CSV: * Edit filter settings" ** Save cell formulas instead of calculated values When opening the CSV file with Calc, set the "Evaluate formulas" check box ON. Are you using those settings? If not, please specify which steps/settings you are using when saving the CSV and which ones when opening it. It may be helpful to "Add an attachment" with a sample csv file to your next post/comment in the bug report page. For me, no repro. Setting to NEEDINFO. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138862] Calc sheet cells keep direction despite sheet direction switch
https://bugs.documentfoundation.org/show_bug.cgi?id=138862 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #11 from Stéphane Guillou (stragu) --- Eyal, how do you envisage this to be implemented (with what we currently have, if we ignore bug 138863)? Would it be that an extra page style is available in LO, called something like "Default (LTR)", which has the LTR text direction and is applied automatically to the sheet when the UI is LTR or when a sheet is switched to LTR? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146326] The Autofilter Input Box should get focus upon mouse-hover
https://bugs.documentfoundation.org/show_bug.cgi?id=146326 Aron Budea changed: What|Removed |Added OS|Linux (All) |All Regression By||Caolán McNamara --- Comment #6 from Aron Budea --- Another symptom: When opening Filter by Condition -> Standard Filter..., the focus is initially in the dialog, but is lost almost immediately. This is a regression from the same commit. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] Add #SPILL! error
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 --- Comment #3 from ady --- (In reply to Óvári from comment #2) > Can you please change the Status to NEW? Unfortunately, comment 0 has nothing to do with comment 1, and the original Summery field has nothing to do with the change you made on it. So, ATM, I would suggest setting this report as invalid, unless you are willing to get this report back in track (and know how to do it). BTW, the #SPILL! error you mentioned in comment 1 would make no sense at this time in Calc, as the feature that would potentially trigger such error is not supported in Calc ATM. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158596] Context menu "Size" with unexpected entries in Kf5 and gen
https://bugs.documentfoundation.org/show_bug.cgi?id=158596 --- Comment #2 from Telesto --- Another possibility bug 158101 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158622] New: CSV which contains #N/A, cannot read as #N/A(NaN, Not a Number)
https://bugs.documentfoundation.org/show_bug.cgi?id=158622 Bug ID: 158622 Summary: CSV which contains #N/A, cannot read as #N/A(NaN, Not a Number) Product: LibreOffice Version: 7.6.4.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: polyes...@yahoo.co.jp Description: CSV file which contains #N/A, cannot read as #N/A(NaN, Not a Number). Steps to Reproduce: 1.Generate spreadsheet which contains #N/A in a cell. "=NA()" works fine. 2.Save the spreadsheet as CSV. 3.Check the CSV file by text editor(Vim, Emacs, ...). We can look #N/A in the file. 4.Read the CSV file using Calc. 5.Check the cell(containg #N/A) using ISNA() function. Actual Results: #N/A interpreted as string, so ISNA() return FALSE. Expected Results: #N/A in CSV should interpret as #N/A(NaN, Not A Number). Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158366] Blurry text hinting (possible regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=158366 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158303] LibreOffice not working on 1280x1024 screen
https://bugs.documentfoundation.org/show_bug.cgi?id=158303 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155259] Text indenting continually changes when I open the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155259 --- Comment #5 from QA Administrators --- Dear samuel.baker90, 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.
[Bug 98520] ODF Validator reported error: attribute "text:start-value" on element "text:list-level-style-number" has a bad value: "0"
https://bugs.documentfoundation.org/show_bug.cgi?id=98520 --- Comment #8 from QA Administrators --- Dear Franklin Weng, 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.
[Bug 134869] LO Writer: Grey line at the right and bottom when pasting an image - not in Print - only in view
https://bugs.documentfoundation.org/show_bug.cgi?id=134869 --- Comment #16 from QA Administrators --- Dear Udo, 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.
[Bug 35449] Paragraph properties of directly formatted text cause wrong reflow in large TABLES at "Print Layout"
https://bugs.documentfoundation.org/show_bug.cgi?id=35449 --- Comment #21 from QA Administrators --- Dear nochschneller, 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.
[Bug 158620] Add #SPILL! error
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 --- Comment #2 from Óvári --- Can you please change the Status to NEW? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158621] New: LibreOffice.app does not launch on MacOS 12.7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=158621 Bug ID: 158621 Summary: LibreOffice.app does not launch on MacOS 12.7.1 Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gordon.w.r...@gmail.com Description: Double click (in finder) /Applications/LibreOffice.app or control click on that and select open. The menu line shows LibreOffice for one second or so, and then disappears without any other visible activity. I tried three versions: (all fail the same way) 7.5.9 from the App. store 7.5.9 from the LO download page 7.6.4 from the LO download page Steps to Reproduce: 1. Double click (in finder) /Applications/LibreOffice.app 2. (alternative) control click on that and select op Actual Results: The menu line shows LibreOffice for one second or so, and then disappears without any other visible activity. Expected Results: At least one window should open Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127293] Add XLOOKUP function in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=127293 Óvári changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |8620| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128425] Add XMATCH function in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=128425 Óvári changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |8620| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] Add #SPILL! error
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 Óvári changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |8425, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |7293| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126573] Add array functions in Calc: FILTER, SORT, SORTBY, UNIQUE, SEQUENCE, RANDARRAY
https://bugs.documentfoundation.org/show_bug.cgi?id=126573 Óvári changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8620 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127293] Add XLOOKUP function in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=127293 Óvári changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8620 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128425] Add XMATCH function in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=128425 Óvári changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8620 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] Add #SPILL! error
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 Óvári changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8425, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||7293, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6573 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126573] Add array functions in Calc: FILTER, SORT, SORTBY, UNIQUE, SEQUENCE, RANDARRAY
https://bugs.documentfoundation.org/show_bug.cgi?id=126573 --- Comment #18 from Óvári --- (In reply to Jacob H from comment #9) > I'll start by saying that dynamic Array manipulation is critical in handling > data and has so many use cases. In my opinion the dynamic handling of arrays > is the only remaining missing link in both function and form, at least as > far as data handling in Calc. Dynamic arrays https://support.microsoft.com/en-us/office/dynamic-array-formulas-and-spilled-array-behavior-205c6b06-03ba-4151-89a1-87a7eb36e531 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158620] Add #SPILL! error
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 Óvári changed: What|Removed |Added Summary|TRANSPOSE() function does |Add #SPILL! error |not provide a message when | |bounds exceeded | --- Comment #1 from Óvári --- Add #SPILL! error 1. Spill range isn't blank 2. Indeterminate size 3. Extends beyond the worksheet's edge 4. Table formula 5. Out of memory 6. Spill into merged cells 7. Unrecognized/Fallback How to correct a #SPILL! error https://support.microsoft.com/en-us/office/how-to-correct-a-spill-error-ffe0f555-b479-4a17-a6e2-ef9cc9ad4023 -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'feature/cib_contract57d' - desktop/qa
desktop/qa/desktop_lib/test_desktop_lib.cxx |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) New commits: commit 55942278621f937b576e88eafa705e1e0c24b387 Author: Miklos Vajna AuthorDate: Mon Nov 27 11:21:57 2023 +0100 Commit: Thorsten Behrens CommitDate: Sun Dec 10 02:21:21 2023 +0100 CppunitTest_desktop_lib: adjust asserts so this works again Change-Id: Id6aba3d9203e3fe4e95771a895d1de50a2030908 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/159990 Tested-by: Jenkins CollaboraOffice Tested-by: Caolán McNamara Reviewed-by: Caolán McNamara (cherry picked from commit ececb678b8362e3be8e02768ddd5e4197d87dc2a) diff --git a/desktop/qa/desktop_lib/test_desktop_lib.cxx b/desktop/qa/desktop_lib/test_desktop_lib.cxx index f3f09b71aa2a..83083b4bf7b3 100644 --- a/desktop/qa/desktop_lib/test_desktop_lib.cxx +++ b/desktop/qa/desktop_lib/test_desktop_lib.cxx @@ -2415,7 +2415,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_ODT() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(1), nState); +// OK or NOTVALIDATED (signature is OK, but certificate could not be validated) +CPPUNIT_ASSERT(nState == 1 || nState == 4); } void DesktopLOKTest::testInsertCertificate_PEM_DOCX() @@ -2475,7 +2476,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_DOCX() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(5), nState); +// PARTIAL_OK or NOTVALIDATED_PARTIAL_OK +CPPUNIT_ASSERT(nState == 5 || nState == 6); } void DesktopLOKTest::testSignDocument_PEM_PDF()
core.git: Branch 'feature/cib_contract138e' - desktop/qa
desktop/qa/desktop_lib/test_desktop_lib.cxx |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) New commits: commit 25ffe7988fab62f4e60899401c7b0876f73a31e5 Author: Miklos Vajna AuthorDate: Mon Nov 27 11:21:57 2023 +0100 Commit: Thorsten Behrens CommitDate: Sun Dec 10 02:19:27 2023 +0100 CppunitTest_desktop_lib: adjust asserts so this works again Change-Id: Id6aba3d9203e3fe4e95771a895d1de50a2030908 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/159990 Tested-by: Jenkins CollaboraOffice Tested-by: Caolán McNamara Reviewed-by: Caolán McNamara (cherry picked from commit ececb678b8362e3be8e02768ddd5e4197d87dc2a) diff --git a/desktop/qa/desktop_lib/test_desktop_lib.cxx b/desktop/qa/desktop_lib/test_desktop_lib.cxx index 5c17f880e2de..014e64f86fff 100644 --- a/desktop/qa/desktop_lib/test_desktop_lib.cxx +++ b/desktop/qa/desktop_lib/test_desktop_lib.cxx @@ -2669,7 +2669,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_ODT() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(1), nState); +// OK or NOTVALIDATED (signature is OK, but certificate could not be validated) +CPPUNIT_ASSERT(nState == 1 || nState == 4); } void DesktopLOKTest::testInsertCertificate_PEM_DOCX() @@ -2726,7 +2727,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_DOCX() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(5), nState); +// PARTIAL_OK or NOTVALIDATED_PARTIAL_OK +CPPUNIT_ASSERT(nState == 5 || nState == 6); } void DesktopLOKTest::testSignDocument_PEM_PDF()
[Bug 127293] Add XLOOKUP function in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=127293 --- Comment #35 from Óvári --- (In reply to LBR from comment #34) > I have actually found Google Sheets functionality has really come on in > recent years, and I can use the XLOOKUP formula in there where I need that > in meantime Are there any other functions missing in LibreOffice Calc core functionality that require Microsoft Excel or Google Sheets in the meantime? Having a complete list of all the missing functions could help TDF to strategize more effectively. Thank you -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'distro/allotropia/zeta-7-4' - desktop/qa
desktop/qa/desktop_lib/test_desktop_lib.cxx |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) New commits: commit cc0ff5ac5245bc9cd574ccc56a4d7b44fdefc381 Author: Miklos Vajna AuthorDate: Mon Nov 27 11:21:57 2023 +0100 Commit: Thorsten Behrens CommitDate: Sun Dec 10 02:16:36 2023 +0100 CppunitTest_desktop_lib: adjust asserts so this works again Change-Id: Id6aba3d9203e3fe4e95771a895d1de50a2030908 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/159990 Tested-by: Jenkins CollaboraOffice Tested-by: Caolán McNamara Reviewed-by: Caolán McNamara (cherry picked from commit ececb678b8362e3be8e02768ddd5e4197d87dc2a) diff --git a/desktop/qa/desktop_lib/test_desktop_lib.cxx b/desktop/qa/desktop_lib/test_desktop_lib.cxx index 1898d3f1377f..be3d9ebd3253 100644 --- a/desktop/qa/desktop_lib/test_desktop_lib.cxx +++ b/desktop/qa/desktop_lib/test_desktop_lib.cxx @@ -2829,7 +2829,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_ODT() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(1), nState); +// OK or NOTVALIDATED (signature is OK, but certificate could not be validated) +CPPUNIT_ASSERT(nState == 1 || nState == 4); } void DesktopLOKTest::testInsertCertificate_PEM_DOCX() @@ -2886,7 +2887,8 @@ void DesktopLOKTest::testInsertCertificate_PEM_DOCX() } int nState = pDocument->m_pDocumentClass->getSignatureState(pDocument); -CPPUNIT_ASSERT_EQUAL(int(5), nState); +// PARTIAL_OK or NOTVALIDATED_PARTIAL_OK +CPPUNIT_ASSERT(nState == 5 || nState == 6); } void DesktopLOKTest::testSignDocument_PEM_PDF()
[Bug 158620] New: TRANSPOSE() function does not provide a message when bounds exceeded
https://bugs.documentfoundation.org/show_bug.cgi?id=158620 Bug ID: 158620 Summary: TRANSPOSE() function does not provide a message when bounds exceeded Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ovari...@zoho.com Description: TRANSPOSE() function produces an result which is incorrect and should warn when operation can not be performed due to being out of bounds. Steps to Reproduce: 1. In cells XFC1:XFD4, enter 1, 2, 3, 4, 5, 6, 7, 8 2. In cell XFC6, enter the formula =transpose(XFC1:XFD4) 3. Press Enter 4. Cell XFC6 shows the value 1, and there are no other elements in the transpose matrix as the matrix would be outside the bounds of the sheet Should there be a warning or an error message when the operation can not be done due to the values extending beyond the boundary of the Sheet? Actual Results: 1. Produces an incorrect value. The result is a value in only 1 cell which is not a transpose of the matrix. 2. No feedback provided when operation can not be performed. Expected Results: 1. Should show an error value in cell instead of 1. 2. Feedback message when operating can not be performed due to out of bounds. Reproducible: Always User Profile Reset: No Additional Info: Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Bug 86209] MENUS: Reorganize the View menu
https://bugs.documentfoundation.org/show_bug.cgi?id=86209 --- Comment #29 from Charlotte --- Okie Concrete is your best choice among all the Oklahoma City concrete companies! Concrete is the most popular and one of the oldest building materials we have https://www.okieconcrete.com/ -- You are receiving this mail because: You are the assignee for the bug.
core.git: external/libeot solenv/gbuild
external/libeot/ExternalProject_libeot.mk |1 - solenv/gbuild/platform/com_GCC_defs.mk|4 2 files changed, 5 deletions(-) New commits: commit 6fa6599963fb7d5ba411540b181c581bbbeb1e9d Author: Thorsten Behrens AuthorDate: Mon Dec 4 13:56:55 2023 +0100 Commit: Thorsten Behrens CommitDate: Sun Dec 10 00:37:58 2023 +0100 Remove hard limit to c89 for clang This seems no longer true: "Windows MSVC only supports C90 so force gnu89" With that said, also do a revert: "external/libeot internally uses --std=c99, do not overrule that" This reverts commit 61a66b612eaeeb38d5d9f9aa83326be6b08c1b6f. Change-Id: Id628131b4fa6b61e19da6d862d773ab36f201729 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160454 Tested-by: Jenkins Reviewed-by: Thorsten Behrens diff --git a/external/libeot/ExternalProject_libeot.mk b/external/libeot/ExternalProject_libeot.mk index 98c7d2eb403d..6e5f465333cc 100644 --- a/external/libeot/ExternalProject_libeot.mk +++ b/external/libeot/ExternalProject_libeot.mk @@ -23,7 +23,6 @@ $(call gb_ExternalProject_get_state_target,libeot,build) : --enable-static \ --disable-shared \ --disable-debug \ - CFLAGS='$(filter-out -std=gnu89,$(CFLAGS))' \ && $(MAKE) $(if $(verbose),V=1) \ ) $(call gb_Trace_EndRange,libeot,EXTERNAL) diff --git a/solenv/gbuild/platform/com_GCC_defs.mk b/solenv/gbuild/platform/com_GCC_defs.mk index 7ea7a16461e3..3f50c4089b09 100644 --- a/solenv/gbuild/platform/com_GCC_defs.mk +++ b/solenv/gbuild/platform/com_GCC_defs.mk @@ -186,10 +186,6 @@ gb_CXX03FLAGS := -std=gnu++98 -Wno-long-long \ -Wno-variadic-macros -Wno-deprecated-declarations endif -# On Windows MSVC only supports C90 so force gnu89 (especially in clang) to -# to catch potential gnu89/C90 incompatibilities locally. -gb_CFLAGS_COMMON += -std=gnu89 - ifeq ($(ENABLE_LTO),TRUE) ifeq ($(COM_IS_CLANG),TRUE) gb_LTOFLAGS := -flto=thin
[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins
https://bugs.documentfoundation.org/show_bug.cgi?id=158523 --- Comment #9 from tim --- (In reply to tim from comment #6) > (In reply to m.a.riosv from comment #5) > > Created attachment 191312 [details] > > Screenshot with the file and the pdf > > > > It is the same for me in both. > > But I don't have installed your font(s), you can see it as italic on the top > > of writer the font name in the screenshot. > > Your attachment shows page 61, but the bottom of the page says page 64. If > you look at my comment (#3) it says in the second paragraph: "You will see > on page 59 (labeled page 62) that there are no comments in the margin." > Please look at it again. The problem is still there. See my comment above. Will you please send a side-by-side screen shot of the pdf file you created page 59 and the odt file page 59. These should both say "page 62" at the bottom of their pages. It does not matter if you have the correct font. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158619] a diaporama made with Powerpoint and imported in Impress is blank when opened again with PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=158619 david.vantyg...@laposte.net changed: What|Removed |Added Summary|A diaporama made with |a diaporama made with |LibreOffice is blank when |Powerpoint and imported in |opened with PowerPoint |Impress is blank when ||opened again with ||PowerPoint -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158619] A diaporama made with LibreOffice is blank when opened with PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=158619 --- Comment #3 from david.vantyg...@laposte.net --- Created attachment 191341 --> https://bugs.documentfoundation.org/attachment.cgi?id=191341=edit Powerpoint pages are blank -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158619] A diaporama made with LibreOffice is blank when opened with PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=158619 --- Comment #2 from david.vantyg...@laposte.net --- Created attachment 191340 --> https://bugs.documentfoundation.org/attachment.cgi?id=191340=edit Powerpoint error -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins
https://bugs.documentfoundation.org/show_bug.cgi?id=158523 --- Comment #8 from m.a.riosv --- As I said I don't have the font installed, that's why the number of pages I see doesn't match the number of pages you see. But there is a correspondence between how I see the odt and how the pdf looks like, as shown in the screenshot I attached. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158619] A diaporama made with LibreOffice is blank when opened with PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=158619 --- Comment #1 from david.vantyg...@laposte.net --- Created attachment 191339 --> https://bugs.documentfoundation.org/attachment.cgi?id=191339=edit Impress file to test -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158619] New: A diaporama made with LibreOffice is blank when opened with PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=158619 Bug ID: 158619 Summary: A diaporama made with LibreOffice is blank when opened with PowerPoint Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: david.vantyg...@laposte.net Description: I made the joined diaporama with Impress. When I open it with MS Powerpoint, there's an error message and the file is blank. Steps to Reproduce: 1.Open the file with Powerpoint Actual Results: All pages are blank Expected Results: Pages shouldn't be blank. Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins
https://bugs.documentfoundation.org/show_bug.cgi?id=158523 --- Comment #7 from tim --- Created attachment 191338 --> https://bugs.documentfoundation.org/attachment.cgi?id=191338=edit screenshot of page 62 I have attached a screenshot of page 62. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151040] Logo in Start Center initially shows correctly but then only shows some pixels after returning from a LibreOffice application.
https://bugs.documentfoundation.org/show_bug.cgi?id=151040 --- Comment #17 from Kityn --- UI: en-US The logo looks fine all the time. UI: pl-PL The logo is partially hidden after going back to the start menu. LO 7.6.4 x64 Windows 10 22H2 x64 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158618] Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=158618 --- Comment #2 from david.vantyg...@laposte.net --- Created attachment 191337 --> https://bugs.documentfoundation.org/attachment.cgi?id=191337=edit On of the the Draw pictures I copied and pasted in the Writer document -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158523] Whole pages of Comments are not PRINTING or exported to PDF in margins
https://bugs.documentfoundation.org/show_bug.cgi?id=158523 --- Comment #6 from tim --- (In reply to m.a.riosv from comment #5) > Created attachment 191312 [details] > Screenshot with the file and the pdf > > It is the same for me in both. > But I don't have installed your font(s), you can see it as italic on the top > of writer the font name in the screenshot. Your attachment shows page 61, but the bottom of the page says page 64. If you look at my comment (#3) it says in the second paragraph: "You will see on page 59 (labeled page 62) that there are no comments in the margin." Please look at it again. The problem is still there. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158618] Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=158618 --- Comment #1 from david.vantyg...@laposte.net --- Created attachment 191336 --> https://bugs.documentfoundation.org/attachment.cgi?id=191336=edit File to test this bug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158618] New: Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file
https://bugs.documentfoundation.org/show_bug.cgi?id=158618 Bug ID: 158618 Summary: Picture made with draw and pasted in Writer disappear when you modify or/and register Writer file Product: LibreOffice Version: 7.3.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: david.vantyg...@laposte.net Description: I made pictures with Draw and copy-paste them in a Writer document. When I modify or simply save the file, close it and reopen it, the picture in the third page before end of the document disappears. Steps to Reproduce: 1.Download and save the joined Writer file on your desktop. 2.Open this file. Look at the last three pages, there are pictures in it, made with Draw. 3.Modify the document and save it or simply save it without modifying it. 4. Close the document and reopen it. 5. Go to the third page before end : the picture as disappeared. Actual Results: The picture at the third page before end disappears. Expected Results: The picture at the third page should not disappear. Reproducible: Always User Profile Reset: No Additional Info: I can reproduce this bug on two different computers. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158617] New: Underlining no vertical separation from text
https://bugs.documentfoundation.org/show_bug.cgi?id=158617 Bug ID: 158617 Summary: Underlining no vertical separation from text Product: LibreOffice Version: 7.6.4.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gjeil...@outlook.com Version 7.3.7.2 underline works okay. Some version after 7.3.7.2 introduces a bug where the underlines are not properly spaced vertically from the underlined text, and various incorrect responses occur from selecting and unselecting the underline icon or the underline menu choice. I have not narrowed this down to the offending update other than it being somewhere between 7.3.7.2 and the latest release. The same problem appears with Windows and Ubuntu OS. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158461] Flicker during live resizing when using Skia/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=158461 Patrick Luby changed: What|Removed |Added Resolution|--- |FIXED Assignee|libreoffice-b...@lists.free |plub...@libreoffice.org |desktop.org | Status|UNCONFIRMED |RESOLVED --- Comment #2 from Patrick Luby --- I have committed a fix and the fix should be in tomorrow's (10 December 2023) nightly master builds: https://dev-builds.libreoffice.org/daily/master/current.html Note for testers: the nightly master builds install in /Applications/LibreOfficeDev.app. These builds are not codesigned like regular LibreOffice releases so you will need to execute the following Terminal command after installation but before you launch /Applications/LibreOfficeDev: xattr -d com.apple.quarantine /Applications/LibreOfficeDev.app -- You are receiving this mail because: You are the assignee for the bug.
core.git: vcl/osx
vcl/osx/salframeview.mm |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
New commits:
commit f7e81a321bc3e4880fc652e7ba24867bba557007
Author: Patrick Luby
AuthorDate: Sat Dec 9 16:19:18 2023 -0500
Commit: Patrick Luby
CommitDate: Sat Dec 9 23:07:58 2023 +0100
tdf#158461 eliminate flicker during live resizing
When using Skia/Metal, the window content will flicker while
live resizing a window if we don't send a paint event.
Change-Id: Ib3edc497e26e6abfdfd17a34f9269a3eae090805
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160519
Tested-by: Jenkins
Reviewed-by: Patrick Luby
diff --git a/vcl/osx/salframeview.mm b/vcl/osx/salframeview.mm
index 4fd5913efc05..c0b23f80a7d6 100644
--- a/vcl/osx/salframeview.mm
+++ b/vcl/osx/salframeview.mm
@@ -465,8 +465,12 @@ static void updateWinDataInLiveResize(bool bInLiveResize)
else
{
[self clearLiveResizeTimer];
-mpFrame->SendPaintEvent();
}
+
+// tdf#158461 eliminate flicker during live resizing
+// When using Skia/Metal, the window content will flicker while
+// live resizing a window if we don't send a paint event.
+mpFrame->SendPaintEvent();
}
mbInWindowDidResize = NO;
[Bug 158461] Flicker during live resizing when using Skia/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=158461 --- Comment #1 from Commit Notification --- Patrick Luby committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f7e81a321bc3e4880fc652e7ba24867bba557007 tdf#158461 eliminate flicker during live resizing It will be available in 24.8.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.
[Bug 158461] Flicker during live resizing when using Skia/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=158461 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140401] LibreOffice crashed due to custom installed fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=140401 Patrick Luby changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |plub...@libreoffice.org |desktop.org | Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #22 from Patrick Luby --- I can reproduce this crash if I manually copy the following fonts into my ~/Library/Fonts folder, launch the Font Book application, and then launch LibreOffice: HanaMin.sfont HanaMinEx.sfont HanaMinExA1.otf HanaMinExA2.otf HanaMinExB.otf If I validate the HanaMin.sfont in the Font Book application, Font Book says that the font has 1 serious problem i.e. it is a badly formatted font file. Disabling the HanaMin.sfont stops the crashing. Below is that LibreOffice crash stack. I can if I can detect a bad font like HanaMin.sfont so that LibreOffice can skip loading it: (lldb) bt * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) * frame #0: 0x000188eef6d0 CoreFoundation`CF_IS_OBJC + 24 frame #1: 0x000188dbbe50 CoreFoundation`CFNumberGetValue + 264 frame #2: 0x0001119c2aac libvclplug_osxlo.dylib`DevFontFromCTFontDescriptor(pFD=0x604acf60, bFontEnabled=0x00016fdfce17) at SystemFontList.cxx:121:5 frame #3: 0x0001119c3b30 libvclplug_osxlo.dylib`fontEnumCallBack(pValue=0x604acf60, pContext=0x63b8d940) at SystemFontList.cxx:210:27 frame #4: 0x000188ddf048 CoreFoundation`CFArrayApplyFunction + 72 frame #5: 0x0001119c3abc libvclplug_osxlo.dylib`SystemFontList::Init(this=0x63b8d940) at SystemFontList.cxx:279:5 frame #6: 0x0001119c3c8c libvclplug_osxlo.dylib`GetCoretextFontList() at SystemFontList.cxx:287:17 frame #7: 0x0001119ceff8 libvclplug_osxlo.dylib`AquaSalGraphics::GetDevFontList(this=0x000152796c70, pFontCollection=0x60a91898) at salgdi.cxx:275:28 frame #8: 0x00011536eae8 libvcllo.dylib`OutputDevice::ImplInitFontList(this=0x000152798370) const at font.cxx:643:17 frame #9: 0x000115372544 libvcllo.dylib`OutputDevice::ImplNewFont(this=0x000152798370) const at font.cxx:700:5 frame #10: 0x00011537048c libvcllo.dylib`OutputDevice::InitFont(this=0x000152798370) const at font.cxx:660:10 frame #11: 0x0001153803ec libvcllo.dylib`OutputDevice::ImplLayout(this=0x000152798370, rOrigStr=0x000152791af0, nMinIndex=0, nLen=0, rLogicalPos=0x00016fdfda90, nLogicalWidth=0, pDXArray=KernArraySpan @ 0x00016fdfd890, pKashidaArray=size=0, flags=NONE, pLayoutCache=0x, pGlyphs=0x) const at text.cxx:1074:10 frame #12: 0x00011537fef4 libvcllo.dylib`OutputDevice::DrawText(this=0x000152798370, rStartPt=0x00016fdfda90, rStr=0x000152791af0, nIndex=0, nLen=0, pVector=0x, pDisplayText=0x, pLayoutCache=0x) at text.cxx:626:45 frame #13: 0x000105907d44 libspllo.dylib`(anonymous namespace)::SplashScreenWindow::Paint(this=0x61ed4870, rRenderContext=0x000152792070, (null)=0x00016fdfdc00) at splash.cxx:607:16 frame #14: 0x00010590e918 libspllo.dylib`(anonymous namespace)::SplashScreenWindow::Redraw(this=0x61ed4870) at splash.cxx:142:5 frame #15: 0x00010590ec14 libspllo.dylib`(anonymous namespace)::SplashScreen::updateStatus(this=0x000152791a30) at splash.cxx:319:14 frame #16: 0x00010590669c libspllo.dylib`(anonymous namespace)::SplashScreen::setValue(this=0x000152791a30, nValue=10) at splash.cxx:240:9 frame #17: 0x000100ffd888 libsofficeapp.dylib`desktop::Desktop::SetSplashScreenProgress(this=0x00016fdff1f8, iProgress=10) at app.cxx:2452:26 frame #18: 0x000100ffb2a0 libsofficeapp.dylib`desktop::Desktop::Main(this=0x00016fdff1f8) at app.cxx:1292:5 frame #19: 0x00011591145c libvcllo.dylib`ImplSVMain() at svmain.cxx:229:35 frame #20: 0x00011198e418 libvclplug_osxlo.dylib`AquaSalInstance::handleAppDefinedEvent(pEvent=0x614d5500) at salinst.cxx:448:20 frame #21: 0x000111a22534 libvclplug_osxlo.dylib`-[VCL_NSApplication sendEvent:](self=0x000152706fa0, _cmd="sendEvent:", pEvent=0x614d5500) at vclnsapp.mm:92:9 frame #22: 0x00018ca1e110 AppKit`-[NSApplication _handleEvent:] + 60 frame #23: 0x00018c5ea124 AppKit`-[NSApplication run] + 512 frame #24: 0x00018c5c13cc AppKit`NSApplicationMain + 880 frame #25: 0x0001119930a4 libvclplug_osxlo.dylib`AquaSalInstance::SVMainHook(this=0x0001526077a0, pnInit=0x00016fdff148) at salinst.cxx:1074:5 frame #26: 0x00011591141c libvcllo.dylib`ImplSVMain() at svmain.cxx:222:54 frame #27: 0x000115912d1c libvcllo.dylib`SVMain() at svmain.cxx:261:12
[Bug 157065] Maximising a Base form opens it too wide the next time (Windows, multiple screens)
https://bugs.documentfoundation.org/show_bug.cgi?id=157065 Kityn changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Kityn --- Reports are also affected. Forms and Reports (in Design View) always open centered and unmaximized (oversized if saved as maximized). LO 7.6.4 x64 Windows 10 22H2 x64 Single monitor -- You are receiving this mail because: You are the assignee for the bug.
core.git: 2 commits - basic/source desktop/source filter/source lotuswordpro/source sc/inc sc/source sd/source starmath/inc starmath/source stoc/source svl/source sw/source toolkit/source vcl/source w
basic/source/basmgr/basmgr.cxx|9 -
desktop/source/deployment/gui/dp_gui_updatedialog.cxx |5 ++---
filter/source/xsltfilter/XSLTFilter.cxx |3 +--
lotuswordpro/source/filter/lwplayout.cxx |4 +---
sc/inc/scmatrix.hxx |2 +-
sc/source/core/tool/interpr5.cxx |2 +-
sc/source/core/tool/scmatrix.cxx |6 +++---
sd/source/core/drawdoc4.cxx |3 +--
sd/source/ui/animations/CustomAnimationPane.cxx |8 ++--
sd/source/ui/app/sdmod2.cxx |6 ++
starmath/inc/ElementsDockingWindow.hxx|4 ++--
starmath/source/SmElementsPanel.cxx |2 +-
starmath/source/SmElementsPanel.hxx |2 +-
stoc/source/invocation/invocation.cxx |3 +--
svl/source/misc/sharecontrolfile.cxx |5 ++---
sw/source/core/doc/DocumentDeviceManager.cxx |3 +--
sw/source/core/text/itrform2.cxx |3 +--
sw/source/uibase/dbui/mailmergehelper.cxx |3 +--
toolkit/source/controls/stdtabcontrollermodel.cxx |5 ++---
vcl/source/filter/ipdf/pdfread.cxx|9 -
writerfilter/source/dmapper/TableManager.hxx |2 +-
xmloff/source/text/txtlists.cxx |4 +---
22 files changed, 36 insertions(+), 57 deletions(-)
New commits:
commit 46b4a5a76816ea8646b726126c3935ebea870180
Author: Caolán McNamara
AuthorDate: Sat Dec 9 20:22:24 2023 +
Commit: Caolán McNamara
CommitDate: Sat Dec 9 22:38:56 2023 +0100
cid#1546300 std::swap COPY_INSTEAD_OF_MOVE
Change-Id: I304f0a9b1f90b77b56c6782bea293075ab9effe4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160516
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sd/source/ui/animations/CustomAnimationPane.cxx
b/sd/source/ui/animations/CustomAnimationPane.cxx
index 7eb623138713..77607e06d033 100644
--- a/sd/source/ui/animations/CustomAnimationPane.cxx
+++ b/sd/source/ui/animations/CustomAnimationPane.cxx
@@ -1672,12 +1672,8 @@ static bool getTextSelection( const Any& rSelection,
Reference< XShape >& xShape
Reference< XTextRange > xStart( xSelectedText->getStart() );
Reference< XTextRange > xEnd( xSelectedText->getEnd() );
-if( xTextRangeCompare->compareRegionEnds( xStart, xEnd ) < 0 )
-{
-Reference< XTextRange > xTemp( xStart );
-xStart = xEnd;
-xEnd = xTemp;
-}
+if (xTextRangeCompare->compareRegionEnds(xStart, xEnd) < 0)
+std::swap(xStart, xEnd);
sal_Int16 nPara = 0;
while( xParaEnum->hasMoreElements() )
commit a58c0d4cefe4de132af32d910ec797a2efb3ee3a
Author: Caolán McNamara
AuthorDate: Sat Dec 9 19:32:40 2023 +
Commit: Caolán McNamara
CommitDate: Sat Dec 9 22:38:50 2023 +0100
cid#1556778 COPY_INSTEAD_OF_MOVE
and
cid#1546474 COPY_INSTEAD_OF_MOVE
cid#1546473 COPY_INSTEAD_OF_MOVE
cid#1546469 COPY_INSTEAD_OF_MOVE
cid#1546467 COPY_INSTEAD_OF_MOVE
cid#1546458 COPY_INSTEAD_OF_MOVE
cid#1546448 COPY_INSTEAD_OF_MOVE
cid#1546446 COPY_INSTEAD_OF_MOVE
cid#1546441 COPY_INSTEAD_OF_MOVE
cid#1546424 COPY_INSTEAD_OF_MOVE
cid#1546377 COPY_INSTEAD_OF_MOVE
cid#1546374 COPY_INSTEAD_OF_MOVE
cid#1546352 COPY_INSTEAD_OF_MOVE
cid#1546334 COPY_INSTEAD_OF_MOVE
cid#1546328 COPY_INSTEAD_OF_MOVE
cid#1546310 COPY_INSTEAD_OF_MOVE
cid#1546303 COPY_INSTEAD_OF_MOVE
Change-Id: I8a43fdd574857ba1d3ec416f23c8269a9a08e12f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160515
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/basic/source/basmgr/basmgr.cxx b/basic/source/basmgr/basmgr.cxx
index c619bbf1fb6a..934297af3862 100644
--- a/basic/source/basmgr/basmgr.cxx
+++ b/basic/source/basmgr/basmgr.cxx
@@ -301,18 +301,17 @@ void SAL_CALL
BasMgrContainerListenerImpl::elementRemoved( const container::Cont
}
BasicError::BasicError( ErrCodeMsg nId, BasicErrorReason nR )
+: nErrorId(std::move(nId))
+, nReason(nR)
{
-nErrorId= nId;
-nReason = nR;
}
BasicError::BasicError( const BasicError& rErr )
+: nErrorId(rErr.nErrorId)
+, nReason(rErr.nReason)
{
-nErrorId= rErr.nErrorId;
-nReason = rErr.nReason;
}
-
class BasicLibInfo
{
private:
diff --git a/desktop/source/deployment/gui/dp_gui_updatedialog.cxx
b/desktop/source/deployment/gui/dp_gui_updatedialog.cxx
index e8da99f3c103..85786e63535c 100644
--- a/desktop/source/deployment/gui/dp_gui_updatedialog.cxx
+++ b/desktop/source/deployment/gui/dp_gui_updatedialog.cxx
@@ -665,13 +665,12 @@ void UpdateDialog::notifyMenubar( bool bPrepareOnly, bool
bRecheckOnly )
dp_gui::UpdateData aUpdData =
[Bug 134876] Create absolute range references when pointer-selecting cell ranges in Function Wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=134876 david.vantyg...@laposte.net changed: What|Removed |Added Status|VERIFIED|CLOSED --- Comment #8 from david.vantyg...@laposte.net --- It works with Calc 7.3.7.2. Thank you very much. -- You are receiving this mail because: You are the assignee for the bug.
core.git: svx/source sw/source
svx/source/form/fmshimp.cxx|2 +-
sw/source/core/layout/paintfrm.cxx |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
New commits:
commit cf3dda7c1c1da50db75d4c022bef279149d26636
Author: Caolán McNamara
AuthorDate: Sat Dec 9 19:28:18 2023 +
Commit: Caolán McNamara
CommitDate: Sat Dec 9 21:59:57 2023 +0100
cid#1546275 Using invalid iterator
and
cid#1545870 Using invalid iterator
Change-Id: I7a517fd67d1100a2feebfd3903c1804a2dcc2992
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160514
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/svx/source/form/fmshimp.cxx b/svx/source/form/fmshimp.cxx
index d54c5acaebde..890394856688 100644
--- a/svx/source/form/fmshimp.cxx
+++ b/svx/source/form/fmshimp.cxx
@@ -3372,7 +3372,7 @@ void FmXFormShell::CreateExternalView_Lock()
// list source
MapUString2UstringSeq::const_iterator aCurrentListSource =
aRadioListSources.find(rCtrlSource.first);
-DBG_ASSERT(aCurrentListSource != aRadioListSources.end(),
+assert(aCurrentListSource != aRadioListSources.end() &&
"FmXFormShell::CreateExternalView : inconsistent radio
descriptions !");
pListBoxDescription->Name = FM_PROP_LISTSOURCE;
pListBoxDescription->Value <<= (*aCurrentListSource).second;
diff --git a/sw/source/core/layout/paintfrm.cxx
b/sw/source/core/layout/paintfrm.cxx
index 0f048c4e805d..8ca5e35d1c84 100644
--- a/sw/source/core/layout/paintfrm.cxx
+++ b/sw/source/core/layout/paintfrm.cxx
@@ -2746,8 +2746,8 @@ void SwTabFramePainter::FindStylesForLine( Point&
rStartPoint,
}
aMapIter = maHoriLines.find( rStartPoint.Y() );
-OSL_ENSURE( aMapIter != maHoriLines.end(), "FindStylesForLine: Error" );
-const SwLineEntrySet& rHoriSet = (*aMapIter).second;
+assert(aMapIter != maHoriLines.end() && "FindStylesForLine: Error");
+const SwLineEntrySet& rHoriSet = aMapIter->second;
for ( const SwLineEntry& rEntry : rHoriSet )
{
[Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Regina Henschel changed: What|Removed |Added Depends on||158451 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158451 [Bug 158451] FILEOPEN DOCX Getting Hang issue on file having 'inline' group with child with text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158451] FILEOPEN DOCX Getting Hang issue on file having 'inline' group with child with text
https://bugs.documentfoundation.org/show_bug.cgi?id=158451 Regina Henschel changed: What|Removed |Added Blocks||136328 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136328 [Bug 136328] [META] DOCX Grouped shape related issues -- You are receiving this mail because: You are the assignee for the bug.
core.git: configmgr/source
configmgr/source/localizedvaluenode.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 9c22c643ffb6ec0d16b6998cf07d61867042b8b5
Author: Caolán McNamara
AuthorDate: Sat Dec 9 19:26:55 2023 +
Commit: Caolán McNamara
CommitDate: Sat Dec 9 21:30:41 2023 +0100
cid#1558833 Uninitialized scalar field
Change-Id: I8c617c20f725f4277a0c4d637be336c6624c3238
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160513
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/configmgr/source/localizedvaluenode.cxx
b/configmgr/source/localizedvaluenode.cxx
index 7f377cc65e2f..407040a560c0 100644
--- a/configmgr/source/localizedvaluenode.cxx
+++ b/configmgr/source/localizedvaluenode.cxx
@@ -34,7 +34,7 @@ LocalizedValueNode::LocalizedValueNode(int layer,
css::uno::Any value):
{}
LocalizedValueNode::LocalizedValueNode(int layer):
-Node(layer)
+Node(layer), modified_(false)
{}
rtl::Reference< Node > LocalizedValueNode::clone(bool) const {
[Bug 158616] New: Verankerung von Bildern im Writer funktioniert nicht mehr
https://bugs.documentfoundation.org/show_bug.cgi?id=158616 Bug ID: 158616 Summary: Verankerung von Bildern im Writer funktioniert nicht mehr Product: LibreOffice Version: 7.5.9.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: uwe.k...@p2-online.com Description: Wenn man Bilder "als Zeichen" verankert, wird nur der Rahmen des Bildes komplett angezeigt, vom Bild selber fehlt etwa 1/3. Bisher gab es dabei überhaupt kein Problem. Für meine Arbeiten wäre es sehr wichtig die Bilder wieder vernünftig als Zeichen zu verankern, weil man die Positonvon Text und Bildern am Besten arrangieren kann. Ich habe alle Einstellungen unter "Einstellungen" - "Position und Größe" ausprobiert. Bei manchen Einstellungen ist nur noch 10% des Bildes sichtbar. Steps to Reproduce: 1.Bild einfügen, es wird dabei als "am Zeichen" verankert 2.Verankern: als Zeichen 3. Actual Results: Das Bild wird nur noch teilweise angezeigt. Expected Results: Das Bild bleibt in gleicher Größe und Auswahl sichbar. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156310] Cross reference does not jump to number range
https://bugs.documentfoundation.org/show_bug.cgi?id=156310 --- Comment #11 from dolez...@cvut.cz --- (In reply to sdc.blanco from comment #10) > Please explain. It is possible to select the reference in 7.2, and also use > single-click, so what is the "added functionality"? Wasn't it only possible using keyboard? I don't think right click used to select it, but I might be misremembering. I do remember for certain that I jumped away more than once accidentally when trying to select it, though. > Only if single-click functionality is rejected. Note that single-click > works for other cross-reference types, so I think there must be a good > reason/argument for not having the same single-click functionality for the > number range type. I admit don't know a lot about the other cross reference types, but for what it's worth, hyperlinks and bibliographical references do use Ctrl+Click, so I think there is a case to be made for unification of the command. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158303] LibreOffice not working on 1280x1024 screen
https://bugs.documentfoundation.org/show_bug.cgi?id=158303 --- Comment #3 from updradedsam3...@gmail.com --- I've tried those steps, by default Skia is enabled and changing those settings doesn't fix the issues. The behaviour changes a bit, a lot of flickering with skia off, for example, which is not better. Also updated to 7.6.4.1 and there were no changes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129261] EDITING: Clicking with mouse in CLOB of a form throws "Content has been changed" when closing the form.
https://bugs.documentfoundation.org/show_bug.cgi?id=129261 --- Comment #10 from Alan Wheeler --- Still present on 9 Dec 2023 with LibreOffice 7.6.4 on Windows 11 Version info copied from LibreOffice Help "About" :- Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded It is probably not significant, but the above info specifies Windows 10, whereas LibreOffice was actually installed and run on Windows 11 version 23H2 (OS Build 22631.2715), not Windows 10. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158397] Freeze (beachball) when hoovering with mouse above an animating gif or when opening presentation mode(macOS) with any backend
https://bugs.documentfoundation.org/show_bug.cgi?id=158397 --- Comment #2 from soto ca --- I have always been a fan of chiropractic care. I believe it is a great way to keep your spine healthy. When I heard about the chairs from https://corechair.com/unveiling-the-magic-of-corechair-the-revolutionary-chiropractic-solution-for-back-pain/, I was immediately interested. This chair combines chiropractic principles with modern design. I have been using the CoreChair for several months now and I am very pleased with the results. My back pain is gone and my posture has improved. I feel more energetic and productive. I believe that CoreChair is the best chair for those who want to get rid of back pain and improve their overall health. -- You are receiving this mail because: You are the assignee for the bug.
core.git: i18npool/source
i18npool/source/localedata/data/bn_IN.xml |6 +++---
i18npool/source/localedata/data/hi_IN.xml |6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
New commits:
commit d48ad3187d82aca8d9c35c43698822865cad58a0
Author: Eike Rathke
AuthorDate: Sat Dec 9 12:33:19 2023 +0100
Commit: Eike Rathke
CommitDate: Sat Dec 9 17:19:32 2023 +0100
{bn-IN}{hi-IN} MM-DD-YY DATE_TIME is very likely wrong, all other are
DD-MM-YY
Wrong since its initial commit.
Change-Id: I75214226ef5e1e58798ca0eaf396bad590918ee5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160511
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/i18npool/source/localedata/data/bn_IN.xml
b/i18npool/source/localedata/data/bn_IN.xml
index 7064336deb0a..7de868c0145e 100644
--- a/i18npool/source/localedata/data/bn_IN.xml
+++ b/i18npool/source/localedata/data/bn_IN.xml
@@ -192,13 +192,13 @@
[HH]:MM:SS.00
- MM-DD-YY HH:MM AM/PM
+ DD-MM-YY HH:MM AM/PM
- MM-DD- HH:MM:SS
+ DD-MM- HH:MM:SS
- MM-DD- HH:MM
+ DD-MM- HH:MM
diff --git a/i18npool/source/localedata/data/hi_IN.xml
b/i18npool/source/localedata/data/hi_IN.xml
index 33d27757dd3d..150dbce6e729 100644
--- a/i18npool/source/localedata/data/hi_IN.xml
+++ b/i18npool/source/localedata/data/hi_IN.xml
@@ -190,13 +190,13 @@
[HH]:MM:SS.00
- MM-DD-YY HH:MM
+ DD-MM-YY HH:MM
- MM-DD- HH:MM:SS
+ DD-MM- HH:MM:SS
- MM-DD- HH:MM
+ DD-MM- HH:MM
[Bug 158615] New: Simplify storing of the "zero date" setting in Calc settings
https://bugs.documentfoundation.org/show_bug.cgi?id=158615 Bug ID: 158615 Summary: Simplify storing of the "zero date" setting in Calc settings Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com CC: balazs.varga...@gmail.com This is a followup to bug 158467 The Calc - Calculate - Date setting defines what should be considered the 0 value in date calculations. This setting is stored as a set of 3 keys[1], which is a bit overcomplicated for such a simple 3 state radio button. It would be a somewhat simpler implementation to replace these 3 keys with a single (for example:) ZeroDate key. Code pointers: [1] https://opengrok.libreoffice.org/xref/core/officecfg/registry/schema/org/openoffice/Office/Calc.xcs?r=464d5f12#45 - the keys in question https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/docoptio.cxx?r=14001bc7#155 - the relevant ScDocCfg class -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108800] [META] Print related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108800 Aron Budea changed: What|Removed |Added OS|Windows (All) |All Version|7.6.3.2 release |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158504] "Default Page Style" does not appear as an applied style
https://bugs.documentfoundation.org/show_bug.cgi?id=158504 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #4 from BogdanB --- Tring to bibisect, but getting bogdan@bogdan-IdeaCentre-AIO-3-24ALC6:~/Documente/Bibisect/24.2/linux-64-24.2$ git bisect good && ./instdir/program/soffice Bisecting: 288 revisions left to test after this (roughly 8 steps) [95947107aa8554151ef8834a326dba9886801a14] source sha:252132d9752964a4aa82567b6a3ca8cd7df5ccfb soffice.bin: ../../../../src/cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. soffice.bin: ../../../../src/cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. soffice.bin: ../../../../src/cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. soffice.bin: ../../../../src/cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. And I get crash, and I can not escape from here with a new document in order to bibisect. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108800] [META] Print related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108800 Bug 108800 depends on bug 158379, which changed state. Bug 158379 Summary: Crash when trying to print specific RTF file (macOS) https://bugs.documentfoundation.org/show_bug.cgi?id=158379 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 158379, which changed state. Bug 158379 Summary: Crash when trying to print specific RTF file (macOS) https://bugs.documentfoundation.org/show_bug.cgi?id=158379 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133836] Autofilter enables deselect items automatically when typing a search
https://bugs.documentfoundation.org/show_bug.cgi?id=133836 --- Comment #34 from Sahil Gautam --- Created attachment 191331 --> https://bugs.documentfoundation.org/attachment.cgi?id=191331=edit Comparing the old behaviour to the new behaviour -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 133836] Autofilter enables deselect items automatically when typing a search
https://bugs.documentfoundation.org/show_bug.cgi?id=133836 --- Comment #33 from Sahil Gautam --- Created attachment 191330 --> https://bugs.documentfoundation.org/attachment.cgi?id=191330=edit old behaviour demonstration -- You are receiving this mail because: You are on the CC list for the bug.
core.git: Branch 'distro/mimo/mimo-6-2' - sw/source
sw/source/uibase/wrtsh/wrtsh2.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit c971d1b920ef0cc7b25e0ec71c8d3824e220e3e0
Author: Aron Budea
AuthorDate: Sun Dec 10 00:19:43 2023 +1030
Commit: Aron Budea
CommitDate: Sun Dec 10 00:19:43 2023 +1030
build fix
Change-Id: I68d53a45cf59dac25c4b92ef4c232751f14f6684
diff --git a/sw/source/uibase/wrtsh/wrtsh2.cxx
b/sw/source/uibase/wrtsh/wrtsh2.cxx
index 040830a27107..4c856efab95e 100644
--- a/sw/source/uibase/wrtsh/wrtsh2.cxx
+++ b/sw/source/uibase/wrtsh/wrtsh2.cxx
@@ -495,7 +495,7 @@ static void LoadURL(SwView& rView, const OUString& rURL,
LoadUrlFlags nFilter,
{
// May be the relative link -> try to convert to absolute path
OUString sParentPath =
-
rVSh.GetDoc()->GetDocShell()->GetMedium()->GetURLObject().GetPath();
+rView.GetDocShell()->GetMedium()->GetURLObject().GetPath();
bool bCorrectURL = true;
aURL = INetURLObject();
core.git: Changes to 'feature/cib_contract8161'
New branch 'feature/cib_contract8161' available with the following commits: commit b4208c3c2bd5175da50fbee7ee232daf69a39071 Author: Vasily Melenchuk Date: Wed Oct 25 22:26:14 2023 +0300 vcl: use Windows FlshWindow() feature For improving UX of LibreOffice it will be great to bring attention to it's windows without hard window switch. For example, if dialog window is opening slowly and user did switch to another application this could be a signal to user that there are some updates in LO window. Change-Id: I6ca6706d2dda8902aea273ebe6e318ec9bf4beda
core.git: Branch 'distro/cib/libreoffice-6-4' - sc/source
sc/source/core/data/dociter.cxx |2 ++
1 file changed, 2 insertions(+)
New commits:
commit 8f4df88ad1e3626610588a1e775861ee929e47aa
Author: Noel Grandin
AuthorDate: Wed Feb 3 15:19:20 2021 +0200
Commit: Thorsten Behrens
CommitDate: Sat Dec 9 14:28:40 2023 +0100
tdf#140014 calc crash on COUNTIF
regression from jumbo-sheets work
Change-Id: I207cf3cc4c6d295688936ea3b672b32f9c09d89a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110349
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sc/source/core/data/dociter.cxx b/sc/source/core/data/dociter.cxx
index ed55445d0558..6815b3693ee4 100644
--- a/sc/source/core/data/dociter.cxx
+++ b/sc/source/core/data/dociter.cxx
@@ -1460,6 +1460,8 @@ ScCountIfCellIterator::ScCountIfCellIterator(ScDocument*
pDocument, const ScInte
mrContext( rContext ),
nTab( nTable)
{
+maParam.nCol1 =
rDoc.maTabs[nTable]->ClampToAllocatedColumns(maParam.nCol1);
+maParam.nCol2 =
rDoc.maTabs[nTable]->ClampToAllocatedColumns(maParam.nCol2);
nCol = maParam.nCol1;
nRow = maParam.nRow1;
}
[Bug 133836] Autofilter enables deselect items automatically when typing a search
https://bugs.documentfoundation.org/show_bug.cgi?id=133836 --- Comment #32 from Mike Kaganski --- (In reply to Heiko Tietze from comment #31) Sigh. Could amyone please describe, how this convoluted workflow should be usable? And what would be wrong with a simple "filtering changes selection" checkbox instead? -- You are receiving this mail because: You are on the CC list for the bug.
core.git: 2 commits - sc/source
sc/source/ui/inc/tabvwsh.hxx |2 +-
sc/source/ui/view/tabvwsh4.cxx | 15 ++-
2 files changed, 7 insertions(+), 10 deletions(-)
New commits:
commit 198035a18f28095b868f9e8ecc01c6b139e21896
Author: Mike Kaganski
AuthorDate: Sat Dec 9 12:52:55 2023 +0300
Commit: Mike Kaganski
CommitDate: Sat Dec 9 14:10:28 2023 +0100
Simplify a bit
Change-Id: Ida8ab7b8e39f3847d58813ca93ae705bc19ac2e5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160508
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sc/source/ui/inc/tabvwsh.hxx b/sc/source/ui/inc/tabvwsh.hxx
index dc05f235c990..1b80b0ab2f25 100644
--- a/sc/source/ui/inc/tabvwsh.hxx
+++ b/sc/source/ui/inc/tabvwsh.hxx
@@ -94,8 +94,8 @@ class ScFormEditData;
class ScViewOptiChangesListener;
class SC_DLLPUBLIC ScTabViewShell : public SfxViewShell, public ScDBFunc
{
-rtl::Reference mChangesListener;
private:
+rtl::Reference mChangesListener;
struct SendFormulabarUpdate
{
OUString m_aText;
diff --git a/sc/source/ui/view/tabvwsh4.cxx b/sc/source/ui/view/tabvwsh4.cxx
index 3948a7d07843..2989d63b5f99 100644
--- a/sc/source/ui/view/tabvwsh4.cxx
+++ b/sc/source/ui/view/tabvwsh4.cxx
@@ -1705,7 +1705,7 @@ private:
void ScViewOptiChangesListener::stopListening()
{
-if (m_xChangesNotifier.is())
+if (m_xChangesNotifier)
m_xChangesNotifier->removeChangesListener(this);
}
@@ -1736,19 +1736,16 @@
ScViewOptiChangesListener::ScViewOptiChangesListener(ScTabViewShell& rViewShell)
uno::Reference xConfigurationProvider(
configuration::theDefaultProvider::get(comphelper::getProcessComponentContext()));
-beans::NamedValue aProperty;
-aProperty.Name = "nodepath";
-aProperty.Value <<=
OUString("/org.openoffice.Office.Calc/Content/Display");
-
-uno::Sequence aArgumentList{ uno::Any(aProperty) };
+beans::NamedValue aProperty{ u"nodepath"_ustr,
+
uno::Any(u"/org.openoffice.Office.Calc/Content/Display"_ustr) };
uno::Reference xConfigurationAccess
= xConfigurationProvider->createInstanceWithArguments(
-"com.sun.star.configuration.ConfigurationAccess", aArgumentList);
+"com.sun.star.configuration.ConfigurationAccess", {
uno::Any(aProperty) });
m_xChangesNotifier.set(xConfigurationAccess, uno::UNO_QUERY);
-if (m_xChangesNotifier.is())
+if (m_xChangesNotifier)
m_xChangesNotifier->addChangesListener(this);
}
commit 6aa07b9e2bca206150de7d5d048833cef31b882a
Author: Mike Kaganski
AuthorDate: Sat Dec 9 12:45:15 2023 +0300
Commit: Mike Kaganski
CommitDate: Sat Dec 9 14:10:22 2023 +0100
Listen to the needed subnode
We don't need to know when other subnodes might change
Change-Id: I9bd065a700e4d313acae1064af743a32a537c89c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160507
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sc/source/ui/view/tabvwsh4.cxx b/sc/source/ui/view/tabvwsh4.cxx
index b7258e86e36e..3948a7d07843 100644
--- a/sc/source/ui/view/tabvwsh4.cxx
+++ b/sc/source/ui/view/tabvwsh4.cxx
@@ -1715,7 +1715,7 @@ void SAL_CALL
ScViewOptiChangesListener::changesOccurred(const util::ChangesEven
for (const auto& change : rEvent.Changes)
{
if (OUString sChangedEntry;
-(change.Accessor >>= sChangedEntry) && sChangedEntry ==
"Display/ColumnRowHighlighting")
+(change.Accessor >>= sChangedEntry) && sChangedEntry ==
"ColumnRowHighlighting")
{
mrViewShell.GetViewData().GetView()->HighlightOverlay();
break;
@@ -1738,7 +1738,7 @@
ScViewOptiChangesListener::ScViewOptiChangesListener(ScTabViewShell& rViewShell)
beans::NamedValue aProperty;
aProperty.Name = "nodepath";
-aProperty.Value <<= OUString("/org.openoffice.Office.Calc/Content");
+aProperty.Value <<=
OUString("/org.openoffice.Office.Calc/Content/Display");
uno::Sequence aArgumentList{ uno::Any(aProperty) };
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 --- Comment #2 from Don Matschull --- Currently, if I set up a right hand page style, there is only a choice for Header on. When I create a header on the page in the document using this right hand page style, the cursor goes to the left and the Page Styles area in the Sidebar indicates that the Header paragraph style is being used. I must change this to Header Right in order for the cursor to start at the right. My thought was: It would be a nice enhancement if, when I set up my right hand page style, I could get the header to automatically use the Header Right page style rather than the parent Header page style. I don't know how hard this would be. I just thought I would make the suggestion. I'm always looking for ways to make writing a document more efficient. That is why I like the LibreOffice emphasis on styles and encourage others to use styles rather than direct formatting. Looking at my illustration after reading your comment, I see that the dialog says "Page Style: _My Page Style" rather than "Page Style: _My Right Page" or "Page Style: _My Left Page". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158340] Page Style Header and Footer tabs: Add setting for choosing Header Right/Left Footer Right/Left
https://bugs.documentfoundation.org/show_bug.cgi?id=158340 --- Comment #2 from Don Matschull --- Currently, if I set up a right hand page style, there is only a choice for Header on. When I create a header on the page in the document using this right hand page style, the cursor goes to the left and the Page Styles area in the Sidebar indicates that the Header paragraph style is being used. I must change this to Header Right in order for the cursor to start at the right. My thought was: It would be a nice enhancement if, when I set up my right hand page style, I could get the header to automatically use the Header Right page style rather than the parent Header page style. I don't know how hard this would be. I just thought I would make the suggestion. I'm always looking for ways to make writing a document more efficient. That is why I like the LibreOffice emphasis on styles and encourage others to use styles rather than direct formatting. Looking at my illustration after reading your comment, I see that the dialog says "Page Style: _My Page Style" rather than "Page Style: _My Right Page" or "Page Style: _My Left Page". -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #10 from Mike Kaganski --- (In reply to ady from comment #8) > If we talk about seeing related data, Calc lacks the (basic) possibility of > tracing precedents (and dependents) on cells located on other worksheets > (tdf#63087); that's much more relevant and much more useful regarding > related data IMO. Additionally, this is a *wrong* idea. Tracking precedents / dependents is completely orthogonal to the basic idea of tables as structured representation of data: precedents / dependents allow to *build* the data, but not to *use* it - because table represents records, with came type of data in each record in the same position; each record having different data belonging to the same entity. Seeing different pieces belonging to the same entity; or same data of different entities - is the most important aspect of *tabular* representation. Comapring apples to oranges, and calling aspects of *creating* tables "much more useful" than aspects of *using* tables is counter-productive. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #10 from Mike Kaganski --- (In reply to ady from comment #8) > If we talk about seeing related data, Calc lacks the (basic) possibility of > tracing precedents (and dependents) on cells located on other worksheets > (tdf#63087); that's much more relevant and much more useful regarding > related data IMO. Additionally, this is a *wrong* idea. Tracking precedents / dependents is completely orthogonal to the basic idea of tables as structured representation of data: precedents / dependents allow to *build* the data, but not to *use* it - because table represents records, with came type of data in each record in the same position; each record having different data belonging to the same entity. Seeing different pieces belonging to the same entity; or same data of different entities - is the most important aspect of *tabular* representation. Comapring apples to oranges, and calling aspects of *creating* tables "much more useful" than aspects of *using* tables is counter-productive. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #9 from Mike Kaganski --- (In reply to ady from comment #8) > Highlighting is useful for contrast, to bring attention to some area. Too > much different highlighted areas would beat the goal, and can even be > counterproductive. Highlight is useful for whatever is useful for a user who enables the feature. Multiselection is not a topic here yet, given that my wording was "with a limitation of only simple case"; for simple case, there will be no more "different highlighted areas" than with current implementation - only size of the areas will be different. > If we talk about seeing related data, Calc lacks the (basic) possibility of > tracing precedents (and dependents) on cells located on other worksheets > (tdf#63087); that's much more relevant and much more useful regarding > related data IMO. This is completely irrelevant. Please avoid such a bad thing as "let's not do something that some person can easily do, just because I thikk there is also another possible related improvement, not necessarily as easy or suitable for the person who implemented *this* feature". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #9 from Mike Kaganski --- (In reply to ady from comment #8) > Highlighting is useful for contrast, to bring attention to some area. Too > much different highlighted areas would beat the goal, and can even be > counterproductive. Highlight is useful for whatever is useful for a user who enables the feature. Multiselection is not a topic here yet, given that my wording was "with a limitation of only simple case"; for simple case, there will be no more "different highlighted areas" than with current implementation - only size of the areas will be different. > If we talk about seeing related data, Calc lacks the (basic) possibility of > tracing precedents (and dependents) on cells located on other worksheets > (tdf#63087); that's much more relevant and much more useful regarding > related data IMO. This is completely irrelevant. Please avoid such a bad thing as "let's not do something that some person can easily do, just because I thikk there is also another possible related improvement, not necessarily as easy or suitable for the person who implemented *this* feature". -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 156310] Cross reference does not jump to number range
https://bugs.documentfoundation.org/show_bug.cgi?id=156310 --- Comment #10 from sdc.bla...@youmail.dk --- (In reply to dolezvo1 from comment #9) > However, the added functionality of being able to select the reference > is actually nice, imo. Please explain. It is possible to select the reference in 7.2, and also use single-click, so what is the "added functionality"? > Would it be a valid solution to show a hint that you > should use Ctrl+Click to jump to the target, like it happens with similar > elements? Only if single-click functionality is rejected. Note that single-click works for other cross-reference types, so I think there must be a good reason/argument for not having the same single-click functionality for the number range type. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #8 from ady --- (In reply to Mike Kaganski from comment #7) > And the "see the related data" is a good reason to implement Roman's > proposal Highlighting is useful for contrast, to bring attention to some area. Too much different highlighted areas would beat the goal, and can even be counterproductive. If we talk about seeing related data, Calc lacks the (basic) possibility of tracing precedents (and dependents) on cells located on other worksheets (tdf#63087); that's much more relevant and much more useful regarding related data IMO. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158587] Improve column/row highlighting in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158587 --- Comment #8 from ady --- (In reply to Mike Kaganski from comment #7) > And the "see the related data" is a good reason to implement Roman's > proposal Highlighting is useful for contrast, to bring attention to some area. Too much different highlighted areas would beat the goal, and can even be counterproductive. If we talk about seeing related data, Calc lacks the (basic) possibility of tracing precedents (and dependents) on cells located on other worksheets (tdf#63087); that's much more relevant and much more useful regarding related data IMO. -- You are receiving this mail because: You are on the CC list for the bug.
