[Libreoffice-commits] core.git: sw/source
sw/source/core/inc/unoflatpara.hxx |3 --- sw/source/core/unocore/unoflatpara.cxx |6 -- 2 files changed, 9 deletions(-) New commits: commit a7ce722b476c4bb0c9a113ae0c2759181edfe48f Author: Mike Kaganski AuthorDate: Fri May 12 23:05:33 2023 +0300 Commit: Mike Kaganski CommitDate: Sat May 13 07:23:36 2023 +0200 tdf#155232: drop m_aFlatParaList from SwXFlatParagraphIterator There is no need to keep those references. The set was there from the beginning, introduced in commits 677eba2322d2753951024c688d59553182bf2fbd (INTEGRATION: CWS gcframework_DEV300 (1.1.2); FILE ADDED, 2008-02-26) and ba76230f6f64b0d333da946a7e487acbeb0b (INTEGRATION: CWS gcframework_DEV300 (1.1.2); FILE ADDED, 2008-02-26). Change-Id: Iaf2482adb0aac063ad106c4198baf74577a75bf4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151712 Tested-by: Jenkins Reviewed-by: Mike Kaganski diff --git a/sw/source/core/inc/unoflatpara.hxx b/sw/source/core/inc/unoflatpara.hxx index 1d68a7d1c8db..77e07af399b9 100644 --- a/sw/source/core/inc/unoflatpara.hxx +++ b/sw/source/core/inc/unoflatpara.hxx @@ -124,9 +124,6 @@ private: SwXFlatParagraphIterator( const SwXFlatParagraphIterator & ) = delete; SwXFlatParagraphIterator & operator =(const SwXFlatParagraphIterator & ) = delete; -// container to hold the 'hard' references as long as necessary and valid -std::set< css::uno::Reference< css::text::XFlatParagraph > > m_aFlatParaList; - SwDoc* mpDoc; const sal_Int32 mnType; const bool mbAutomatic; diff --git a/sw/source/core/unocore/unoflatpara.cxx b/sw/source/core/unocore/unoflatpara.cxx index 94adf66e08b6..c5c2ef94e441 100644 --- a/sw/source/core/unocore/unoflatpara.cxx +++ b/sw/source/core/unocore/unoflatpara.cxx @@ -485,8 +485,6 @@ uno::Reference< text::XFlatParagraph > SwXFlatParagraphIterator::getNextPara() const OUString& aExpandText = aConversionMap.getViewText(); xRet = new SwXFlatParagraph( *pRet, aExpandText, aConversionMap ); -// keep hard references... -m_aFlatParaList.insert( xRet ); } return xRet; @@ -533,8 +531,6 @@ uno::Reference< text::XFlatParagraph > SwXFlatParagraphIterator::getParaAfter(co const OUString& aExpandText = aConversionMap.getViewText(); xRet = new SwXFlatParagraph( *pNextTextNode, aExpandText, aConversionMap ); -// keep hard references... -m_aFlatParaList.insert( xRet ); } return xRet; @@ -576,8 +572,6 @@ uno::Reference< text::XFlatParagraph > SwXFlatParagraphIterator::getParaBefore(c const OUString& aExpandText = aConversionMap.getViewText(); xRet = new SwXFlatParagraph( *pPrevTextNode, aExpandText, aConversionMap ); -// keep hard references... -m_aFlatParaList.insert( xRet ); } return xRet;
[Libreoffice-bugs] [Bug 155273] New: Immediate crash when I open any .docx file and inability to directly open file
https://bugs.documentfoundation.org/show_bug.cgi?id=155273 Bug ID: 155273 Summary: Immediate crash when I open any .docx file and inability to directly open file Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sc07...@georgiasouthern.edu Description: LibreOffice immediately crashes upon opening a file; I am unable to edit, let alone view, any file. This occurs with .docx and other file extensions; I have not found a file extension that doesn't fail. I have removed all the configuration files, reinstalled LibreOffice, and tried once more, but there is still failure. System is running Debian Bookworm 12 with KDE as the desktop environment. Kernel version is 6.0.0.0 and it occurs in 6.1.0.7 as well. Libreoffice was installed through the packages in the repository [libreoffice-kde]. It fails even when running safe mode using the "libreoffice --safe-mode" command in terminal. The terminal output upon failure is present in "Other Information" Steps to Reproduce: 1.Open LibreOffice/LibreOffice Writer 2.Select Open under the File taskbar tab 3.Select desired file and open Actual Results: Immediate crash and closing of LibreOffice Expected Results: Selected file contents are displayed and are available to be edit Reproducible: Always User Profile Reset: Yes Additional Info: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc terminate called recursively Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x376b2)[0x7fa2fbf9b6b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3788a)[0x7fa2fbf9b88a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bf90)[0x7fa2f7a5af90] /lib/x86_64-linux-gnu/libc.so.6(+0x8accc)[0x7fa2f7aa9ccc] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x12)[0x7fa2f7a5aef2] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7fa2f7a45472] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xaae9a)[0x7fa2f78aae9a] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7fa2f78a8e1a] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa7e89)[0x7fa2f78a7e89] /lib/x86_64-linux-gnu/libstdc++.so.6(__gxx_personality_v0+0x86)[0x7fa2f78a85a6] /lib/x86_64-linux-gnu/libgcc_s.so.1(+0x16934)[0x7fa2fbf17934] /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Resume+0x12d)[0x7fa2fbf1838d] /usr/lib/libreoffice/program/libmergedlo.so(+0xff09eb)[0x7fa2f8bf09eb] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x377d2)[0x7fa2fbf9b7d2] /lib/x86_64-linux-gnu/libc.so.6(+0x3bf90)[0x7fa2f7a5af90] /lib/x86_64-linux-gnu/libc.so.6(+0x8accc)[0x7fa2f7aa9ccc] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x12)[0x7fa2f7a5aef2] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7fa2f7a45472] /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d919)[0x7fa2f789d919] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7fa2f78a8e1a] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7fa2f78a8e85] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7fa2f78a90d8] /usr/lib/libreoffice/program/libpyuno.so(+0x927f)[0x7fa2eb61b27f] /usr/lib/libreoffice/program/libpyuno.so(+0x9284)[0x7fa2eb61b284] /usr/lib/libreoffice/program/libpyuno.so(_ZNK5pyuno7Runtime19extractUnoExceptionERKNS_5PyRefES3_S3_+0x541)[0x7fa2eb629c01] /usr/lib/libreoffice/program/libpythonloaderlo.so(pyuno_Loader_get_implementation+0x1be)[0x7fa2f04d000e] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5ded2)[0x7fa2f5823ed2] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5e438)[0x7fa2f5824438] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5e4c0)[0x7fa2f58244c0] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5f7a9)[0x7fa2f58257a9] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x6016c)[0x7fa2f582616c] /usr/lib/libreoffice/program/libmergedlo.so(+0x19d17da)[0x7fa2f95d17da] /usr/lib/libreoffice/program/libmergedlo.so(+0x19d36d7)[0x7fa2f95d36d7] /usr/lib/libreoffice/program/libmergedlo.so(+0x19db82e)[0x7fa2f95db82e] /usr/lib/libreoffice/program/libmergedlo.so(+0x19e6ae9)[0x7fa2f95e6ae9] /usr/lib/libreoffice/program/libmergedlo.so(linguistic_LngSvcMgr_get_implementation+0x38a)[0x7fa2f95ed08a] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5ded2)[0x7fa2f5823ed2] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5e438)[0x7fa2f5824438] /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3(+0x5e4c0)[0x7fa2f58244c0] /usr/lib/libreoffice/program/libswlo.so(_ZN8SwModuleC2EP16SfxObjectFactoryS1_S1_+0x55c)[0x7fa2e956a58c] /usr/lib/libreoffice/program/libswlo.so(+0xdee5d4)[0x7fa2e97ee5d4] /usr/lib/libreoffice/program/libswlo.so(_ZN9SwGlobals6ensureEv+0x35)[0x7fa2e9558ee5] /usr/lib/libreoffice/program/libswlo.so(Writer_SwTextDocument_get_implementation+0x38)[0x7fa2e97090b8]
[Libreoffice-bugs] [Bug 143223] Tab key have no effect just after copy/paste one cell to another
https://bugs.documentfoundation.org/show_bug.cgi?id=143223 BogdanB changed: What|Removed |Added Resolution|WORKSFORME |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 BogdanB changed: What|Removed |Added Depends on|143223 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143223 [Bug 143223] Tab key have no effect just after copy/paste one cell to another -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143223] Tab key have no effect just after copy/paste one cell to another
https://bugs.documentfoundation.org/show_bug.cgi?id=143223 BogdanB changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME Blocks|102593 | --- Comment #5 from BogdanB --- Not a bug, based on comment 4. Indeed, using selection and TAB could be very useful. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102593 [Bug 102593] [META] Paste bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85184 BogdanB changed: What|Removed |Added Depends on||142962 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142962 [Bug 142962] The text color button resets to it's default color when entering and exiting textboxes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142962] The text color button resets to it's default color when entering and exiting textboxes
https://bugs.documentfoundation.org/show_bug.cgi?id=142962 BogdanB changed: What|Removed |Added Blocks||85184 CC||buzea.bog...@libreoffice.or ||g --- Comment #2 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85184 [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137340] Line textbox opening at the wrong place when rotated 180 degrees
https://bugs.documentfoundation.org/show_bug.cgi?id=137340 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||122886 --- Comment #5 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122886 [Bug 122886] [META] Bugs with textboxes in shapes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122886] [META] Bugs with textboxes in shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=122886 BogdanB changed: What|Removed |Added Depends on||137340 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137340 [Bug 137340] Line textbox opening at the wrong place when rotated 180 degrees -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123823] Feature request: Show positioning guide assistance in Draw (UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=123823 BogdanB changed: What|Removed |Added Blocks||100023 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100023 [Bug 100023] [META] Enhance Draw's user experience -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100023] [META] Enhance Draw's user experience
https://bugs.documentfoundation.org/show_bug.cgi?id=100023 BogdanB changed: What|Removed |Added Depends on||123823 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=123823 [Bug 123823] Feature request: Show positioning guide assistance in Draw (UI) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 155246, which changed state. Bug 155246 Summary: Undocking sidebar crashing https://bugs.documentfoundation.org/show_bug.cgi?id=155246 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155246] Undocking sidebar crashing
https://bugs.documentfoundation.org/show_bug.cgi?id=155246 Elmar changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Elmar --- I can explain Now, LO starts, no problem. Will re-open bug if it occurs again. May have had something to do with main SSD failing and having to re-install from scratch. Previously it worked fine in v7.3.7.2 (default for Linux Mint Cinnamon 21.1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122859] Unable to remove size protection of formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=122859 BogdanB changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3812 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135859] [META] Formula-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=135859 BogdanB changed: What|Removed |Added Depends on||143812 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143812 [Bug 143812] Can't modify the size of the equation window when inserting an equation in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143812] Can't modify the size of the equation window when inserting an equation in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=143812 BogdanB changed: What|Removed |Added OS|Windows (All) |All See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2859 Blocks||135859 CC||buzea.bog...@libreoffice.or ||g --- Comment #2 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135859 [Bug 135859] [META] Formula-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108254] [META] File format filters (import/export) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108254 BogdanB changed: What|Removed |Added Depends on||143715 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143715 [Bug 143715] FILEOPEN DBF timestamp fields (type '@') trigger corruption error -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143715] FILEOPEN DBF timestamp fields (type '@') trigger corruption error
https://bugs.documentfoundation.org/show_bug.cgi?id=143715 BogdanB changed: What|Removed |Added Blocks||108254 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108254 [Bug 108254] [META] File format filters (import/export) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107838] [META] Character-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107838 BogdanB changed: What|Removed |Added Depends on||140125 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140125 [Bug 140125] character border implementation issues vs. Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140125] character border implementation issues vs. Word
https://bugs.documentfoundation.org/show_bug.cgi?id=140125 BogdanB changed: What|Removed |Added Blocks||107838 CC||buzea.bog...@libreoffice.or ||g --- Comment #5 from BogdanB --- Michael, could you attach a screenshot from Word? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107838 [Bug 107838] [META] Character-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108519] [META] Page break bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108519 BogdanB changed: What|Removed |Added Depends on||143753 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143753 [Bug 143753] Fontwork insert on the wrong page (before page break instead of after) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107634] [META] Fontwork / WordArt bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107634 BogdanB changed: What|Removed |Added Depends on||143753 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143753 [Bug 143753] Fontwork insert on the wrong page (before page break instead of after) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143753] Fontwork insert on the wrong page (before page break instead of after)
https://bugs.documentfoundation.org/show_bug.cgi?id=143753 BogdanB changed: What|Removed |Added Blocks||107634, 108519 --- Comment #3 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107634 [Bug 107634] [META] Fontwork / WordArt bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108519 [Bug 108519] [META] Page break bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148251] Use std::swap instead of using temporary values
https://bugs.documentfoundation.org/show_bug.cgi?id=148251 --- Comment #9 from Commit Notification --- Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/389b801cea9c9f3c311dcbe9d32df62a66e5ea4a tdf#148251 qt: Use std::swap instead of using temporary values It will be available in 7.6.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-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 BogdanB changed: What|Removed |Added Depends on||143836 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143836 [Bug 143836] Arrow up changes spacing between text below and image (as character). Arrow down or undo doesn't revert this -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143836] Arrow up changes spacing between text below and image (as character). Arrow down or undo doesn't revert this
https://bugs.documentfoundation.org/show_bug.cgi?id=143836 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103152 --- Comment #3 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/qt5
vcl/qt5/QtGraphics_GDI.cxx | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
New commits:
commit 389b801cea9c9f3c311dcbe9d32df62a66e5ea4a
Author: Dr. David Alan Gilbert
AuthorDate: Wed May 10 23:55:14 2023 +0100
Commit: Michael Weghorn
CommitDate: Sat May 13 06:36:47 2023 +0200
tdf#148251 qt: Use std::swap instead of using temporary values
Another std::swap case in drawLine
Change-Id: I207fe3c8c6c88532c23faf3aa3188acdcda3a5b8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151654
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/vcl/qt5/QtGraphics_GDI.cxx b/vcl/qt5/QtGraphics_GDI.cxx
index 08116f85a529..28bab34a7cca 100644
--- a/vcl/qt5/QtGraphics_GDI.cxx
+++ b/vcl/qt5/QtGraphics_GDI.cxx
@@ -198,19 +198,10 @@ void QtGraphicsBackend::drawLine(tools::Long nX1,
tools::Long nY1, tools::Long n
QtPainter aPainter(*this);
aPainter.drawLine(nX1, nY1, nX2, nY2);
-tools::Long tmp;
if (nX1 > nX2)
-{
-tmp = nX1;
-nX1 = nX2;
-nX2 = tmp;
-}
+std::swap(nX1, nX2);
if (nY1 > nY2)
-{
-tmp = nY1;
-nY1 = nY2;
-nY2 = tmp;
-}
+std::swap(nY1, nY2);
aPainter.update(nX1, nY1, nX2 - nX1 + 1, nY2 - nY1 + 1);
}
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 BogdanB changed: What|Removed |Added Depends on||143606 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143606 [Bug 143606] Write Navigator no longer remembers 2nd monitor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143606] Write Navigator no longer remembers 2nd monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=143606 BogdanB changed: What|Removed |Added Blocks||103030 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59284] [META] Calc cell border related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=59284 BogdanB changed: What|Removed |Added Depends on||143839 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143839 [Bug 143839] Border removed after merge cells -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143839] Border removed after merge cells
https://bugs.documentfoundation.org/show_bug.cgi?id=143839 BogdanB changed: What|Removed |Added Summary|Merge cell |Border removed after merge ||cells OS|Windows (All) |All Blocks||59284 CC||buzea.bog...@libreoffice.or ||g --- Comment #2 from BogdanB --- Repro in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=59284 [Bug 59284] [META] Calc cell border related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107707] [META] Writer table enhancements requests
https://bugs.documentfoundation.org/show_bug.cgi?id=107707 BogdanB changed: What|Removed |Added Depends on||143848 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143848 [Bug 143848] Table boundaries keeps lines black (when set to Automatic) when document background is set to black -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143848] Table boundaries keeps lines black (when set to Automatic) when document background is set to black
https://bugs.documentfoundation.org/show_bug.cgi?id=143848 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107707 Summary|Auto table boundaries keeps |Table boundaries keeps |lines black when doc|lines black (when set to |background set to black.|Automatic) when document ||background is set to black OS|Windows (All) |All --- Comment #2 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107707 [Bug 107707] [META] Writer table enhancements requests -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154930] In a Dialog screen, TextFields, NumberFields and Datefields are appearing badly.
https://bugs.documentfoundation.org/show_bug.cgi?id=154930 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 138206] windows are unfocused when they open
https://bugs.documentfoundation.org/show_bug.cgi?id=138206 --- Comment #18 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154930] In a Dialog screen, TextFields, NumberFields and Datefields are appearing badly.
https://bugs.documentfoundation.org/show_bug.cgi?id=154930 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138206] windows are unfocused when they open
https://bugs.documentfoundation.org/show_bug.cgi?id=138206 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 151506] Impress - record gradient colour does not record automatic filling option
https://bugs.documentfoundation.org/show_bug.cgi?id=151506 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 151506] Impress - record gradient colour does not record automatic filling option
https://bugs.documentfoundation.org/show_bug.cgi?id=151506 --- Comment #3 from QA Administrators --- Dear philippe, 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 150228] Libre office freezes and then completely shuts down
https://bugs.documentfoundation.org/show_bug.cgi?id=150228 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 145649] Copy-paste 323 columns chrome/mozilla: corrupted result
https://bugs.documentfoundation.org/show_bug.cgi?id=145649 --- Comment #9 from QA Administrators --- Dear tim, 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 150228] Libre office freezes and then completely shuts down
https://bugs.documentfoundation.org/show_bug.cgi?id=150228 --- Comment #4 from QA Administrators --- Dear lstoker, 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 141415] DOC: FILEOPEN: Very slow document opening (2-5min instead of 20sec)
https://bugs.documentfoundation.org/show_bug.cgi?id=141415 --- Comment #10 from QA Administrators --- Dear Igor D., 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 128583] Can not paste Picture (Windows Metafile) but MS Word can
https://bugs.documentfoundation.org/show_bug.cgi?id=128583 --- Comment #22 from QA Administrators --- Dear Ferry Toth, 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 119933] Slower file-opening and dump with ODT file
https://bugs.documentfoundation.org/show_bug.cgi?id=119933 --- Comment #14 from QA Administrators --- Dear Telesto, 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 113738] Drawing elements are EXTREMELY slow to open
https://bugs.documentfoundation.org/show_bug.cgi?id=113738 --- Comment #13 from QA Administrators --- Dear Timur Davletshin, 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 51613] FILESAVE: Saving Mean Value Lines in XLS/X format not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=51613 --- Comment #15 from QA Administrators --- Dear Cornelius, 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 55204] FILEOPEN PPTX: Position and precision of trendline equation in chart displayed incorrectly (comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=55204 --- Comment #12 from QA Administrators --- Dear spasmous, 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 81012] FORMATTING: Wrong chapter title in running header/footer after the first page of endnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=81012 --- Comment #18 from QA Administrators --- Dear Kartik Subbarao, 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 142218] FILEOPEN PPTX Header/footer settings of Handouts/Notes not read correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=142218 --- Comment #3 from QA Administrators --- Dear NISZ LibreOffice Team, 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 142206] [EMF] WidenPath support
https://bugs.documentfoundation.org/show_bug.cgi?id=142206 --- Comment #13 from QA Administrators --- Dear Valek Filippov, 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 141939] Undo/undo insertion of caption frame moves a shape to all corners of the page
https://bugs.documentfoundation.org/show_bug.cgi?id=141939 --- Comment #5 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 132277] Shapes not properly placed after undoing change of anchor from "To character" to "As character"
https://bugs.documentfoundation.org/show_bug.cgi?id=132277 --- Comment #5 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 124554] FORMATTING Text colour change on pdf export of Impress presentation based on new master slide with dark background
https://bugs.documentfoundation.org/show_bug.cgi?id=124554 --- Comment #7 from QA Administrators --- Dear Colin S, 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 107423] Contextual groups variant of the Notebookbar is supposed to work with main menu and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=107423 --- Comment #7 from QA Administrators --- Dear Heiko Tietze, 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 106130] incorrect/faulty comment position for OOXML documents
https://bugs.documentfoundation.org/show_bug.cgi?id=106130 --- Comment #5 from QA Administrators --- Dear Pranav Kant, 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 138453] TABLE STYLE: can't be turned off because there is no "OFF" option
https://bugs.documentfoundation.org/show_bug.cgi?id=138453 --- Comment #9 from Jim Raykowski --- So do I have this right, what is wanted is a way to simply turn table formatting off, not to reset formatting that has been made to the table? For example, a table is inserted with the 'Box List Blue' style, then 'No Table Style' is double clicked in the table styles list, nothing noticeable happens to the table other than the style is now shown as 'No Table Style'. When the table has 'No Table Style', no automatic formatting is applied when new rows or columns are added to the table. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138206] windows are unfocused when they open
https://bugs.documentfoundation.org/show_bug.cgi?id=138206 --- Comment #17 from Scott --- Hi all, The issue has not changed. I'm still using Ubuntu 20.04. The problem remained after my last reinstallation in the fall of 2021. I've continued to rely on my workaround of focusing windows whenever I hover over them. That's working well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155272] New: Writer: Very bad import/display of .docx Microsoft Word file
https://bugs.documentfoundation.org/show_bug.cgi?id=155272 Bug ID: 155272 Summary: Writer: Very bad import/display of .docx Microsoft Word file Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gerry.trep...@googlemail.com Created attachment 187237 --> https://bugs.documentfoundation.org/attachment.cgi?id=187237=edit This is how the .docx file looks (correctly) in MS Word The following .docx Microsoft Word file is imported/displayed absolutely incorrectly in LibreOffice Writer. The layout is completely wrong and most of the text is missing: https://vergabe.niedersachsen.de/Satellite/public/company/project/CXTMYYDYRHF/de/documents/misc/VVB+236+-+Verplichtungserklaerung+anderer+Unternehmen+12-2017.docx System: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu package version: 4:7.5.2-0ubuntu1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138139] FILEOPEN DOCX Empty paragraph with only page break has its border from style drawn
https://bugs.documentfoundation.org/show_bug.cgi?id=138139 --- Comment #4 from Justin L --- Created attachment 187236 --> https://bugs.documentfoundation.org/attachment.cgi?id=187236=edit emptypara-skippedNumbering.docx: even numbering is not shown repro 7.6+ compatibilityMode 15, but does the same thing in Word 2010. And look at this: the "invisible" heading line even ignores numbering while still being affected by it. (At least in Word 2010 this has headings 1. and 3.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108769] [META] DOCX (OOXML) character-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108769 Bug 108769 depends on bug 130363, which changed state. Bug 130363 Summary: FILESAVE DOCX character padded border highlight fill incomplete at end-of-line https://bugs.documentfoundation.org/show_bug.cgi?id=130363 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130363] FILESAVE DOCX character padded border highlight fill incomplete at end-of-line
https://bugs.documentfoundation.org/show_bug.cgi?id=130363 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130363] FILESAVE DOCX character padded border highlight fill incomplete at end-of-line
https://bugs.documentfoundation.org/show_bug.cgi?id=130363 --- Comment #9 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b5a22fceed57f05eb43a5fb0817afbc141610c5e tdf#130363 sw layout: MS Word compatibility trailing blanks option part 4 It will be available in 7.6.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: sw/source
sw/source/core/text/inftxt.cxx |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
New commits:
commit b5a22fceed57f05eb43a5fb0817afbc141610c5e
Author: Justin Luth
AuthorDate: Fri May 12 14:47:54 2023 -0400
Commit: Justin Luth
CommitDate: Sat May 13 02:21:51 2023 +0200
tdf#130363 sw layout: MS Word compatibility trailing blanks option part 4
There are also margins to be considered.
Granted, the previous approach DID seem to get the right width,
since MS Word doesn't paint the left border spacing either.
However, since the existing situation doesn't cover that case,
just remove the excess amount.
Although not perfect (and this whole thing is a total hack,
so perfection can hardly be expected)
it is better than before.
Change-Id: I9dd1e801d8fede020d59c7463138e2ad9f6f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151716
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/source/core/text/inftxt.cxx b/sw/source/core/text/inftxt.cxx
index dcb1657d2801..dd436e0358c6 100644
--- a/sw/source/core/text/inftxt.cxx
+++ b/sw/source/core/text/inftxt.cxx
@@ -1259,11 +1259,10 @@ void SwTextPaintInfo::DrawBackBrush( const
SwLinePortion ) const
if (GetText()[i] != CH_BLANK)
{
const sal_uInt16 nOldWidth = rPor.Width();
-const sal_uInt16 nNewWidth
-= GetTextSize(m_pOut, nullptr, GetText(), GetIdx(),
- TextFrameIndex(i + 1) -
GetIdx()).Width();
-
-const_cast(rPor).Width( nNewWidth );
+const sal_uInt16 nExcessWidth
+= GetTextSize(m_pOut, nullptr, GetText(),
TextFrameIndex(i + 1),
+ TextFrameIndex(nLastPos -
i)).Width();
+const_cast(rPor).Width(nOldWidth -
nExcessWidth);
CalcRect( rPor, nullptr, , true );
const_cast(rPor).Width( nOldWidth );
[Libreoffice-bugs] [Bug 130363] FILESAVE DOCX character padded border highlight fill incomplete at end-of-line
https://bugs.documentfoundation.org/show_bug.cgi?id=130363 --- Comment #8 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/06824845cc0a1b48d87554091bcac5aad8d60b4a NFC tdf#130363 sw layout: cleanup MS Word compatibility trailing blanks It will be available in 7.6.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-bugs] [Bug 130363] FILESAVE DOCX character padded border highlight fill incomplete at end-of-line
https://bugs.documentfoundation.org/show_bug.cgi?id=130363 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/text/inftxt.cxx | 56 ++---
1 file changed, 20 insertions(+), 36 deletions(-)
New commits:
commit 06824845cc0a1b48d87554091bcac5aad8d60b4a
Author: Justin Luth
AuthorDate: Fri May 12 15:40:54 2023 -0400
Commit: Justin Luth
CommitDate: Sat May 13 02:18:51 2023 +0200
NFC tdf#130363 sw layout: cleanup MS Word compatibility trailing blanks
Cleaning up the code separately so my change can be better understood.
Change-Id: Ib756eb8c86f0c515056fba3e9af61cf645a19365
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151715
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/source/core/text/inftxt.cxx b/sw/source/core/text/inftxt.cxx
index 895d2aba2dd7..dcb1657d2801 100644
--- a/sw/source/core/text/inftxt.cxx
+++ b/sw/source/core/text/inftxt.cxx
@@ -1216,35 +1216,30 @@ void SwTextPaintInfo::DrawBackBrush( const
SwLinePortion ) const
{
bool draw = false;
bool full = false;
-SwLinePortion *pPos = const_cast();
+const sal_Int32 nMaxLen = GetText().getLength();
+const sal_Int32 nCurrPorEnd(GetIdx() + rPor.GetLen());
+const SwLinePortion* pPos =
TextFrameIndex nIdx = GetIdx();
-TextFrameIndex nLen;
do
{
-nLen = pPos->GetLen();
-for (TextFrameIndex i = nIdx; i < (nIdx + nLen); ++i)
+const sal_Int32 nEndPos = std::min(sal_Int32(nIdx +
pPos->GetLen()), nMaxLen);
+for (sal_Int32 i = sal_Int32(nIdx); i < nEndPos; ++i)
{
-if (i < TextFrameIndex(GetText().getLength())
-&& GetText()[sal_Int32(i)] == CH_TXTATR_NEWLINE)
-{
-if ( i >= (GetIdx() + rPor.GetLen()) )
-{
-goto drawcontinue;
-}
-}
-if (i >= TextFrameIndex(GetText().getLength())
-|| GetText()[sal_Int32(i)] != CH_BLANK)
+if (i < nMaxLen && i >= nCurrPorEnd && GetText()[i] ==
CH_TXTATR_NEWLINE)
+goto drawcontinue;
+
+if (i == nMaxLen || GetText()[i] != CH_BLANK)
{
draw = true;
-if ( i >= (GetIdx() + rPor.GetLen()) )
+if (i >= nCurrPorEnd)
{
full = true;
goto drawcontinue;
}
}
}
-nIdx += nLen;
+nIdx += pPos->GetLen();
pPos = pPos->GetNextPortion();
} while ( pPos );
@@ -1255,36 +1250,25 @@ void SwTextPaintInfo::DrawBackBrush( const
SwLinePortion ) const
if ( !full )
{
-pPos = const_cast();
-nIdx = GetIdx();
-
-nLen = pPos->GetLen();
-for (TextFrameIndex i = nIdx + nLen - TextFrameIndex(1);
-i >= nIdx; --i)
+const sal_Int32 nLastPos = std::min(nCurrPorEnd, nMaxLen) - 1;
+for (sal_Int32 i = nLastPos; TextFrameIndex(i) >= GetIdx();
--i)
{
-if (i < TextFrameIndex(GetText().getLength())
-&& GetText()[sal_Int32(i)] == CH_TXTATR_NEWLINE)
-{
+if (GetText()[i] == CH_TXTATR_NEWLINE)
continue;
-}
-if ((i + TextFrameIndex(1) ).get() > GetText().getLength())
-// prevent crash by not passing bad data down to
GetTextSize->SwDrawTextInfo
-SAL_WARN("sw", "something dodgy, clamping text index
to prevent crash");
-else if (i >= TextFrameIndex(GetText().getLength())
-|| GetText()[sal_Int32(i)] != CH_BLANK)
+
+if (GetText()[i] != CH_BLANK)
{
-sal_uInt16 nOldWidth = rPor.Width();
-sal_uInt16 nNewWidth = GetTextSize(m_pOut, nullptr,
-GetText(), nIdx, (i + TextFrameIndex(1) -
nIdx)).Width();
+const sal_uInt16 nOldWidth = rPor.Width();
+const sal_uInt16 nNewWidth
+= GetTextSize(m_pOut, nullptr, GetText(), GetIdx(),
+ TextFrameIndex(i + 1) -
GetIdx()).Width();
const_cast(rPor).Width( nNewWidth );
CalcRect( rPor, nullptr, , true );
const_cast(rPor).Width( nOldWidth );
if ( !aIntersect.HasArea() )
-{
[Libreoffice-bugs] [Bug 155271] New: The attribute drawooo:display is missing in libreoffice rng -file
https://bugs.documentfoundation.org/show_bug.cgi?id=155271 Bug ID: 155271 Summary: The attribute drawooo:display is missing in libreoffice rng -file Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de The attribute drawooo:display is missing in file OpenDocument-v1.3+libreoffice-schema.rng. Thus validation fails for documents which contain this attribute. This affects especially unit tests with 'saveAndReload' method. Such unit tests have now the 'SkipValidation' workaround. The attribute was introduced with https://git.libreoffice.org/core/commit/33ef17ed7207b82d8e6fe1fa4ddaec676092d0f1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135762] Export all sheets as CSV
https://bugs.documentfoundation.org/show_bug.cgi?id=135762 --- Comment #25 from Jim Avera --- Sorry, wrong docs url, should have said https://wiki.documentfoundation.org/Documentation/DevGuide/Spreadsheet_Documents#Filter_Options_for_the_CSV_Filter And, overloading the 12th token to allow a sheet *name* isn't a good idea because it would cause confusion with numeric sheet names. So a better way to specify a name is needed. For example, require a sheet *name* to be prefixed with, say ':' (to avoid confusion with sheet numbers). Or introduce a Token 13. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155270] [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]
https://bugs.documentfoundation.org/show_bug.cgi?id=155270 James changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9665 CC||user2...@proton.me -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155270] New: [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]
https://bugs.documentfoundation.org/show_bug.cgi?id=155270 Bug ID: 155270 Summary: [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ] Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: Feel free to break this out into sub bugs if need be. 0 - UI - Despite having "Ignore empty rows" enabled under the options sub menu, refreshing does not remove (empty). I - EDITING / FORMATTING - A somewhat similar but opposite vain to https://bugs.documentfoundation.org/show_bug.cgi?id=149665. II - EDITING / FORMATTING - A column of numbers did change to reflect the custom cell format. Steps to Reproduce: 0 - UI -- 1. Have a data set containing filled and empty rows. 2. Create a pivot table using the above. 3. Do not tick "Ignore empty rows" under options 4. Upon pivot table creation; Right click then "Properties". 5. Options -> tick "Ignore empty rows". 6. Hit ok and then right click, selecting "Refresh". I - EDITING / FORMATTING -- 1. Raw data is "3/1/2022" 2. Somehow during processing it become "'3/1/2022". 3. Removing the "'" allows for it to be converted to ISO-8601. In this case I had several; entires of "'X/X/XXX" and was unable to use find and replace to perform step 3. II - EDITING / FORMATTING -- 1. Have data such as 2. Highlight all applicable cells. 3. Right click, format cells. 4. User-defined. 5. Enter "0## ### " Actual Results: 0 - UI -- (empty) I - EDITING / FORMATTING -- 3/1/2022 II - EDITING / FORMATTING -- Expected Results: 0 - UI -- Render the cell blank as the case with pivot table data. I - EDITING / FORMATTING -- 2022-01-03 II - EDITING / FORMATTING -- 0XX XXX XXX... Reproducible: Always User Profile Reset: No Additional Info: Upgraded from 7.4.X.X. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: CL threaded Workbook layout Sheet A - Data set A Sheet B - Data set B Sheet C - Combines Data set A & B Sheet D - Pivot table using Sheet C -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155269] Chapter numbering mech silently changes para style numeric outline-level
https://bugs.documentfoundation.org/show_bug.cgi?id=155269 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please could you post in our forum https://ask.libreoffice.org/c/english/5. There are people with a deep acknowledge of Writer, maybe it is not a bug but the way how styles are used. In any case, here or there, a sample file, it's needed to test what's happen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152906] Text adjust to contour broken in recent draw/impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152906 m.a.riosv changed: What|Removed |Added CC||dmatsch...@quietriding.com --- Comment #6 from m.a.riosv --- *** Bug 155264 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155264] Unexpected results when selecting Adjust to Contour
https://bugs.documentfoundation.org/show_bug.cgi?id=155264 m.a.riosv changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEEDINFO|RESOLVED --- Comment #4 from m.a.riosv --- Some useful information on https://ask.libreoffice.org/t/why-is-adjust-to-contour-dim-in-text-window-in-draw/12149/5 *** This bug has been marked as a duplicate of bug 152906 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: basctl/source
basctl/source/basicide/localizationmgr.cxx | 64 +++--
1 file changed, 17 insertions(+), 47 deletions(-)
New commits:
commit e08c910f9ee520ce00fe99d6dab9988138996ee3
Author: Supriyo Paul
AuthorDate: Thu Mar 2 20:17:30 2023 +0530
Commit: Hossein
CommitDate: Sat May 13 00:54:00 2023 +0200
tdf#145538: traditional for loops to range-based for loops
changes traditional for to ranged based for in localizationmgr.cxx
goal: better readability for programmers
Change-Id: Ifde48037b27a794a9cdc3b1183f825651896cafb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148127
Tested-by: Jenkins
Reviewed-by: Hossein
diff --git a/basctl/source/basicide/localizationmgr.cxx
b/basctl/source/basicide/localizationmgr.cxx
index ef3a1ed9ff90..22e44c09c6aa 100644
--- a/basctl/source/basicide/localizationmgr.cxx
+++ b/basctl/source/basicide/localizationmgr.cxx
@@ -926,15 +926,10 @@ void LocalizationMgr::renameStringResourceIDs( const
ScriptDocument& rDocument,
xDummyStringResolver, RENAME_DIALOG_IDS );
// Handle all controls
-Sequence< OUString > aNames = xDialogModel->getElementNames();
-const OUString* pNames = aNames.getConstArray();
-sal_Int32 nCtrls = aNames.getLength();
-for( sal_Int32 i = 0 ; i < nCtrls ; ++i )
-{
-OUString aCtrlName( pNames[i] );
-Any aCtrl = xDialogModel->getByName( aCtrlName );
+for(const auto& rCtrlName : xDialogModel->getElementNames()) {
+Any aCtrl = xDialogModel->getByName( rCtrlName );
implHandleControlResourceProperties( aCtrl, aDlgName,
-aCtrlName, xStringResourceManager,
+rCtrlName, xStringResourceManager,
xDummyStringResolver, RENAME_DIALOG_IDS );
}
}
@@ -957,15 +952,10 @@ void LocalizationMgr::removeResourceForDialog( const
ScriptDocument& rDocument,
xDummyStringResolver, REMOVE_IDS_FROM_RESOURCE );
// Handle all controls
-Sequence< OUString > aNames = xDialogModel->getElementNames();
-const OUString* pNames = aNames.getConstArray();
-sal_Int32 nCtrls = aNames.getLength();
-for( sal_Int32 i = 0 ; i < nCtrls ; ++i )
-{
-OUString aCtrlName( pNames[i] );
-Any aCtrl = xDialogModel->getByName( aCtrlName );
+for(const auto& rCtrlName : xDialogModel->getElementNames()) {
+Any aCtrl = xDialogModel->getByName( rCtrlName );
implHandleControlResourceProperties( aCtrl, aDlgName,
-aCtrlName, xStringResourceManager,
+rCtrlName, xStringResourceManager,
xDummyStringResolver, REMOVE_IDS_FROM_RESOURCE );
}
}
@@ -985,15 +975,10 @@ void LocalizationMgr::resetResourceForDialog( const
Reference< container::XNameC
aDummyName, xStringResourceManager, xDummyStringResolver, RESET_IDS );
// Handle all controls
-Sequence< OUString > aNames = xDialogModel->getElementNames();
-const OUString* pNames = aNames.getConstArray();
-sal_Int32 nCtrls = aNames.getLength();
-for( sal_Int32 i = 0 ; i < nCtrls ; ++i )
-{
-OUString aCtrlName( pNames[i] );
-Any aCtrl = xDialogModel->getByName( aCtrlName );
+for(const auto& rCtrlName : xDialogModel->getElementNames()){
+Any aCtrl = xDialogModel->getByName( rCtrlName );
implHandleControlResourceProperties( aCtrl, aDummyName,
-aCtrlName, xStringResourceManager, xDummyStringResolver, RESET_IDS
);
+rCtrlName, xStringResourceManager, xDummyStringResolver, RESET_IDS
);
}
}
@@ -1012,15 +997,10 @@ void LocalizationMgr::setResourceIDsForDialog( const
Reference< container::XName
aDummyName, xStringResourceManager, xDummyStringResolver, SET_IDS );
// Handle all controls
-Sequence< OUString > aNames = xDialogModel->getElementNames();
-const OUString* pNames = aNames.getConstArray();
-sal_Int32 nCtrls = aNames.getLength();
-for( sal_Int32 i = 0 ; i < nCtrls ; ++i )
-{
-OUString aCtrlName( pNames[i] );
-Any aCtrl = xDialogModel->getByName( aCtrlName );
+for(const auto& rCtrlName : xDialogModel->getElementNames()) {
+Any aCtrl = xDialogModel->getByName( rCtrlName );
implHandleControlResourceProperties( aCtrl, aDummyName,
-aCtrlName, xStringResourceManager, xDummyStringResolver, SET_IDS );
+rCtrlName, xStringResourceManager, xDummyStringResolver, SET_IDS );
}
}
@@ -1066,15 +1046,10 @@ void LocalizationMgr::copyResourceForDroppedDialog(
const Reference< container::
std::u16string_view(), xStringResourceManager, xSourceStringResolver,
MOVE_RESOURCES );
// Handle all controls
-Sequence< OUString > aNames = xDialogModel->getElementNames();
-const OUString* pNames = aNames.getConstArray();
-sal_Int32 nCtrls = aNames.getLength();
-for( sal_Int32 i = 0 ; i < nCtrls ; ++i )
-{
-OUString aCtrlName( pNames[i] );
-Any aCtrl =
[Libreoffice-bugs] [Bug 145538] Use range based for loops
https://bugs.documentfoundation.org/show_bug.cgi?id=145538 --- Comment #22 from Commit Notification --- Supriyo Paul committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e08c910f9ee520ce00fe99d6dab9988138996ee3 tdf#145538: traditional for loops to range-based for loops It will be available in 7.6.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-bugs] [Bug 155260] Lots of CPU time spend in SwFieldType::GetXObject while spell-checking
https://bugs.documentfoundation.org/show_bug.cgi?id=155260 --- Comment #2 from Telesto --- (In reply to m.a.riosv from comment #1) > For me, it opens in a few seconds. No time to wait after enable 'Automatic > spell checker'. > Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community > Build ID: 99a88c9e55872214ce01d89447d18708e47e956b > CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win > Locale: es-ES (es_ES); UI: en-US Calc: CL threaded There is no delay when toggling automatic spell checker on or freeze, however LibreOffice keeps utilizing a single core in the task manager at max. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155269] New: Chapter numbering mech silently changes para style numeric outline-level
https://bugs.documentfoundation.org/show_bug.cgi?id=155269 Bug ID: 155269 Summary: Chapter numbering mech silently changes para style numeric outline-level Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rdbing...@verizon.net Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 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 Jumbo Discovered this issue while developing an OTT having several dozen custom styles across paragraph, frame, and page. My desired OTT functionality includes power-user usage of both: + various Writer effects dependent on the outline-level mechanism, particularly the [Insert->Field->More fields->Document tab->Chapter->Chapter name], and + use of the [Tools->Chapter number] mechanism for both auto chapter number prepend insertion by style name and by explicit field invocation [More fields->Document tab->Chapter->Chapter number]. Observed increasing erratic behaviors of the Chapter_name variables set of 10, 1 for each outline-level. Observed increasing erratic behaviors of the Chapter_numbering mechanism and variables set of 10, 1 for each element of the Chapter_number text-string and erratic behavior of the Automatic Numbering (auto-chapter_number text-string insertion) mechanism. In a purpose-created, compact diagnostic ODT, I tripped over the following reproducible sequences: Start with fresh File->New (Default OTT) diagnostic ODT. In Navigator->Styles->Paragraph, examine and record the numeric outline-levels of some paragraph styles you will play with in the [Tools->Chapter number] feature. For the Default OTT, that feature comes pre-loaded with the 'Heading ' styles. Just in case there is some hardcoded relationship to built-in para styles, create some custom styles inheriting from Default having a sample of numeric outline-level values + none (TextBody). Open the [Tools->Chapter number] feature UI. This UI, unfortunately for user confusion with Outline numeric level, uses the term "Levels." I will use the term Element here, each Element (of 10 total) having in turn a numeric index (1--10) and several property slots such as [Number:], [Paragraph style:], [Before:] and [After:]. Explaining my rational for Element that will take several paragraphs, so I defer that. Notice that with the Default OTT, the [Tools->Chapter number] feature is pre-loaded with the "Heading " paragraph styles such that the ascending Element numeric index matches the numeric value of the pre-load "Heading " family para styles. Make one or more changes to any of the 10 Elements' [Paragraph style:] property. Examples : + (A) move an incumbent style name in, say Element[4] [Paragraph style:] to, say Element7] [Paragraph style:]. You do this by going to Element[7] and selecting the style name of what is in Element[4] from the [Paragraph style:] picklist. You should see the change in the Preview area. + (B) remove (evict) some incumbent style name entirely from the 10-Element set of [Paragraph style:] styles. You do this by [Paragraph style:] < - [None] for some chosen Element index. + (C) add a para style not already in the incumbent style name set, either a Writer built-in or one of your new custom styles, to an Element [Paragraph style:] style slot, say Element[2], possibly displacing an incumbent style name. OK-close the [Tools->Chapter number] UI. In Navigator again examine the outline-levels of the paragraph styles you just manipulated above in [Tools->Chapter number] Element [Paragraph style:] properties. My observation is this: The [Tools->Chapter number] feature SILENTLY CHANGES the numeric outline-level of the para styles just manipulated such that after OK-close those outline-levels == the numeric value of the index of the Element where that para style name has been set in [Paragraph style:]. + For example (A), the new numeric outline-level for the re-located style is now 7. + For example (B), the new numeric outline-level for the evicted style is now TextBody. + For example (C), the new numeric outline-level for the net-added style is now 2. This in turn, in a document having chapter_number and outline-level schemes under development experimentation, silently breaks the functionality of all other Writer features dependent on an independently stable numeric outline-level scheme, such as default index tables and, wait for it, [Chapter name]. Of particular note is that if you evict one of the pre-load 'Heading ' styles, that style gets silently demoted to outline-level TextBody. There is nothing in the user-facing documentation which states that the numeric
[Libreoffice-bugs] [Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=108252 Bug 108252 depends on bug 126308, which changed state. Bug 126308 Summary: Escape character "'" (single quote) shows in final cell output https://bugs.documentfoundation.org/show_bug.cgi?id=126308 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126308] Escape character "'" (single quote) shows in final cell output
https://bugs.documentfoundation.org/show_bug.cgi?id=126308 ady changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from ady --- This is solved with the resolution in bug 149665 for LO 7.5. I'm not sure I would call it a duplicate, but the behavior presented here in bug 126308 is no longer present. If you want the apostrophe to be really part of the cell, then format the cell as text before introducing the content with its initial "'" (see Release Notes for LO 7.5). Setting as WFM. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155268] Wrong paragraph spacing when opening .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155268 --- Comment #1 from Hossein --- Created attachment 187235 --> https://bugs.documentfoundation.org/attachment.cgi?id=187235=edit PDF Output created with Office Live -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155268] New: Wrong paragraph spacing when opening .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155268 Bug ID: 155268 Summary: Wrong paragraph spacing when opening .doc file Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 187234 --> https://bugs.documentfoundation.org/attachment.cgi?id=187234=edit PDF Output created with the latest LO 7.6 dev on Windows Description: The paragraph spacing for the .doc files are sometimes incorrect. Steps to Reproduce: 1. Open attachment 149081 from tdf#123321 in LibreOffice 2. Create PDF output 3. Compare it with the output from MS Word. You can create PDF output with MS Office live viewer: (Click on "Print", then "Open PDF") https://view.officeapps.live.com/op/view.aspx?src=https://bugs.documentfoundation.org/attachment.cgi?id=149081 Actual Results: The paragraph spacing is different from MS Word, even on Windows with the same fonts Expected Results: The paragraph spacing should be similar to MS Word when appropriate fonts are availble Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: a9c14a3b2c1d14373b63cf0aff0eb92ab5d640d8 CPU threads: 32; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 104487] Function Wizard should remember Category selection per session
https://bugs.documentfoundation.org/show_bug.cgi?id=104487 --- Comment #15 from ady --- (In reply to Andreas Heinisch from comment #14) > Hm, for me it is not clear if this minimizes the clicks in the function > dialog. The current behavior is useful only when the usual functions that are being used are all from the same Category. For any other case, users have to either use the Search field (i.e. "All" Category), or click on the Category field in order to select the "Last Used" Category. This is relevant for empty cells, or for nested functions, while you are building a complex formula. When the recent functions that were/are being used are part of different Categories, having the "Last Used" Category ready allows to keep using them: a single click to select, versus at least two clicks or typing-in in the aforementioned situation (which is the current behavior). Moreover, the same proposed behavior also allows one click selection when the functions are from the same Category, because they are also part of the "Last Used" Category. The only case in which there is no relative advantage in the proposed behavior is when the user is using "much more than just a few" functions in the recent runs of the F.W. while all those functions come from the same Category. If the functions are not from the same Category, then there is no "cons" either. > You may also provide a patch for the function itself because it is > just setting a static variable > (https://gerrit.libreoffice.org/c/core/+/151565). I may review the change. Sure, except that I am not a developer so I have no idea how to do it :(. -- You are receiving this mail because: You are on the CC list for the bug.
Libreoffice 7.6 code checkout from https://dev-www.libreoffice.org/bundles
Hi everyone Does the 07-May-2023 release of 7 codepacks from https://dev-www.libreoffice.org/ bundles contain the code to check out and compile lo7.6 alpha 1 build, offline and self-sufficient? Debian 32 and 64bit How do I ‘checkout’ the exact alpha release from what i assume is a more generic codebase in the above bundles. Many Thanks -- Alex Tao Tao Submarines and Systems Chios, Aegean Sea
[Libreoffice-bugs] [Bug 143223] Tab key have no effect just after copy/paste one cell to another
https://bugs.documentfoundation.org/show_bug.cgi?id=143223 --- Comment #4 from ady --- This is not a bug. The relation to pasting actions is only indirect. When you have selected cells, the [TAB] key makes the focus jump between the selected cells. This is similar to what happens when you jump from field to field in a dialog window (or in most applications). 1. New Calc. 2. Click on some cell once. That cell will have the focus. 3. [CTRL]+click on some other cell that is not adjacent to the prior cell – this is just to make the behavior easier to spot. Both cells are now selected. 4. Press [TAB] several times. The focus "jumps" between the selected cells for each time the [TAB] key is pressed. There are several advantages/utilities of this behavior. The same thing happens when you have only one cell selected, except the "jump" is always to the same cell, so you don't notice it. To "un-select" the cell, instead of [TAB] simply use the arrow keys, or click on some cell. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139863] Grantha consonants combining with Vedic svara markers are not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=139863 --- Comment #6 from خالد حسني --- I suspect that the fact ጕ (U+11305) is outside the basic multilingual plane (i.e. represented by a UTF-16 surrogate pair) has something to do with what is happening here. Looks like some code path is not handling surrogate pairs correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121221] Formula editor: Upside down question-marks appear for SOME characters in equations
https://bugs.documentfoundation.org/show_bug.cgi?id=121221 --- Comment #3 from Sebastian Lonnberg --- https://olmadi-olmuyor1.blogspot.com/ https://olmadi-olmuyor10.blogspot.com/ https://olmadi-olmuyor100.blogspot.com/ https://olmadi-olmuyor101.blogspot.com/ https://olmadi-olmuyor101.blogspot.com/ https://olmadi-olmuyor102.blogspot.com/ https://olmadi-olmuyor103.blogspot.com/ https://olmadi-olmuyor104.blogspot.com/ https://olmadi-olmuyor105.blogspot.com/ https://olmadi-olmuyor106.blogspot.com/ https://olmadi-olmuyor107.blogspot.com/ https://olmadi-olmuyor108.blogspot.com/ https://olmadi-olmuyor109.blogspot.com/ https://olmadi-olmuyor11.blogspot.com/ https://olmadi-olmuyor110.blogspot.com/ https://olmadi-olmuyor111.blogspot.com/ https://olmadi-olmuyor112.blogspot.com/ https://olmadi-olmuyor113.blogspot.com/ https://olmadi-olmuyor114.blogspot.com/ https://olmadi-olmuyor115.blogspot.com/ https://olmadi-olmuyor116.blogspot.com/ https://olmadi-olmuyor117.blogspot.com/ https://olmadi-olmuyor118.blogspot.com/ https://olmadi-olmuyor119.blogspot.com/ https://olmadi-olmuyor12.blogspot.com/ https://olmadi-olmuyor120.blogspot.com/ https://olmadi-olmuyor121.blogspot.com/ https://olmadi-olmuyor122.blogspot.com/ https://olmadi-olmuyor123.blogspot.com/ https://olmadi-olmuyor124.blogspot.com/ https://olmadi-olmuyor125.blogspot.com/ https://olmadi-olmuyor126.blogspot.com/ https://olmadi-olmuyor127.blogspot.com/ https://olmadi-olmuyor128.blogspot.com/ https://olmadi-olmuyor129.blogspot.com/ https://olmadi-olmuyor13.blogspot.com/ https://olmadi-olmuyor130.blogspot.com/ https://olmadi-olmuyor131.blogspot.com/ https://olmadi-olmuyor132.blogspot.com/ https://olmadi-olmuyor133.blogspot.com/ https://olmadi-olmuyor134.blogspot.com/ https://olmadi-olmuyor135.blogspot.com/ https://olmadi-olmuyor136.blogspot.com/ https://olmadi-olmuyor137.blogspot.com/ https://olmadi-olmuyor138.blogspot.com/ https://olmadi-olmuyor139.blogspot.com/ https://olmadi-olmuyor14.blogspot.com/ https://olmadi-olmuyor140.blogspot.com/ https://olmadi-olmuyor141.blogspot.com/ https://olmadi-olmuyor142.blogspot.com/ https://olmadi-olmuyor143.blogspot.com/ https://olmadi-olmuyor144.blogspot.com/ https://olmadi-olmuyor145.blogspot.com/ https://olmadi-olmuyor146.blogspot.com/ https://olmadi-olmuyor147.blogspot.com/ https://olmadi-olmuyor148.blogspot.com/ https://olmadi-olmuyor149.blogspot.com/ https://olmadi-olmuyor15.blogspot.com/ https://olmadi-olmuyor150.blogspot.com/ https://olmadi-olmuyor151.blogspot.com/ https://olmadi-olmuyor152.blogspot.com/ https://olmadi-olmuyor153.blogspot.com/ https://olmadi-olmuyor154.blogspot.com/ https://olmadi-olmuyor155.blogspot.com/ https://olmadi-olmuyor156.blogspot.com/ https://olmadi-olmuyor157.blogspot.com/ https://olmadi-olmuyor158.blogspot.com/ https://olmadi-olmuyor159.blogspot.com/ https://olmadi-olmuyor16.blogspot.com/ https://olmadi-olmuyor160.blogspot.com/ https://olmadi-olmuyor161.blogspot.com/ https://olmadi-olmuyor162.blogspot.com/ https://olmadi-olmuyor163.blogspot.com/ https://olmadi-olmuyor164.blogspot.com/ https://olmadi-olmuyor165.blogspot.com/ https://olmadi-olmuyor166.blogspot.com/ https://olmadi-olmuyor167.blogspot.com/ https://olmadi-olmuyor168.blogspot.com/ https://olmadi-olmuyor169.blogspot.com/ https://olmadi-olmuyor17.blogspot.com/ https://olmadi-olmuyor170.blogspot.com/ https://olmadi-olmuyor171.blogspot.com/ https://olmadi-olmuyor172.blogspot.com/ https://olmadi-olmuyor173.blogspot.com/ https://olmadi-olmuyor174.blogspot.com/ https://olmadi-olmuyor175.blogspot.com/ https://olmadi-olmuyor176.blogspot.com/ https://olmadi-olmuyor177.blogspot.com/ https://olmadi-olmuyor178.blogspot.com/ https://olmadi-olmuyor179.blogspot.com/ https://olmadi-olmuyor18.blogspot.com/ https://olmadi-olmuyor180.blogspot.com/ https://olmadi-olmuyor181.blogspot.com/ https://olmadi-olmuyor182.blogspot.com/ https://olmadi-olmuyor183.blogspot.com/ https://olmadi-olmuyor184.blogspot.com/ https://olmadi-olmuyor185.blogspot.com/ https://olmadi-olmuyor186.blogspot.com/ https://olmadi-olmuyor187.blogspot.com/ https://olmadi-olmuyor188.blogspot.com/ https://olmadi-olmuyor189.blogspot.com/ https://olmadi-olmuyor19.blogspot.com/ https://olmadi-olmuyor190.blogspot.com/ https://olmadi-olmuyor191.blogspot.com/ https://olmadi-olmuyor192.blogspot.com/ https://olmadi-olmuyor193.blogspot.com/ https://olmadi-olmuyor194.blogspot.com/ https://olmadi-olmuyor195.blogspot.com/ https://olmadi-olmuyor196.blogspot.com/ https://olmadi-olmuyor197.blogspot.com/ https://olmadi-olmuyor198.blogspot.com/ https://olmadi-olmuyor199.blogspot.com/ https://olmadi-olmuyor2.blogspot.com/ https://olmadi-olmuyor20.blogspot.com/ https://olmadi-olmuyor200.blogspot.com/ https://olmadi-olmuyor201.blogspot.com/ https://olmadi-olmuyor202.blogspot.com/ https://olmadi-olmuyor203.blogspot.com/ https://olmadi-olmuyor204.blogspot.com/ https://olmadi-olmuyor205.blogspot.com/ https://olmadi-olmuyor206.blogspot.com/ https://olmadi-olmuyor207.blogspot.com/
[Libreoffice-bugs] [Bug 121221] Formula editor: Upside down question-marks appear for SOME characters in equations
https://bugs.documentfoundation.org/show_bug.cgi?id=121221 --- Comment #2 from Sebastian Lonnberg --- https://akrep1.blogspot.com/ https://akrep10.blogspot.com/ https://akrep11.blogspot.com/ https://akrep12.blogspot.com/ https://akrep13.blogspot.com/ https://akrep14.blogspot.com/ https://akrep15.blogspot.com/ https://akrep16.blogspot.com/ https://akrep18.blogspot.com/ https://akrep2.blogspot.com/ https://akrep22.blogspot.com/ https://akrep23.blogspot.com/ https://akrep24.blogspot.com/ https://akrep26.blogspot.com/ https://akrep28.blogspot.com/ https://akrep29.blogspot.com/ https://akrep30.blogspot.com/ https://akrep31.blogspot.com/ https://akrep32.blogspot.com/ https://akrep33.blogspot.com/ https://akrep36.blogspot.com/ https://akrep39.blogspot.com/ https://akrep4.blogspot.com/ https://akrep40.blogspot.com/ https://akrep41.blogspot.com/ https://akrep43.blogspot.com/ https://akrep44.blogspot.com/ https://akrep46.blogspot.com/ https://akrep47.blogspot.com/ https://akrep48.blogspot.com/ https://akrep49.blogspot.com/ https://akrep5.blogspot.com/ https://akrep50.blogspot.com/ https://akrep51.blogspot.com/ https://akrep52.blogspot.com/ https://akrep53.blogspot.com/ https://akrep56.blogspot.com/ https://akrep57.blogspot.com/ https://akrep58.blogspot.com/ https://akrep59.blogspot.com/ https://akrep6.blogspot.com/ https://akrep60.blogspot.com/ https://akrep61.blogspot.com/ https://akrep62.blogspot.com/ https://akrep63.blogspot.com/ https://akrep64.blogspot.com/ https://akrep65.blogspot.com/ https://akrep66.blogspot.com/ https://akrep67.blogspot.com/ https://akrep68.blogspot.com/ https://akrep7.blogspot.com/ https://akrep70.blogspot.com/ https://akrep71.blogspot.com/ https://akrep72.blogspot.com/ https://akrep73.blogspot.com/ https://akrep75.blogspot.com/ https://akrep8.blogspot.com/ https://akrep9.blogspot.com/ https://aslanlaar1.blogspot.com/ https://aslanlaar10.blogspot.com/ https://aslanlaar11.blogspot.com/ https://aslanlaar12.blogspot.com/ https://aslanlaar13.blogspot.com/ https://aslanlaar14.blogspot.com/ https://aslanlaar15.blogspot.com/ https://aslanlaar16.blogspot.com/ https://aslanlaar17.blogspot.com/ https://aslanlaar18.blogspot.com/ https://aslanlaar19.blogspot.com/ https://aslanlaar2.blogspot.com/ https://aslanlaar20.blogspot.com/ https://aslanlaar21.blogspot.com/ https://aslanlaar22.blogspot.com/ https://aslanlaar23.blogspot.com/ https://aslanlaar24.blogspot.com/ https://aslanlaar25.blogspot.com/ https://aslanlaar26.blogspot.com/ https://aslanlaar27.blogspot.com/ https://aslanlaar28.blogspot.com/ https://aslanlaar29.blogspot.com/ https://aslanlaar3.blogspot.com/ https://aslanlaar30.blogspot.com/ https://aslanlaar31.blogspot.com/ https://aslanlaar32.blogspot.com/ https://aslanlaar33.blogspot.com/ https://aslanlaar34.blogspot.com/ https://aslanlaar35.blogspot.com/ https://aslanlaar36.blogspot.com/ https://aslanlaar37.blogspot.com/ https://aslanlaar38.blogspot.com/ https://aslanlaar39.blogspot.com/ https://aslanlaar4.blogspot.com/ https://aslanlaar40.blogspot.com/ https://aslanlaar41.blogspot.com/ https://aslanlaar42.blogspot.com/ https://aslanlaar43.blogspot.com/ https://aslanlaar44.blogspot.com/ https://aslanlaar45.blogspot.com/ https://aslanlaar46.blogspot.com/ https://aslanlaar47.blogspot.com/ https://aslanlaar48.blogspot.com/ https://aslanlaar49.blogspot.com/ https://aslanlaar5.blogspot.com/ https://aslanlaar50.blogspot.com/ https://aslanlaar51.blogspot.com/ https://aslanlaar52.blogspot.com/ https://aslanlaar53.blogspot.com/ https://aslanlaar54.blogspot.com/ https://aslanlaar55.blogspot.com/ https://aslanlaar56.blogspot.com/ https://aslanlaar6.blogspot.com/ https://aslanlaar7.blogspot.com/ https://aslanlaar8.blogspot.com/ https://aslanlaar9.blogspot.com/ https://brokoli1.blogspot.com/ https://brokoli10.blogspot.com/ https://brokoli11.blogspot.com/ https://brokoli13.blogspot.com/ https://brokoli15.blogspot.com/ https://brokoli17.blogspot.com/ https://brokoli18.blogspot.com/ https://brokoli19.blogspot.com/ https://brokoli2.blogspot.com/ https://brokoli21.blogspot.com/ https://brokoli3.blogspot.com/ https://brokoli4.blogspot.com/ https://brokoli5.blogspot.com/ https://brokoli6.blogspot.com/ https://brokoli7.blogspot.com/ https://brokoli8.blogspot.com/ https://brokoli9.blogspot.com/ https://civanpercemi1.blogspot.com/ https://civanpercemi10.blogspot.com/ https://civanpercemi11.blogspot.com/ https://civanpercemi12.blogspot.com/ https://civanpercemi13.blogspot.com/ https://civanpercemi14.blogspot.com/ https://civanpercemi15.blogspot.com/ https://civanpercemi16.blogspot.com/ https://civanpercemi17.blogspot.com/ https://civanpercemi18.blogspot.com/ https://civanpercemi19.blogspot.com/ https://civanpercemi2.blogspot.com/ https://civanpercemi20.blogspot.com/ https://civanpercemi21.blogspot.com/ https://civanpercemi22.blogspot.com/ https://civanpercemi23.blogspot.com/ https://civanpercemi24.blogspot.com/ https://civanpercemi25.blogspot.com/ https://civanpercemi26.blogspot.com/
[Libreoffice-bugs] [Bug 91235] appending nowidth breaking character, corrupts searching in Persian
https://bugs.documentfoundation.org/show_bug.cgi?id=91235 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from خالد حسني --- I can’t reproduce either. Search works fine with or without U+200C appended to the text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112810] [META] Arabic & Farsi language-specific RTL issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112810 Bug 112810 depends on bug 91235, which changed state. Bug 91235 Summary: appending nowidth breaking character, corrupts searching in Persian https://bugs.documentfoundation.org/show_bug.cgi?id=91235 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155243] EDITING: keyboard, or most combinations, are dead when document opens. And no blinking cursor in writer. But there are ways to get around.
https://bugs.documentfoundation.org/show_bug.cgi?id=155243 --- Comment #1 from u...@net9.ga --- After a reboot, and possibly upgrading some packages, but not the software mentioned before, I had the following experience: Launched a bare X server, running only a terminal. Within the terminal, run a handful of commands, including using the mouse to copy-paste. Then run SAL_USE_VCLPLUGIN=gen soffice --writer The following 2 lines were printed to the terminal: javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx And writer started fine. Blinking cursor, Ctrl+f fully working. But after quitting writer the terminal was completely unresponsive. Both the keyboard, and the mouse, were unresponsive. And the terminal cursor was an blanked rectangle. I had to kill the X environment from another VT. After restarting X, this time with a window manager, things got back to what they used to be. Including the documents that are opened by writer without a blinking cursor, and without a response from Ctrl+f. Though it looks like not only a mouse click brings things back to their normal working order, but also pressing the down arrow key. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155267] New: ACCESSIBILITY: With universal accessibility option (PDF/UA) on export to PDF, show a warning of accessibility issues, with attached file.
https://bugs.documentfoundation.org/show_bug.cgi?id=155267 Bug ID: 155267 Summary: ACCESSIBILITY: With universal accessibility option (PDF/UA) on export to PDF, show a warning of accessibility issues, with attached file. Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miguelange...@libreoffice.org With file https://bugs.documentfoundation.org/attachment.cgi?id=151324, exporting as PDF and Universal accessibility option enable, after a about 15", shows a message: 159546 accessibility issues detected. Do you want to continue? [Continue] export is successful in about 50". [Investigate issues] LO seems doing something but never ends, I drop out it after more than three hours. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: emfio/inc emfio/qa emfio/source
emfio/inc/mtftools.hxx |4 -
emfio/qa/cppunit/wmf/data/TestSetTextAlign.wmf |binary
emfio/qa/cppunit/wmf/wmfimporttest.cxx | 91 +
emfio/source/reader/mtftools.cxx | 10 +-
4 files changed, 99 insertions(+), 6 deletions(-)
New commits:
commit 717bdd06a7ac1a2a266f36a43d7f1e695559d056
Author: Bartosz Kosiorek
AuthorDate: Wed May 10 22:30:20 2023 +0200
Commit: Bartosz Kosiorek
CommitDate: Fri May 12 22:42:00 2023 +0200
EMF Fix text aligning for EMR_SETTEXTALIGN for wrong values.
Change-Id: I4d67eb7112d2295185905eac52ebab022a1beb78
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151670
Tested-by: Jenkins
Reviewed-by: Bartosz Kosiorek
diff --git a/emfio/inc/mtftools.hxx b/emfio/inc/mtftools.hxx
index b2237736869b..f5638af59ecb 100644
--- a/emfio/inc/mtftools.hxx
+++ b/emfio/inc/mtftools.hxx
@@ -178,7 +178,9 @@ namespace emfio
TA_RIGHT_CENTER = (TA_RIGHT | TA_CENTER),
TA_TOP = 0x,
TA_BOTTOM = 0x0008,
-TA_BASELINE = 0x0018,
+// In [MS-WMF] 2.1.2.3, TA_BASELINE value is wrong.
+// It is 0x0018 and it should be 0x0010.
+TA_BASELINE = 0x0010,
TA_RTLREADING = 0x0100
};
diff --git a/emfio/qa/cppunit/wmf/data/TestSetTextAlign.wmf
b/emfio/qa/cppunit/wmf/data/TestSetTextAlign.wmf
new file mode 100644
index ..9a3ad46f1d32
Binary files /dev/null and b/emfio/qa/cppunit/wmf/data/TestSetTextAlign.wmf
differ
diff --git a/emfio/qa/cppunit/wmf/wmfimporttest.cxx
b/emfio/qa/cppunit/wmf/wmfimporttest.cxx
index 48e47fb0fd36..780933da58d7 100644
--- a/emfio/qa/cppunit/wmf/wmfimporttest.cxx
+++ b/emfio/qa/cppunit/wmf/wmfimporttest.cxx
@@ -48,6 +48,7 @@ public:
void testNonPlaceableWmf();
void testTdf88163NonPlaceableWmf();
void testTdf88163PlaceableWmf();
+void testSetTextAlignWmf();
void testSine();
void testEmfProblem();
void testEmfLineStyles();
@@ -65,6 +66,7 @@ public:
CPPUNIT_TEST(testNonPlaceableWmf);
CPPUNIT_TEST(testTdf88163NonPlaceableWmf);
CPPUNIT_TEST(testTdf88163PlaceableWmf);
+CPPUNIT_TEST(testSetTextAlignWmf);
CPPUNIT_TEST(testSine);
CPPUNIT_TEST(testEmfProblem);
CPPUNIT_TEST(testEmfLineStyles);
@@ -184,6 +186,95 @@ void WmfTest::testTdf88163PlaceableWmf()
assertXPath(pDoc, "/metafile/push[2]/textarray[3]", "y", "390");
}
+void WmfTest::testSetTextAlignWmf()
+{
+OUString fileName(u"TestSetTextAlign.wmf");
+SvFileStream aFileStream(getFullUrl(fileName), StreamMode::READ);
+GDIMetaFile aGDIMetaFile;
+ReadWindowMetafile(aFileStream, aGDIMetaFile);
+
+MetafileXmlDump dumper;
+
+xmlDocUniquePtr pDoc = dumpAndParse(dumper, aGDIMetaFile);
+
+CPPUNIT_ASSERT(pDoc);
+
+assertXPath(pDoc, "/metafile", "height", "20999");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[2]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[2]", "x", "11642");
+assertXPath(pDoc, "/metafile/push[2]/textarray[2]", "y", "212");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[2]/text",
"textalignment:default");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[3]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[3]", "x", "12700");
+assertXPath(pDoc, "/metafile/push[2]/textarray[3]", "y", "212");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[3]/text",
"textalignment:0x00");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[4]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[4]", "x", "11999");
+assertXPath(pDoc, "/metafile/push[2]/textarray[4]", "y", "423");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[4]/text",
"textalignment:0x02");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[5]", "align", "top");
+// Fails without the fix: Expected: 11999, Actual: 12350
+assertXPath(pDoc, "/metafile/push[2]/textarray[5]", "x", "11999");
+assertXPath(pDoc, "/metafile/push[2]/textarray[5]", "y", "635");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[5]/text",
"textalignment:0x04");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[6]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[6]", "x", "12350");
+assertXPath(pDoc, "/metafile/push[2]/textarray[6]", "y", "847");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[6]/text",
"textalignment:0x06");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[7]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[7]", "x", "12700");
+assertXPath(pDoc, "/metafile/push[2]/textarray[7]", "y", "1058");
+assertXPathContent(pDoc, "/metafile/push[2]/textarray[7]/text",
"textalignment:0x08");
+
+assertXPath(pDoc, "/metafile/push[2]/textalign[8]", "align", "top");
+assertXPath(pDoc, "/metafile/push[2]/textarray[8]", "x", "11999");
+assertXPath(pDoc,
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 BogdanB changed: What|Removed |Added Depends on||141638 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141638 [Bug 141638] Rotation impossible *on new files*: Green circles don't appear -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141638] Rotation impossible *on new files*: Green circles don't appear
https://bugs.documentfoundation.org/show_bug.cgi?id=141638 BogdanB changed: What|Removed |Added Blocks||108741 CC||buzea.bog...@libreoffice.or ||g --- Comment #3 from BogdanB --- Also in Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108741 [Bug 108741] [META] Shapes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 BogdanB changed: What|Removed |Added Depends on||139863 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=139863 [Bug 139863] Grantha consonants combining with Vedic svara markers are not displayed correctly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139863] Grantha consonants combining with Vedic svara markers are not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=139863 BogdanB changed: What|Removed |Added Blocks||71732 CC||buzea.bog...@libreoffice.or ||g --- Comment #5 from BogdanB --- Can you retest this bug? Partially, it is better than the PDF. But not enough. Retested with Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sc/inc sc/source
sc/inc/colorscale.hxx |2 ++
sc/source/core/data/colorscale.cxx | 15 +++
2 files changed, 17 insertions(+)
New commits:
commit 3fc2dce9d332268a93c854e9badf12b9076b1457
Author: Henry Castro
AuthorDate: Thu May 11 16:23:03 2023 -0400
Commit: Henry Castro
CommitDate: Fri May 12 22:25:16 2023 +0200
sc: copy cache values when clone color conditional format
When clone a conditional format list, also copy the cache
values that hold the min and max values, otherwise if clone
occurs when copying to the clipboard the values have wrong
data due to limiting range cells copied.
Signed-off-by: Henry Castro
Change-Id: Id9085a1488a3bde24842e0d2e062c9b425074157
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151686
Tested-by: Jenkins CollaboraOffice
diff --git a/sc/inc/colorscale.hxx b/sc/inc/colorscale.hxx
index 9923eac4c572..fc5c34dda287 100644
--- a/sc/inc/colorscale.hxx
+++ b/sc/inc/colorscale.hxx
@@ -224,6 +224,8 @@ public:
virtual ~ScColorFormat() override;
const ScRangeList& GetRange() const;
+void SetCache(const std::vector& aValues);
+std::vector GetCache() const;
virtual void SetParent(ScConditionalFormat* pParent) override;
diff --git a/sc/source/core/data/colorscale.cxx
b/sc/source/core/data/colorscale.cxx
index 34cdb91511d2..c8f8d84f1873 100644
--- a/sc/source/core/data/colorscale.cxx
+++ b/sc/source/core/data/colorscale.cxx
@@ -379,6 +379,9 @@ ScColorScaleFormat::ScColorScaleFormat(ScDocument* pDoc,
const ScColorScaleForma
{
maColorScales.emplace_back(new ScColorScaleEntry(pDoc, *rxEntry));
}
+
+auto aCache = rFormat.GetCache();
+SetCache(aCache);
}
ScColorFormat* ScColorScaleFormat::Clone(ScDocument* pDoc) const
@@ -440,6 +443,18 @@ const ScRangeList& ScColorFormat::GetRange() const
return mpParent->GetRange();
}
+std::vector ScColorFormat::GetCache() const
+{
+std::vector empty;
+return mpCache ? mpCache->maValues : empty;
+}
+
+void ScColorFormat::SetCache(const std::vector& aValues)
+{
+mpCache.reset(new ScColorFormatCache);
+mpCache->maValues = aValues;
+}
+
std::vector& ScColorFormat::getValues() const
{
if(!mpCache)
[Libreoffice-bugs] [Bug 107656] [META] Frame bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107656 BogdanB changed: What|Removed |Added Depends on||143570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143570 [Bug 143570] Cut/paste object area for auto-layout makes 'Click to edit the outline text" permanent -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 BogdanB changed: What|Removed |Added Depends on||143570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143570 [Bug 143570] Cut/paste object area for auto-layout makes 'Click to edit the outline text" permanent -- You are receiving this mail because: You are the assignee for the bug.
