[Libreoffice-bugs] [Bug 105961] TABLE/GUI: Numeric and Decimal doesn' t allow input of more than 17 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=105961 --- Comment #4 from rob...@familiegrosskopf.de --- Nothing changed in Version: 6.0.1.1 Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: kde4; Locale: de-DE (de_DE.UTF-8); Calc: group Input of more than 17 digits isn't saved through GUI in Decimal and Numeric fields. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115670] openfile .docx unnecessary grey box or area beside left vertical box
https://bugs.documentfoundation.org/show_bug.cgi?id=115670 Julien Nabetchanged: What|Removed |Added Summary|openfile .docx unnecssary |openfile .docx unnecessary |grey box or area beside |grey box or area beside |left vertical box |left vertical box -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115661] same Elementary icons for different figures on Flowchart toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=115661 Commit Notificationchanged: What|Removed |Added Whiteboard||target:6.1.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115661] same Elementary icons for different figures on Flowchart toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=115661 --- Comment #2 from Commit Notification--- andreas kainz committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=1c8f53ae76b18c015095c9998df617a7800370ce tdf#115661 Elementary icon fix lc_flowchartshapes.flowchart-sort It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: icon-themes/elementary icon-themes/elementary_svg
icon-themes/elementary/cmd/lc_flowchartshapes.flowchart-sort.png |binary icon-themes/elementary_svg/cmd/lc_flowchartshapes.flowchart-sort.svg |2 +- 2 files changed, 1 insertion(+), 1 deletion(-) New commits: commit 1c8f53ae76b18c015095c9998df617a7800370ce Author: andreas kainzDate: Tue Feb 13 08:35:52 2018 +0100 tdf#115661 Elementary icon fix lc_flowchartshapes.flowchart-sort Change-Id: I897bd294a5352b44de35b035a58368353f938e0d Reviewed-on: https://gerrit.libreoffice.org/49619 Reviewed-by: andreas_kainz Tested-by: andreas_kainz diff --git a/icon-themes/elementary/cmd/lc_flowchartshapes.flowchart-sort.png b/icon-themes/elementary/cmd/lc_flowchartshapes.flowchart-sort.png index 478769d0ce78..d641ee85fb31 100644 Binary files a/icon-themes/elementary/cmd/lc_flowchartshapes.flowchart-sort.png and b/icon-themes/elementary/cmd/lc_flowchartshapes.flowchart-sort.png differ diff --git a/icon-themes/elementary_svg/cmd/lc_flowchartshapes.flowchart-sort.svg b/icon-themes/elementary_svg/cmd/lc_flowchartshapes.flowchart-sort.svg index d7e6df08962f..08a288d1fe25 100644 --- a/icon-themes/elementary_svg/cmd/lc_flowchartshapes.flowchart-sort.svg +++ b/icon-themes/elementary_svg/cmd/lc_flowchartshapes.flowchart-sort.svg @@ -1 +1 @@ -http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file +http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 115674] New: lo viewer closes opening docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=115674 Bug ID: 115674 Summary: lo viewer closes opening docx file Product: LibreOffice Version: 6.1.0.0.alpha0+ Master Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Viewer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kris...@grrlz.net open Table of Contents [public].docx attachment 86275 on bug# 69655 current behaviour: closes lo viewer master daily build expected behaviour: view contents of file tinderbox: buildname: Android-ARM@24-Bytemark-Hosting tinderbox: tree: MASTER tinderbox: pull time 2018-02-12 15:26:16 tinderbox: git sha1s core:9cf2616c5e709b5956ab88dacdfad2003f98 lyf flame 3, android 5.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86568] BASIC IDE: horizontal scrollbar isn’t next to the box it controls
https://bugs.documentfoundation.org/show_bug.cgi?id=86568 Samuel Mehrbrodt (CIB)changed: What|Removed |Added Severity|minor |enhancement -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] online.git: tools/Config.cpp
tools/Config.cpp |8 1 file changed, 4 insertions(+), 4 deletions(-) New commits: commit 463fc6044021b94440701bd80fb7a9a7ee0ae2d0 Author: Pranav KantDate: Tue Feb 13 12:33:01 2018 +0530 loolconfig: set-raw-config -> set Change-Id: I7821bcf7bf8a6b8247e824d18b1d9f29b8db8851 diff --git a/tools/Config.cpp b/tools/Config.cpp index 79f4398b..b5c815af 100644 --- a/tools/Config.cpp +++ b/tools/Config.cpp @@ -102,7 +102,7 @@ void Config::displayHelp() #if ENABLE_SUPPORT_KEY << "set-support-key\n" #endif - << "set-raw-config " << std::endl; + << "set " << std::endl; } void Config::defineOptions(OptionSet& optionSet) @@ -299,7 +299,7 @@ int Config::main(const std::vector& args) changed = true; } #endif -else if (args[0] == "set-raw-config") +else if (args[0] == "set") { if (args.size() == 3) { @@ -317,9 +317,9 @@ int Config::main(const std::vector& args) std::cerr << "No property, \"" << args[1] << "\"," << " found in config file." << std::endl; } else -std::cerr << "set-raw-config expects a key and value as arguments" << std::endl +std::cerr << "set expects a key and value as arguments" << std::endl << "Eg: " << std::endl - << "set-raw-config logging.level trace" << std::endl; + << "set logging.level trace" << std::endl; } else ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 --- Comment #3 from BLaACkRose--- The table is not selected therefore noting is assigned -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96483] Tips of Navigation Icons in Find Toolbar are no Longer Specific since Version 4.3.0
https://bugs.documentfoundation.org/show_bug.cgi?id=96483 BLaACkRosechanged: What|Removed |Added Blocks|108743 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108743 [Bug 108743] [META] Find toolbar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108743 BLaACkRosechanged: What|Removed |Added CC||bhavypolad...@gmail.com Depends on|96483 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=96483 [Bug 96483] Tips of Navigation Icons in Find Toolbar are no Longer Specific since Version 4.3.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/notebookbar_single.ui |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) New commits: commit 71efbe9244818ae5a4245e7c7854b81fbafd16f7 Author: Yousuf PhilipsDate: Fri Feb 9 16:34:15 2018 +0400 Notebookbar Single: Fix context glitch and spacing Change-Id: I9417b45b190bab746e5f9fa08b7076b4488bcf16 Reviewed-on: https://gerrit.libreoffice.org/49492 Tested-by: Jenkins Reviewed-by: Yousuf Philips diff --git a/sw/uiconfig/swriter/ui/notebookbar_single.ui b/sw/uiconfig/swriter/ui/notebookbar_single.ui index 7266c9019dbc..e75440e41e2a 100644 --- a/sw/uiconfig/swriter/ui/notebookbar_single.ui +++ b/sw/uiconfig/swriter/ui/notebookbar_single.ui @@ -20,6 +20,8 @@ True False center +6 +6 3 @@ -761,7 +763,7 @@ - + ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/sglobal/menubar/menubar.xml | 139 +--- 1 file changed, 78 insertions(+), 61 deletions(-) New commits: commit 18d78dac064bdb16c54c89563d8df22803e84083 Author: Yousuf PhilipsDate: Thu Feb 8 01:10:34 2018 +0400 tdf#103733 Unify writer master doc menu with writer Change-Id: I147544acc2b783538f5a69fd0cdad1837b0abbd0 Reviewed-on: https://gerrit.libreoffice.org/49395 Tested-by: Jenkins Reviewed-by: Yousuf Philips diff --git a/sw/uiconfig/sglobal/menubar/menubar.xml b/sw/uiconfig/sglobal/menubar/menubar.xml index 614025b0fa5d..ab133daf836c 100644 --- a/sw/uiconfig/sglobal/menubar/menubar.xml +++ b/sw/uiconfig/sglobal/menubar/menubar.xml @@ -20,7 +20,7 @@ - + @@ -48,7 +48,14 @@ - + + + + + + + + @@ -118,7 +125,9 @@ + + @@ -156,8 +165,8 @@ - - + + @@ -196,7 +205,7 @@ - + @@ -222,7 +231,14 @@ - + + + + + + + + @@ -266,7 +282,9 @@ - + + + @@ -278,6 +296,7 @@ + @@ -321,41 +340,8 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -452,10 +438,10 @@ - - + + @@ -503,12 +489,6 @@ - - - - - - @@ -519,6 +499,8 @@ + + @@ -572,8 +554,6 @@ - - @@ -585,7 +565,10 @@ + + + @@ -664,6 +647,50 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -697,16 +724,6 @@ - - - - - - - - - - ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: avmedia/source basctl/source basic/source
avmedia/source/viewer/mediawindow.cxx |4 +-- avmedia/source/viewer/mediawindow_impl.cxx | 14 +- basctl/source/basicide/baside2.cxx | 10 +++ basctl/source/basicide/baside2b.cxx| 38 ++--- basctl/source/basicide/basides1.cxx| 10 +++ basctl/source/basicide/layout.cxx |2 - basctl/source/basicide/objdlg.cxx |6 ++-- basctl/source/dlged/dlged.cxx | 36 +-- basctl/source/dlged/dlgedobj.cxx | 24 +- basctl/source/dlged/propbrw.cxx|8 +++--- basic/source/runtime/inputbox.cxx |6 ++-- 11 files changed, 79 insertions(+), 79 deletions(-) New commits: commit 1adb1a320a7e9832a41545bde13fd59d27ce7954 Author: Noel GrandinDate: Mon Feb 12 16:48:57 2018 +0200 loplugin:changetoolsgen in avmedia..basic Change-Id: I4e355ae27b9fad1cc6e8f8f408dbd9e93d7256d7 Reviewed-on: https://gerrit.libreoffice.org/49603 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/avmedia/source/viewer/mediawindow.cxx b/avmedia/source/viewer/mediawindow.cxx index a3a61feaa2c5..df416bb96db7 100644 --- a/avmedia/source/viewer/mediawindow.cxx +++ b/avmedia/source/viewer/mediawindow.cxx @@ -328,8 +328,8 @@ bool MediaWindow::isMediaURL( const OUString& rURL, const OUString& rReferer, bo { const awt::Size aAwtSize( xPlayer->getPreferredPlayerWindowSize() ); -pPreferredSizePixel->Width() = aAwtSize.Width; -pPreferredSizePixel->Height() = aAwtSize.Height; +pPreferredSizePixel->setWidth( aAwtSize.Width ); +pPreferredSizePixel->setHeight( aAwtSize.Height ); } } } diff --git a/avmedia/source/viewer/mediawindow_impl.cxx b/avmedia/source/viewer/mediawindow_impl.cxx index c8af35df34bf..1d1f5fe946cb 100644 --- a/avmedia/source/viewer/mediawindow_impl.cxx +++ b/avmedia/source/viewer/mediawindow_impl.cxx @@ -296,8 +296,8 @@ Size MediaWindowImpl::getPreferredSize() const { awt::Size aPrefSize( mxPlayer->getPreferredPlayerWindowSize() ); -aRet.Width() = aPrefSize.Width; -aRet.Height() = aPrefSize.Height; +aRet.setWidth( aPrefSize.Width ); +aRet.setHeight( aPrefSize.Height ); } return aRet; @@ -532,7 +532,7 @@ void MediaWindowImpl::Resize() const sal_Int32 nControlHeight = mpMediaWindowControl->GetSizePixel().Height(); const sal_Int32 nControlY = std::max(aCurSize.Height() - nControlHeight - nOffset, 0L); -aPlayerWindowSize.Height() = (nControlY - (nOffset << 1)); +aPlayerWindowSize.setHeight( nControlY - (nOffset << 1) ); mpMediaWindowControl->SetPosSizePixel(Point(nOffset, nControlY ), Size(aCurSize.Width() - (nOffset << 1), nControlHeight)); } if (mpChildWindow) @@ -613,13 +613,13 @@ void MediaWindowImpl::Paint(vcl::RenderContext& rRenderContext, const tools::Rec if (fLogoWH < (double(aVideoRect.GetWidth()) / aVideoRect.GetHeight())) { -aLogoSize.Width() = long(aVideoRect.GetHeight() * fLogoWH); -aLogoSize.Height() = aVideoRect.GetHeight(); +aLogoSize.setWidth( long(aVideoRect.GetHeight() * fLogoWH) ); +aLogoSize.setHeight( aVideoRect.GetHeight() ); } else { -aLogoSize.Width() = aVideoRect.GetWidth(); -aLogoSize.Height()= long(aVideoRect.GetWidth() / fLogoWH); +aLogoSize.setWidth( aVideoRect.GetWidth() ); +aLogoSize.setHeight( long(aVideoRect.GetWidth() / fLogoWH) ); } } diff --git a/basctl/source/basicide/baside2.cxx b/basctl/source/basicide/baside2.cxx index a2415818def2..43d7d0fd9f19 100644 --- a/basctl/source/basicide/baside2.cxx +++ b/basctl/source/basicide/baside2.cxx @@ -131,7 +131,7 @@ void lcl_PrintHeader( Printer* pPrinter, sal_uInt16 nPages, sal_uInt16 nCurPage, { aFont.SetWeight( WEIGHT_NORMAL ); pPrinter->SetFont( aFont ); -aPos.X() += pPrinter->GetTextWidth( rTitle ); +aPos.setX( aPos.X() + pPrinter->GetTextWidth( rTitle ) ); if( bOutput ) { @@ -810,8 +810,8 @@ sal_Int32 ModulWindow::FormatAndPrint( Printer* pPrinter, sal_Int32 nPrintPage ) } Size aPaperSz = pPrinter->GetOutputSize(); -aPaperSz.Width() -= (Print::nLeftMargin + Print::nRightMargin); -aPaperSz.Height() -= (Print::nTopMargin + Print::nBottomMargin); +aPaperSz.setWidth( aPaperSz.Width() - (Print::nLeftMargin + Print::nRightMargin) ); +aPaperSz.setHeight( aPaperSz.Height() - (Print::nTopMargin + Print::nBottomMargin) ); // nLinepPage is not
[Libreoffice-commits] core.git: 2 commits - filter/source
filter/source/graphicfilter/ipbm/ipbm.cxx | 55 +- filter/source/graphicfilter/iras/iras.cxx | 45 2 files changed, 34 insertions(+), 66 deletions(-) New commits: commit 5ea3a708c7d6a8088e438e021a07e5a6508daa74 Author: Noel GrandinDate: Mon Feb 12 11:04:00 2018 +0200 use RawBitmap in RASReader part of making Bitmap an internal detail of vcl Change-Id: I72947ac6b59f251db93ff176d28fa840ab0f52ed Reviewed-on: https://gerrit.libreoffice.org/49581 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/filter/source/graphicfilter/iras/iras.cxx b/filter/source/graphicfilter/iras/iras.cxx index 810915dc09a7..251c3cf480b3 100644 --- a/filter/source/graphicfilter/iras/iras.cxx +++ b/filter/source/graphicfilter/iras/iras.cxx @@ -19,7 +19,7 @@ #include -#include +#include class FilterConfigItem; @@ -50,7 +50,7 @@ private: sal_Int32 mnColorMapType, mnColorMapSize; sal_uInt8 mnRepCount, mnRepVal; // RLE Decoding -boolImplReadBody(BitmapWriteAccess * pAcc); +boolImplReadBody(vcl::bitmap::RawBitmap&, std::vector const & rvPalette); boolImplReadHeader(); sal_uInt8 ImplGetByte(); @@ -97,7 +97,7 @@ bool RASReader::ReadRAS(Graphic & rGraphic) return false; bool bPalette(false); -BitmapPalette aPalette; +std::vector aPalette; bool bOk = true; if ( mnDstBitsPerPix <= 8 ) // pallets pictures @@ -116,7 +116,7 @@ bool RASReader::ReadRAS(Graphic & rGraphic) if ( ( mnDstColors >= 2 ) && ( ( mnColorMapSize % 3 ) == 0 ) ) { -aPalette.SetEntryCount(mnDstColors); +aPalette.resize(mnDstColors); sal_uInt16 i; sal_uInt8 nRed[256], nGreen[256], nBlue[256]; for ( i = 0; i < mnDstColors; i++ ) m_rRAS.ReadUChar( nRed[ i ] ); @@ -124,7 +124,7 @@ bool RASReader::ReadRAS(Graphic & rGraphic) for ( i = 0; i < mnDstColors; i++ ) m_rRAS.ReadUChar( nBlue[ i ] ); for ( i = 0; i < mnDstColors; i++ ) { -aPalette[i] = BitmapColor(nRed[ i ], nGreen[ i ], nBlue[ i ]); +aPalette[i] = Color(nRed[ i ], nGreen[ i ], nBlue[ i ]); } bPalette = true; } @@ -138,11 +138,11 @@ bool RASReader::ReadRAS(Graphic & rGraphic) if (!bPalette) { mnDstColors = 1 << mnDstBitsPerPix; -aPalette.SetEntryCount(mnDstColors); +aPalette.resize(mnDstColors); for ( sal_uInt16 i = 0; i < mnDstColors; i++ ) { sal_uLong nCount = 255 - ( 255 * i / ( mnDstColors - 1 ) ); -aPalette[i] = BitmapColor(static_cast(nCount), static_cast(nCount), static_cast(nCount)); +aPalette[i] = Color(static_cast(nCount), static_cast(nCount), static_cast(nCount)); } bPalette = true; } @@ -172,22 +172,13 @@ bool RASReader::ReadRAS(Graphic & rGraphic) return false; } -Bitmap aBmp(Size(mnWidth, mnHeight), mnDstBitsPerPix); -Bitmap::ScopedWriteAccess pAcc(aBmp); -if (!pAcc) -return false; - -if (bPalette) -{ -pAcc->SetPalette(aPalette); -} - +vcl::bitmap::RawBitmap aBmp(Size(mnWidth, mnHeight)); // read in the bitmap data -mbStatus = ImplReadBody(pAcc.get()); +mbStatus = ImplReadBody(aBmp, aPalette); if ( mbStatus ) -rGraphic = aBmp; +rGraphic = vcl::bitmap::CreateFromData(std::move(aBmp)); return mbStatus; } @@ -228,7 +219,7 @@ bool RASReader::ImplReadHeader() return mbStatus; } -bool RASReader::ImplReadBody(BitmapWriteAccess * pAcc) +bool RASReader::ImplReadBody(vcl::bitmap::RawBitmap& rBitmap, std::vector const & rvPalette) { sal_Int32 x, y; sal_uInt8nRed, nGreen, nBlue; @@ -239,7 +230,6 @@ bool RASReader::ImplReadBody(BitmapWriteAccess * pAcc) sal_uInt8 nDat = 0; for (y = 0; y < mnHeight && mbStatus; ++y) { -Scanline pScanline = pAcc->GetScanline(y); for (x = 0; x < mnWidth && mbStatus; ++x) { if (!(x & 7)) @@ -248,9 +238,9 @@ bool RASReader::ImplReadBody(BitmapWriteAccess * pAcc) if (!m_rRAS.good()) mbStatus = false; } -pAcc->SetPixelOnData(pScanline, x, BitmapColor( +rBitmap.SetPixel(y, x, rvPalette[ sal::static_int_cast< sal_uInt8 >( -nDat >> ( ( x & 7 ) ^ 7 )) )); +nDat >> ( ( x & 7 ) ^ 7 ))] ); }
[Libreoffice-commits] core.git: filter/source include/vcl
filter/source/graphicfilter/icgm/actimpr.cxx |2 filter/source/msfilter/msdffimp.cxx | 259 +-- include/vcl/BitmapTools.hxx |2 3 files changed, 130 insertions(+), 133 deletions(-) New commits: commit 3bc228a1dd2f85e92ca341d16cb86e6eedef5eb7 Author: Noel GrandinDate: Mon Feb 12 10:48:13 2018 +0200 use RawBitmap and BitmapEx in DffPropertyReader part of making Bitmap an internal feature of vcl Change-Id: I2945005b9070bc13844c02f8ecaa349920d151fe Reviewed-on: https://gerrit.libreoffice.org/49579 Tested-by: Jenkins Reviewed-by: Noel Grandin diff --git a/filter/source/graphicfilter/icgm/actimpr.cxx b/filter/source/graphicfilter/icgm/actimpr.cxx index 5ec28efb1a89..fc701f64f570 100644 --- a/filter/source/graphicfilter/icgm/actimpr.cxx +++ b/filter/source/graphicfilter/icgm/actimpr.cxx @@ -555,7 +555,7 @@ void CGMImpressOutAct::DrawBitmap( CGMBitmapDescriptor* pBmpDesc ) if ( pBmpDesc->mbVMirror ) nMirr |= BmpMirrorFlags::Vertical; if ( nMirr != BmpMirrorFlags::NONE ) -pBmpDesc->mxBitmap.Mirror( nMirr ); // FIXME +pBmpDesc->mxBitmap.Mirror( nMirr ); mpCGM->ImplMapPoint( aOrigin ); mpCGM->ImplMapX( fdx ); diff --git a/filter/source/msfilter/msdffimp.cxx b/filter/source/msfilter/msdffimp.cxx index ffd6cfda2ef0..6743f503480e 100644 --- a/filter/source/msfilter/msdffimp.cxx +++ b/filter/source/msfilter/msdffimp.cxx @@ -42,6 +42,7 @@ #include #include #include +#include #include "viscache.hxx" // SvxItem-Mapping. Is needed to successfully include the SvxItem-Header @@ -,164 +1112,160 @@ void ApplyRectangularGradientAsBitmap( const SvxMSDffManager& rManager, SvStream double fFocusX = rManager.GetPropertyValue( DFF_Prop_fillToRight, 0 ) / 65536.0; double fFocusY = rManager.GetPropertyValue( DFF_Prop_fillToBottom, 0 ) / 65536.0; -Bitmap aBitmap( aBitmapSizePixel, 24 ); -BitmapWriteAccess* pAcc = aBitmap.AcquireWriteAccess(); -if ( pAcc ) +vcl::bitmap::RawBitmap aBitmap(aBitmapSizePixel); + +for ( long nY = 0; nY < aBitmapSizePixel.Height(); nY++ ) { -for ( long nY = 0; nY < aBitmapSizePixel.Height(); nY++ ) +for ( long nX = 0; nX < aBitmapSizePixel.Width(); nX++ ) { -Scanline pScanline = pAcc->GetScanline(nY); -for ( long nX = 0; nX < aBitmapSizePixel.Width(); nX++ ) -{ -double fX = static_cast< double >( nX ) / aBitmapSizePixel.Width(); -double fY = static_cast< double >( nY ) / aBitmapSizePixel.Height(); +double fX = static_cast< double >( nX ) / aBitmapSizePixel.Width(); +double fY = static_cast< double >( nY ) / aBitmapSizePixel.Height(); -double fD, fDist; -if ( fX < fFocusX ) +double fD, fDist; +if ( fX < fFocusX ) +{ +if ( fY < fFocusY ) { -if ( fY < fFocusY ) +if ( fX > fY ) { -if ( fX > fY ) -{ -fDist = fY; -fD = fFocusY; -} -else -{ -fDist = fX; -fD = fFocusX; -} +fDist = fY; +fD = fFocusY; } else { -if ( fX > ( 1 - fY ) ) -{ -fDist = 1 - fY; -fD = 1 - fFocusY; -} -else -{ -fDist = fX; -fD = fFocusX; -} +fDist = fX; +fD = fFocusX; } } else { -if ( fY < fFocusY ) +if ( fX > ( 1 - fY ) ) { -if ( ( 1 - fX ) > fY ) -{ -fDist = fY; -fD = fFocusY; -} -else -{ -fDist = 1 - fX; -fD = 1 - fFocusX; -} +
[Libreoffice-bugs] [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 Yousuf Philips (jay)changed: What|Removed |Added Blocks|108743 |115673 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108743 [Bug 108743] [META] Find toolbar bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=115673 [Bug 115673] [META] Navigate By toolbar control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115673] [META] Navigate By toolbar control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115673 Yousuf Philips (jay)changed: What|Removed |Added Depends on||115666 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115666 [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108743 Yousuf Philips (jay)changed: What|Removed |Added Depends on|115666 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115666 [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115673] [META] Navigate By toolbar control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115673 Yousuf Philips (jay)changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Alias||Navigate-By -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108743 Yousuf Philips (jay)changed: What|Removed |Added Depends on||115673 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115673 [Bug 115673] [META] Navigate By toolbar control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115673] New: [META] Navigate By toolbar control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115673 Bug ID: 115673 Summary: [META] Navigate By toolbar control bugs and enhancements Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: philip...@hotmail.com Blocks: 108743 Navigate By (.uno:NavElement) toolbar control was added in bug 79167 to the Find Toolbar in LibreOffice 6.0. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108743 [Bug 108743] [META] Find toolbar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: vcl/source
vcl/source/window/builder.cxx |1 + 1 file changed, 1 insertion(+) New commits: commit c6b702cdd50003f756247e6352357e535f7167a0 Author: Michael MeeksDate: Tue Feb 13 07:11:57 2018 +0100 Add missing SVLIBRARY include. Change-Id: I10a1d9430f38499d77ad528ef98cff260873d4de diff --git a/vcl/source/window/builder.cxx b/vcl/source/window/builder.cxx index 8deda5a66b83..353db7d5c633 100644 --- a/vcl/source/window/builder.cxx +++ b/vcl/source/window/builder.cxx @@ -44,6 +44,7 @@ #include #include #include +#include #ifdef DISABLE_DYNLOADING #include ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 115669] Reference to another sheet don' t set when row and column was fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=115669 Andrewchanged: What|Removed |Added Version|unspecified |Inherited From OOo --- Comment #2 from Andrew --- AOo 4.1.2 - same behavior. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95848] FORMATTING: Numbering list in DOCX does not continue previous numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=95848 --- Comment #6 from Justin L--- The key to fixing this will be to pruning out identical list styles. In this case, both style1 and style6 both use abstract style 24 with no modifications. #para style Пункт-3 using list numId=6 ilvl=2 B w:t>C -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115672] New: libreoffice-6.0.1.1 fails to compile with system gpgme-1.9.0
https://bugs.documentfoundation.org/show_bug.cgi?id=115672 Bug ID: 115672 Summary: libreoffice-6.0.1.1 fails to compile with system gpgme-1.9.0 Product: LibreOffice Version: 6.0.1.1 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: john.frank...@outlook.com Description: 1. configure/make looks for headers in include rather than include/gpgme++ 2. make fails with: [CXX] xmlsecurity/source/gpg/CertificateImpl.cxx [CXX] xmlsecurity/source/gpg/CipherContext.cxx In file included from /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:12:0: /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.hxx:36:5: error: 'GpgME' does not name a type GpgME::Key m_pKey; ^ In file included from /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:12:0: /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.hxx:85:25: error: 'GpgME' has not been declared void setCertificate(GpgME::Context* ctx, const GpgME::Key& key); ^ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.hxx:85:39: error: expected ',' or '...' before '*' token void setCertificate(GpgME::Context* ctx, const GpgME::Key& key); ^ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.hxx:86:11: error: 'GpgME' does not name a type const GpgME::Key* getCertificate() const; ^ [CXX] xmlsecurity/source/gpg/DigestContext.cxx [CXX] xmlsecurity/source/gpg/SecurityEnvironment.cxx /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In constructor 'CertificateImpl::CertificateImpl()': /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:30:5: error: class 'CertificateImpl' does not have any field named 'm_pKey' m_pKey() ^~ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In member function 'virtual rtl::OUString CertificateImpl::getIssuerName()': /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:53:34: error: 'm_pKey' was not declared in this scope const GpgME::UserID userId = m_pKey.userID(0); ^~ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:53:34: note: suggested alternative: 'ecKey' const GpgME::UserID userId = m_pKey.userID(0); ^~ ecKey /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In member function 'virtual com::sun::star::util::DateTime CertificateImpl::getNotValidBefore()': /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:83:34: error: 'm_pKey' was not declared in this scope const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:83:34: note: suggested alternative: 'ecKey' const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ ecKey /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In member function 'virtual com::sun::star::util::DateTime CertificateImpl::getNotValidAfter()': /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:92:34: error: 'm_pKey' was not declared in this scope const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:92:34: note: suggested alternative: 'ecKey' const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ ecKey /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In member function 'virtual rtl::OUString CertificateImpl::getSubjectPublicKeyAlgorithm()': /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:131:34: error: 'm_pKey' was not declared in this scope const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx:131:34: note: suggested alternative: 'ecKey' const GpgME::Subkey subkey = m_pKey.subkey(0); ^~ ecKey /mnt/sdc8/usr/src/libreoffice-6.0.1.1/xmlsecurity/source/gpg/CertificateImpl.cxx: In member function 'virtual rtl::OUString
[Libreoffice-bugs] [Bug 95848] FORMATTING: Numbering list in DOCX does not continue previous numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=95848 --- Comment #5 from Justin L--- The key to fixing this will be to pruning out identical list styles. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115671] New: FILEOPEN: MSO OOXML shape incorrectly rendered
https://bugs.documentfoundation.org/show_bug.cgi?id=115671 Bug ID: 115671 Summary: FILEOPEN: MSO OOXML shape incorrectly rendered Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lukebe...@hotmail.com Created attachment 139854 --> https://bugs.documentfoundation.org/attachment.cgi?id=139854=edit Example Callout Steps to reproduce: 1. In MSO insert Rounded Rectangular Callout 2. Save and Open in LO The imported shape in LO is only partially drawn, missing a segment on the side. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115670] New: openfile .docx unnecssary grey box or area beside left vertical box
https://bugs.documentfoundation.org/show_bug.cgi?id=115670 Bug ID: 115670 Summary: openfile .docx unnecssary grey box or area beside left vertical box Product: LibreOffice Version: 6.1.0.0.alpha0+ Master Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Viewer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kris...@grrlz.net open Paul Wilson CRR seminar notice.docx attachment 62036 on bug# 50295 pdf export of docx attachment 74994 bug# 50295 screenshot on lo viewer master daily build https://github.com/kr1shna-opensource/qa/blob/master/docs/_screenshot/50295%20grey%20shadow.png current behaviour: grey area or box beside left vertical box expected behaviour: similar to pdf export tinderbox: buildname: Android-ARM@24-Bytemark-Hosting tinderbox: tree: MASTER tinderbox: pull time 2018-02-12 15:26:16 tinderbox: git sha1s core:9cf2616c5e709b5956ab88dacdfad2003f98 lyf flame 3, android 5.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94819] Fileopen: outline numbering not continued in docx
https://bugs.documentfoundation.org/show_bug.cgi?id=94819 --- Comment #4 from Justin L--- This is a challenging bug. The problem is that for unidentified reasons, PROP_NUMBERING_RULES are written directly into the paragraph. But there are no identifying marks on PROP_NUMBERING_RULES - so it is impossible to tell whether they came from numId=1/WWNum1 and thus whether one or the other is redundant. This is complicated by the fact that Heading X is treated differently by LO - a secret "Outline" list style is used by Tools->Chapter Numbering which on docx import can only be associated with Heading X. I think that PROP_NUMBERING_RULES ought to be replaced by PROP_NUMBERING_STYLE_NAME in most cases. Attempting this led to a lot of failed unit tests however. PROP_NUMBERING_RULES existed already in OOo. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115669] Reference to another sheet don' t set when row and column was fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=115669 kompilainenn <79045_79...@mail.ru> changed: What|Removed |Added Status|UNCONFIRMED |NEW Summary|Reference to sheen don't|Reference to another sheet |set when cell is fixed |don't set when row and ||column was fixed Ever confirmed|0 |1 --- Comment #1 from kompilainenn <79045_79...@mail.ru> --- confirmed for 6.0.0.3 if try to make link to "Sheet2" into row 1 or column A -> link is creating -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115207] Shapes should format text with word wrapping by default
https://bugs.documentfoundation.org/show_bug.cgi?id=115207 Lukechanged: What|Removed |Added Component|Impress |LibreOffice -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115207] Shapes should format text with word wrapping by default
https://bugs.documentfoundation.org/show_bug.cgi?id=115207 Lukechanged: What|Removed |Added Status|UNCONFIRMED |NEW Summary|Call Out forms should |Shapes should format text |format text with word |with word wrapping by |wrapping by default |default Ever confirmed|0 |1 --- Comment #1 from Luke --- We are inconsistent here. In Google Docs, Writer, and MS Word Insert Shape -> Add Text creates a textbox that defaults to wrap. In Google Presentation and PowerPoint, they both set default to wrap text(no need to "Add Text"). The Google and PowerPoint defaults make more sense to me than we use in Impress. It would also make LO more consistent. Confirmed in Version: 6.1.0.0.alpha0+ (x64) Build ID: 3deac9691011711a3b9e50d19499c588af074d7f -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115669] New: Reference to sheen don't set when cell is fixed
https://bugs.documentfoundation.org/show_bug.cgi?id=115669 Bug ID: 115669 Summary: Reference to sheen don't set when cell is fixed Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tenc...@gmail.com Created attachment 139853 --> https://bugs.documentfoundation.org/attachment.cgi?id=139853=edit Sheet with fixed cell When sheet has fixed rows and column, you cannot enter reference to another sheet with mouse selection. To example. In attached sample try to enter "=" in B3 and then click mouse to sheet2 to select any cell, same as B2. It is not work. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104385] FILEOPEN DOCX:VML Cloud Callout Not Imported
https://bugs.documentfoundation.org/show_bug.cgi?id=104385 Lukechanged: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=41 ||466 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 41466] VML Callout shapes are incorrectly imported
https://bugs.documentfoundation.org/show_bug.cgi?id=41466 Lukechanged: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4385 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106541] FILEOPEN: Numbering from custom style based on Heading 1 is not considered in this DOC /DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=106541 --- Comment #7 from Justin L--- Created attachment 139852 --> https://bugs.documentfoundation.org/attachment.cgi?id=139852=edit tdf106541.diff: patch that adds re-numbering to inheriting style This patch at least turns numbering on for TOC Level 1. However, LO’s hidden “Outline” list style is inaccessible to other styles, so “TOC Level 1” style cannot use the same list as the headings. That leads to incorrect numberings. It will take a huge effort to redesign numbering/styles to fix this bug. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106541] FILEOPEN: Numbering from custom style based on Heading 1 is not considered in this DOC /DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=106541 Justin Lchanged: What|Removed |Added Whiteboard|interoperability|interoperability |target:6.1.0| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 67775] FILEOPEN: Incorrect lines connecting shapes (.docx)
https://bugs.documentfoundation.org/show_bug.cgi?id=67775 --- Comment #9 from Luke--- Created attachment 139851 --> https://bugs.documentfoundation.org/attachment.cgi?id=139851=edit Stripped down file with only problematic connector Still reproducible in Version: 6.1.0.0.alpha0+ (x64) Build ID: 3deac9691011711a3b9e50d19499c588af074d7f -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106541] FILEOPEN: Numbering from custom style based on Heading 1 is not considered in this DOC /DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=106541 --- Comment #6 from Commit Notification--- Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ed8221aa0b1550834f8ca18ca3af21f2a41e678d tdf#106541 preventative unit test: don't force inheritance It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106541] FILEOPEN: Numbering from custom style based on Heading 1 is not considered in this DOC /DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=106541 Commit Notificationchanged: What|Removed |Added Whiteboard|interoperability|interoperability ||target:6.1.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/qa
sw/qa/extras/ooxmlexport/data/tdf106541_noinheritChapterNumbering.odt |binary sw/qa/extras/ooxmlexport/ooxmlexport.cxx | 17 ++ 2 files changed, 17 insertions(+) New commits: commit ed8221aa0b1550834f8ca18ca3af21f2a41e678d Author: Justin LuthDate: Sat Feb 10 13:38:34 2018 +0300 tdf#106541 preventative unit test: don't force inheritance In LO, it appears to be impossible for a style based on a Chapter Numbering List style to inherit the numbering and outline level. Ensure that any fix for Word-authored documents that DO inherit this don't break round-tripping natively created docx files. Change-Id: I0cd4c25fbc7cd60346fcd949d5a3b89c2b311dbd Reviewed-on: https://gerrit.libreoffice.org/49544 Tested-by: Jenkins Reviewed-by: Justin Luth diff --git a/sw/qa/extras/ooxmlexport/data/tdf106541_noinheritChapterNumbering.odt b/sw/qa/extras/ooxmlexport/data/tdf106541_noinheritChapterNumbering.odt new file mode 100644 index ..2408ecf550e0 Binary files /dev/null and b/sw/qa/extras/ooxmlexport/data/tdf106541_noinheritChapterNumbering.odt differ diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport.cxx b/sw/qa/extras/ooxmlexport/ooxmlexport.cxx index 00448c979dbe..b7acdffbdc16 100644 --- a/sw/qa/extras/ooxmlexport/ooxmlexport.cxx +++ b/sw/qa/extras/ooxmlexport/ooxmlexport.cxx @@ -346,6 +346,23 @@ DECLARE_OOXMLEXPORT_TEST(testNumberingFont, "numbering-font.docx") CPPUNIT_ASSERT_EQUAL(OUString("Verdana"), getProperty(xStyle, "CharFontName")); } +DECLARE_OOXMLEXPORT_TEST(testTdf106541_noinheritChapterNumbering, "tdf106541_noinheritChapterNumbering.odt") +{ +// in LO, it appears that styles based on the Chapter Numbering style explicitly sets the +// numbering style/outline level to 0 by default, and prevents inheriting directly from "Outline" style. +// Adding this preventative unit test to ensure that any fix for tdf106541 doesn't make incorrect assumptions. +CPPUNIT_ASSERT_EQUAL(OUString("Outline"), getProperty(getParagraph(1), "NumberingStyleName")); +OUString sPara3NumberingStyle = getProperty(getParagraph(3), "NumberingStyleName"); +CPPUNIT_ASSERT_EQUAL(sPara3NumberingStyle, getProperty(getParagraph(4), "NumberingStyleName")); + +xmlDocPtr pXmlDoc = parseLayoutDump(); +assertXPath(pXmlDoc, "//body/txt/Special", 3); //three of the four paragraphs have numbering +assertXPath(pXmlDoc, "//body/txt[1]/Special", "rText", "1"); +assertXPath(pXmlDoc, "//body/txt[2]/Special", 0); //second paragraph style disables numbering +assertXPath(pXmlDoc, "//body/txt[3]/Special", "rText", "I."); +assertXPath(pXmlDoc, "//body/txt[4]/Special", "rText", "II."); +} + DECLARE_OOXMLEXPORT_TEST(testTdf53856_conflictingStyle, "tdf53856_conflictingStyle.docx") { // The "Text" style conflicted with builtin paragraph style Caption -> Text ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 49881] VML Autoshapes created in MS Office not imported at all in LO 3.5.3, FILEOPEN, FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=49881 Lukechanged: What|Removed |Added Summary|Autoshapes created in MS|VML Autoshapes created in |Office not imported at all |MS Office not imported at |in LO 3.5.3, FILEOPEN, |all in LO 3.5.3, FILEOPEN, |FORMATTING |FORMATTING -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 49881] Autoshapes created in MS Office not imported at all in LO 3.5.3, FILEOPEN , FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=49881 --- Comment #10 from Luke--- Created attachment 139850 --> https://bugs.documentfoundation.org/attachment.cgi?id=139850=edit Stripped down test document Stripped down version to demonstrate the issues. This is likely a VML issue. When file is upgraded to OOXML, the shapes are correctly imported. Reproducible in Version: 6.1.0.0.alpha0+ (x64) Build ID: 3deac9691011711a3b9e50d19499c588af074d7f -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 41466] VML Callout shapes are incorrectly imported
https://bugs.documentfoundation.org/show_bug.cgi?id=41466 Lukechanged: What|Removed |Added Summary|Missing notes and moved |VML Callout shapes are |components after importing |incorrectly imported |.docx file | --- Comment #18 from Luke --- This is likely a VML issue. When attachment 53047 is upgraded to OOXML, the Callout shapes are correctly imported. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105749] Document-level snap and grid options not superseding global-level options
https://bugs.documentfoundation.org/show_bug.cgi?id=105749 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 95250] Undo of picture deleting.
https://bugs.documentfoundation.org/show_bug.cgi?id=95250 --- Comment #4 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 82926] scroll bar ineffective in Content field of Form Properties dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=82926 --- Comment #6 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 101109] FILESAVE Exporting a Sheet containing a scrollbar control to XLS will result in dysfunctional slider having 0 max value.
https://bugs.documentfoundation.org/show_bug.cgi?id=101109 --- Comment #3 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 104983] Dragging on Slides sidebar vertically on a Windows touchscreen moving a page instead of scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=104983 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105753] The setting "Mirror on even pages" for frames is misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=105753 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105961] TABLE/GUI: Numeric and Decimal doesn' t allow input of more than 17 digits
https://bugs.documentfoundation.org/show_bug.cgi?id=105961 --- Comment #3 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105674] Calc will give a non-clickable error box when adding a gallery item which isn 't accessible anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=105674 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105870] EDITING: start and end buttons in navigator do the wrong thing
https://bugs.documentfoundation.org/show_bug.cgi?id=105870 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103109] Document scrollbar has positioning issues when contracting or uncontracting the Sidebar in chart edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=103109 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105760] TextCursor.gotoPreviousWord fails when quote is at start of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=105760 --- Comment #3 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 58141] VIEWING: Scrollbar freezes on fast scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=58141 --- Comment #8 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 99923] Table: Can' t set bottom border without top border after a page break
https://bugs.documentfoundation.org/show_bug.cgi?id=99923 --- Comment #2 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86568] BASIC IDE: horizontal scrollbar isn’t next to the box it controls
https://bugs.documentfoundation.org/show_bug.cgi?id=86568 --- Comment #3 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105940] An image within a selection isn't really selected when it' s anchored to page, so cut and paste isn't working
https://bugs.documentfoundation.org/show_bug.cgi?id=105940 --- Comment #5 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105743] Textflow changes on hiding whitespace && two columns-layout
https://bugs.documentfoundation.org/show_bug.cgi?id=105743 --- Comment #3 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84704] SIDEBAR: Slow 1-pixel scrollbar scrolling when clicking in empty space or arrow buttons
https://bugs.documentfoundation.org/show_bug.cgi?id=84704 --- Comment #16 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 59348] UI: Vertical and horizontal scroll bar of a data grid control doesn' t resize when zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=59348 --- Comment #8 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86390] File Type List has no scrollbar
https://bugs.documentfoundation.org/show_bug.cgi?id=86390 --- Comment #14 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 105959] FORMATTING in Calc --change case does not happen across cells
https://bugs.documentfoundation.org/show_bug.cgi?id=105959 --- Comment #5 from QA Administrators--- ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 --- Comment #2 from Kevin Suo--- Note that this happens not only for tables, but also for any other objects such as shapes, images etc. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 Kevin Suochanged: What|Removed |Added Keywords||needsUXEval Status|UNCONFIRMED |NEW CC||suokunl...@126.com Ever confirmed|0 |1 --- Comment #1 from Kevin Suo --- Reproduced, but I do not think this is a bug. When cursor is in the comment, the comment area is active. Since there is no table inside the comment, noting is found, that is why there is no reaction when you click the up and down arrow button. If you put the cursor back to the text area, then find the tables with up and down arrow buttons work perfect. Version: 6.0.0.3 (x64) Build ID:64a0f66915f38c6217de274f0aa8e15618924765 CPU 线程:4; 操作系统:Windows 10.0; UI 渲染:默认; 区域语言:zh-CN (zh_CN); Calc: group I mark it as NEW, and added keyword needsUXEval. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98079] FILESAVE CALC crashes sporadically when saving multiple sheet workbook ( Win x64)
https://bugs.documentfoundation.org/show_bug.cgi?id=98079 Kevin Suochanged: What|Removed |Added CC||suokunl...@126.com --- Comment #32 from Kevin Suo --- No crash for me in: Version: 6.0.0.3 (x64) Build ID:64a0f66915f38c6217de274f0aa8e15618924765 CPU 线程:4; 操作系统:Windows 10.0; UI 渲染:默认; 区域语言:zh-CN (zh_CN); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115668] Improvement Suggestions for LibreOffice AutoCorrect Function Word Completion and Quick Starter
https://bugs.documentfoundation.org/show_bug.cgi?id=115668 J. Schultechanged: What|Removed |Added Alias||Dallun511, Ferewo -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115668] Improvement Suggestions for LibreOffice AutoCorrect Function Word Completion and Quick Starter
https://bugs.documentfoundation.org/show_bug.cgi?id=115668 J. Schultechanged: What|Removed |Added Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115668] New: Improvement Suggestions for LibreOffice AutoCorrect Function Word Completion and Quick Starter
https://bugs.documentfoundation.org/show_bug.cgi?id=115668 Bug ID: 115668 Summary: Improvement Suggestions for LibreOffice AutoCorrect Function Word Completion and Quick Starter Product: LibreOffice Version: 6.0.1.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dallun...@outlook.de Description: Improvement Suggestions for LibreOffice Writer AutoCorrect Function Word Completion and Quick Starter. Steps to Reproduce: Dear LibreOffice Team I would like to suggest a few suggestions for the LibreOffice Writer, which I would be very happy if you could fulfill them in the upcoming release. Proposal number 1 is a revision of the "AutoCorrect Function Word Completion", which stores words that are longer than six letters and adds them as needed. Example: "LibreOffice", the word has more than six letters, which is why the word completion remembers the word and saves it for a new need. The second time you need to write only "Libr" and the word extension proposes "LibreOffice" before and pressing the Enter key is "LibreOffice" in the text. I come now to my suggestion, because the word supplement also remembers words that occur only once in the text, so that words that occur more often in the text and much more typed are not even suggested first, which I think is a pity because I have this Use the function daily. The word supplement needs to be further developed so that it remembers words that occur more often in the text than once and then never again. In addition, the word completion remembers spelling mistakes or typos, such as "Sie geht heute nach Hause. Er geht nach Hause." If you hit "Zuhause" now, the word "Zuhause." Suggests what's no advantage, because it's grammatically wrong, as well also words with numbers are wrong. For example, one wanted to write "verlassen" but instead one accidentally "verliert" remembering the word completion, even though it is completely wrong, and yet the wrong word is always suggested first. I offer that the word completion be reprogrammed, that the word completion will not remember any words with dots, hyphens, typos and spelling errors, because nobody needs words like "Zuhause .", "Auto" Cellar, example. Verlie0en, gro0 "Der Bindestrich sollte auch beim Wortzusatz ignoriert werden, wenn die Wörter dort enden, denn Wörter wie" sick, police and fire trucks "are abbreviations in the German language because they would not have to write out and rather become themselves That's why I ask that the word supplement no longer suggests this in the future. That was my first suggestion. Proposal number 2 is a memory issue when a document is closed. LibreOffice has the function that it starts with the start of the PC, which I like very much, which makes my documents load faster, but when I close my document, it stays in memory forever, which is very annoying because My documents consume 2.6 GB of RAM, which I can only recover if the Task Manager completely exits LibreOffice, which also stops LibreOffice's quick-start and thus loses its advantage. I ask that when closing a document, the RAM released back to the system without me even have to finish the task. That was my second suggestion. Proposal number 3 is about the performance of LibreOffice Writer. I write documents that have over 600 thousand words and are over 700 pages long, which causes the writer to lose performance and no longer run smoothly, even sometimes threatening to crash if I try to find spelling mistakes with the spell checker, which takes ten to fifteen minutes Because of the size of the document, even though I have a power PC and the CPU gets bored, LibreOffice is not usable at all during the spellchecker, which prevents me from reading or editing another document. The performance has to be improved somehow, so this does not happen. It is very annoying when LibreOffice crashes during the process, because the spell checker does not follow and you have to start over again because it could not be saved. That was my third suggestion. I come now to two requests, which I would be happy if they appear in the upcoming version, the first is the request that there is a function, which LibreOffice stops remembering the last open documents, which I personally do not want because I share my PC and therefore everyone can see what I've been working on recently. My last request is the table function in the Writer, which defaults to the English language, although LibreOffice was installed in German, which means I always have to change the language to German by hand, so that spelling errors in the German language are checked and not the English, which is not comfortable. Thank you for your attention and look forward to the upcoming releases of
[Libreoffice-bugs] [Bug 115616] Crash in: framework::ToolBarManager::UpdateControllers()
https://bugs.documentfoundation.org/show_bug.cgi?id=115616 Oliver Heardchanged: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Oliver Heard --- It's a tough one because I'm not sure what actually triggered the crash due to the (possible) touch pad slippage. Therefore reproducing it intentionally is unlikely. I'd hoped the crash dump would have enough info for those familiar with the code base to see any immediate problems. Having gone back in and finished customising the toolbars it hasn't crashed again. I'll change the status back to UNCONFIRMED in case you guys want to do anything more with it but if it does ever happen again (I still need to customise a few other programs) I'll return with more details. In the meantime I don't see any harm in it being set to RESOLVED for bookkeeping purposes if that suits you. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115210] Impress: Slideshow flickering on Windows 7
https://bugs.documentfoundation.org/show_bug.cgi?id=115210 Technologovchanged: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Technologov --- Version: 6.0.0.2 Build ID: 06b618bb6f431d27fd2def25aa19c833e29b61cd CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-GB (en_GB); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111474] UI: Row numbers are clipped when OpenGL is used
https://bugs.documentfoundation.org/show_bug.cgi?id=111474 V Stuart Footechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114743] PRINT: angled text does not display
https://bugs.documentfoundation.org/show_bug.cgi?id=114743 Adolfo Jaymechanged: What|Removed |Added Whiteboard|target:6.1.0| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72174] convert_add() from "at" and "atm" to "Pa" gives the same answer.
https://bugs.documentfoundation.org/show_bug.cgi?id=72174 --- Comment #26 from Eike Rathke--- No, I meant an additional unit symbol to be specified by ODFF. Sorry for confusion. And yes, that would mean an "at-correct" symbol because "at" is spoiled forever and either calculated as Excel does and specified, or not calculated at all as Gnumeric does. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111474] UI: Row numbers are clipped when OpenGL is used
https://bugs.documentfoundation.org/show_bug.cgi?id=111474 kyamachanged: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #9 from kyama --- Confirmed fixed in Version: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 8; OS:Windows 10.0; UI render: GL; Locale: ja-JP (ja_JP); Calc: group Thank you! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115667] Objects partly outside of slide get moved/ shrinked fully onto slide in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=115667 --- Comment #2 from Stefan Breunig--- Created attachment 139849 --> https://bugs.documentfoundation.org/attachment.cgi?id=139849=edit example as rendered in presentation mode -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115667] Objects partly outside of slide get moved/ shrinked fully onto slide in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=115667 --- Comment #1 from Stefan Breunig--- Created attachment 139848 --> https://bugs.documentfoundation.org/attachment.cgi?id=139848=edit example as rendered in edit mode -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115667] New: Objects partly outside of slide get moved/ shrinked fully onto slide in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=115667 Bug ID: 115667 Summary: Objects partly outside of slide get moved/shrinked fully onto slide in presentation mode Product: LibreOffice Version: 6.0.1.1 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stefan-libreoff...@breunig.xyz Description: Any object that is partly on a slide and partly outside of it gets moved/shrunk back onto the slide when viewed in presentation mode. Steps to Reproduce: 1. create shape or text area 2. place it so that it has visible parts both within the slide and outside of it 3. goto presentation mode Actual Results: Objects get pushed fully back onto slide Expected Results: Parts out of the slide in edit mode should be cut off in presentation mode as well Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.0.1.1 Build ID: 1:6.0.1-1 CPU threads: 4; OS: Linux 4.14; UI render: default; VCL: x11; Locale: de-DE (de_DE.UTF-8); Calc: group I'm using the version from the Debian repositories User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: vcl/source
vcl/source/window/builder.cxx |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit adff6293ce22d84e5a380aa649e7d0f0ffdc4d80 Author: Eike RathkeDate: Tue Feb 13 00:22:44 2018 +0100 Blind fix for MERGELIBS build It's g_aMergedLib instead of g_aMergedLibs, and osl::Module is not a unique_ptr or somesuch.. commit 707f787cd991f9c59712cd3020d127d09605c792 AuthorDate: Sun Feb 11 00:01:44 2018 +0100 CommitDate: Mon Feb 12 22:27:55 2018 +0100 Change-Id: I1f0266d189546dfe3b0d9eb449c878daebbf0da6 diff --git a/vcl/source/window/builder.cxx b/vcl/source/window/builder.cxx index becc75d63f41..8deda5a66b83 100644 --- a/vcl/source/window/builder.cxx +++ b/vcl/source/window/builder.cxx @@ -1115,7 +1115,7 @@ void VclBuilder::preload() #ifndef DISABLE_DYNLOADING #if ENABLE_MERGELIBS -g_aMergedLibs->loadRelative(, SVLIBRARY("merged")); +g_aMergedLib.loadRelative(, SVLIBRARY("merged")); #endif // find -name '*ui*' | xargs grep 'class=".*lo-' | // sed 's/.*class="//' | sed 's/-.*$//' | sort | uniq @@ -1643,8 +1643,8 @@ VclPtr VclBuilder::makeObject(vcl::Window *pParent, const OString & bool ok = false; #if ENABLE_MERGELIBS if (!g_aMergedLib.is()) -g_aMergedLib->loadRelative(, SVLIBRARY("merged")); -ok = g_aMergedLib->getFunctionSymbol(sFunction); +g_aMergedLib.loadRelative(, SVLIBRARY("merged")); +ok = g_aMergedLib.getFunctionSymbol(sFunction); #endif if (!ok) ok = pModule->loadRelative(, sModule); ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 115662] LibreOffice can't build with google-roboto-fonts installed
https://bugs.documentfoundation.org/show_bug.cgi?id=115662 Stephan van den Akkerchanged: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Stephan van den Akker --- I can confirm this problem. While building LOdev (master) on openSuSE Tumbleweed and openSuSE 42.2 (64-bit) the test for tdf@108947 has been failing for at least several months now. Removing the roboto fonts the build of Version: 6.1.0.0.alpha0+ Build ID: d9fc18d5a797972ba182fbcae941535a50098dcb CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); Calc: CL now works on Tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
Re: Implementing accessibility non-regression check tool
Hello, So there was a presentation about this tool at FOSDEM, the video recording is already available on https://fosdem.org/2018/schedule/event/ode_testing/ Basically, the tool (improved a bit since FOSDEM) is currently reporting about 8000 warnings, i.e. 8 per file on average. I have attached the evolution over time, we clearly see the migration to .ui files during 4.0 :) Looking at a few .ui files, there are some false positives, but not so many, and they are usually based on semantic, so they wouldn't be detectable anyway, one needs to mark them as such anyway. There are some errors too (parsing error or missing targets), they are quite rare. We have discussed with various people at FOSDEM about their feeling on it, and thought how to proceed from there. Our goal is to achieve zero-regression and fixing existing issues on the long run, while avoiding to bother developers too hard. Our fears is that the tool might produce too many false positives, that people need to be taught how to fix the true positives, and that we don't want to do several a11y-fix passes over all .ui files. We thought about the following planning, step by step: - Add to the build process error checking (only the hard errors such as bogus target names). There are only a few existing issues, so we can fix them alongside, and people won't introduce many, so making them errors already shouldn't be bothering. - Add to make check warning checking, one kind of warning at a time, with suppression files alongside, so that the tool only displays " suppressed warnings" and new warnings introduced by developers from there. These warnings would point to wiki pages explaining the ins and outs of the issues and how to fix them. Introducing warnings one kind of warning at a time should leave time to developers for learning the accessibility rules progressively. It should also allow to observe how well false positives are treated before enabling all warnings. - When we get more and more confident that warnings are solid, we can make them fatal (one kind at a time), to really enforce non-regression. - At the same time, we would work on fixing issues raised by the tool on some set of dialog boxes, to check that fixing them does provide good accessibility, and to what extent we want to introduce more warnings to reach good accessibility. - At some point we'll get confident that we won't introduce other big classes of warnings over hundreds of .ui files. That's the point where we can say "ok, let's start fixing the existing issues over all .ui files once for good". We can then run through .ui files one by one, fixing the issues and removing the corresponding suppression lines. These could be used as "easy hacks" entries, they are usually just a few lines to fix. The progression of all of this could be monitored with statistics reported e.g. in the minutes of ESC calls. What do people think about this plan? Samuel libreoffice.eps Description: PostScript document ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Bug Report
Hello, I'm a Libreoffice. I'ts just for reporting a bug in LibreOffice for Debian based systems (running on Elementary OS -> Ubuntu 16.04). There is a problem in the returning from the edition of an OLE object, when press scape, LibreOffice crashes, also in secure mode. It also fails to insert special characters in OLE mode. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 80768] Cell ranges with the same Conditional Formatting should be consolidated to 1 range.
https://bugs.documentfoundation.org/show_bug.cgi?id=80768 --- Comment #34 from Simon--- Yeah, new fancy design. But no time for function? Please give the user the opportunity to press a button to combine same rules. Cant belief that it takes more than 3,5 years even in Version 6+ the bug is there. Give this bug a higher importance than low, please. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108743 Harald Koesterchanged: What|Removed |Added Depends on||115666 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115666 [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79167] UI: Opening the new "navigate by" for choosing the object to go back opens the "big" navigation window, too
https://bugs.documentfoundation.org/show_bug.cgi?id=79167 Harald Koesterchanged: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||5666 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115666] “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 Harald Koesterchanged: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=79 ||167 Blocks||108743 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108743 [Bug 108743] [META] Find toolbar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115666] New: “Navigate By” Function does not Work if Cursor is Positioned in Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=115666 Bug ID: 115666 Summary: “Navigate By” Function does not Work if Cursor is Positioned in Comment Product: LibreOffice Version: 6.0.1.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: harald.koes...@mail.de In order to reproduce: [1] Create a new text document and insert 3 simple tables with some empty lines between them.. [2] Insert a comment after first table. [3] Position the cursor inside the comment. [4] Display Find toolbar and select Table in “Navigate By” drop-down menu. [5] Click arrow keys in order to find the previous or next table. Nothing happens. The cursor is still in the comment. Expected: Cursor in tables. This bug also occurs if you use bookmarks instead of tables. I did not check the other object types. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103341] [META] Auto Correct and Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 115382, which changed state. Bug 115382 Summary: Hungarian users need better access to apostrophe https://bugs.documentfoundation.org/show_bug.cgi?id=115382 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97361] Make unittests more pythonic
https://bugs.documentfoundation.org/show_bug.cgi?id=97361 --- Comment #29 from Commit Notification--- Saurav Chirania committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4469c1d4061e8cb463469e60e5d87af5f9bf9636 tdf#97361 Tests in sw should be more pythonic It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: sw/qa
sw/qa/python/check_table.py | 55 +--- 1 file changed, 27 insertions(+), 28 deletions(-) New commits: commit 4469c1d4061e8cb463469e60e5d87af5f9bf9636 Author: Saurav ChiraniaDate: Fri Feb 2 05:00:39 2018 +0530 tdf#97361 Tests in sw should be more pythonic The modified files have been made more pythonic by removing Java-like codes. Change-Id: Ie015bb5fa2348d31682b843df7f9c6d86c5e9fc1 Reviewed-on: https://gerrit.libreoffice.org/49163 Tested-by: Jenkins Reviewed-by: Björn Michaelsen diff --git a/sw/qa/python/check_table.py b/sw/qa/python/check_table.py index 60c2d726ed58..47389fdeef08 100644 --- a/sw/qa/python/check_table.py +++ b/sw/qa/python/check_table.py @@ -26,13 +26,13 @@ class CheckTable(unittest.TestCase): for x in range(3): for y in range(3): -xTable.getCellByPosition(x, y).String = 'Cell %d %d' % (x, y) +xTable[y,x].String = 'Cell %d %d' % (x, y) def _check_table(self, xTable): for x in range(3): for y in range(3): -self.assertEqual('Cell %d %d' % (x, y), xTable.getCellByPosition(x, y).String) +self.assertEqual('Cell %d %d' % (x, y), xTable[y,x].String) @classmethod def setUpClass(cls): @@ -282,14 +282,14 @@ class CheckTable(unittest.TestCase): self._check_table(xTable) xTable.RowDescriptions = ('fooRow', 'bazRow') xTable.ColumnDescriptions = ('fooColumn', 'bazColumn') -self.assertEqual('fooRow', xTable.getCellByPosition(0, 1).String) -self.assertEqual('bazRow', xTable.getCellByPosition(0, 2).String) -self.assertEqual('fooColumn', xTable.getCellByPosition(1, 0).String) -self.assertEqual('bazColumn', xTable.getCellByPosition(2, 0).String) -xTable.getCellByPosition(0, 1).String = 'Cell 0 1' # reset changes values ... -xTable.getCellByPosition(0, 2).String = 'Cell 0 2' -xTable.getCellByPosition(1, 0).String = 'Cell 1 0' -xTable.getCellByPosition(2, 0).String = 'Cell 2 0' +self.assertEqual('fooRow', xTable[1,0].String) +self.assertEqual('bazRow', xTable[2,0].String) +self.assertEqual('fooColumn', xTable[0,1].String) +self.assertEqual('bazColumn', xTable[0,2].String) +xTable[1,0].String = 'Cell 0 1' # reset changes values ... +xTable[2,0].String = 'Cell 0 2' +xTable[0,1].String = 'Cell 1 0' +xTable[0,2].String = 'Cell 2 0' self._check_table(xTable) # ... to ensure the rest was untouched # check disconnected table excepts, but doesn't crash xTable2 = xDoc.createInstance("com.sun.star.text.TextTable") @@ -310,11 +310,11 @@ class CheckTable(unittest.TestCase): xTable.ChartColumnAsLabel = False xTable.ChartRowAsLabel = False # roundtrip -xTable.Data = ((1, 2, 3), (4, 5, 6), (7, 8, 9), (10, 11, 12)) +xTable.Data = ((y for y in range(3*x+1,3*x+4)) for x in range(4)) self.assertEqual(xTable.Data, ((1, 2, 3), (4, 5, 6), (7, 8, 9), (10, 11, 12))) # missing row with self.assertRaises(Exception): -xTable.Data = ((1, 2, 3), (4, 5, 6), (7, 8, 9)) +xTable.Data = ((y for y in range(3*x+1,3*x+4)) for x in range(3)) # missing column with self.assertRaises(Exception): xTable.Data = ((1, 2), (4, 5), (7, 8), (10, 11)) @@ -342,7 +342,7 @@ class CheckTable(unittest.TestCase): xDoc.Text.insertTextContent(xCursor, xTable, False) xTable.ChartColumnAsLabel = False xTable.ChartRowAsLabel = False -xTable.Data = ((1, 2, 3), (4, 5, 6), (7, 8, 9), (10, 11, 12)) +xTable.Data = ((y for y in range(3*x+1,3*x+4)) for x in range(4)) xRows = xTable.Rows self.assertEqual(xRows.ImplementationName, 'SwXTableRows') self.assertTrue(xRows.supportsService('com.sun.star.text.TableRows')) @@ -369,7 +369,7 @@ class CheckTable(unittest.TestCase): xDoc.Text.insertTextContent(xCursor, xTable, False) xTable.ChartColumnAsLabel = False xTable.ChartRowAsLabel = False -xTable.Data = ((1, 2, 3), (4, 5, 6), (7, 8, 9), (10, 11, 12)) +xTable.Data = ((y for y in range(3*x+1,3*x+4)) for x in range(4)) xRows = xTable.Rows xRows.insertByIndex(1, 2) nan = float('nan') @@ -411,7 +411,7 @@ class CheckTable(unittest.TestCase): xDoc.Text.insertTextContent(xCursor, xTable, False) xTable.ChartColumnAsLabel = False xTable.ChartRowAsLabel = False -xTable.Data = ((1, 2, 3), (4, 5, 6), (7, 8, 9), (10, 11, 12)) +xTable.Data = ((y for y in range(3*x+1,3*x+4)) for x in range(4)) self.assertTrue(xTable.Name == 'Table1') self.assertIn('com.sun.star.text.GenericTextDocument',
[Libreoffice-bugs] [Bug 115664] Arial Unicode font issue?
https://bugs.documentfoundation.org/show_bug.cgi?id=115664 --- Comment #2 from Dave--- Created attachment 139847 --> https://bugs.documentfoundation.org/attachment.cgi?id=139847=edit current user profile (after factory reset) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115664] Arial Unicode font issue?
https://bugs.documentfoundation.org/show_bug.cgi?id=115664 --- Comment #1 from Dave--- Created attachment 139846 --> https://bugs.documentfoundation.org/attachment.cgi?id=139846=edit sample test .doc file the small extract of the offending document -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115665] New: Format in the CTRL+H search affects the CTRL+F search
https://bugs.documentfoundation.org/show_bug.cgi?id=115665 Bug ID: 115665 Summary: Format in the CTRL+H search affects the CTRL+F search Product: LibreOffice Version: 6.0.1.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tomaspa...@centrum.cz Description: Setting Format in the CTRL+H search dialog affects the search performed by the CTRL+F dialog. This is similar to this former bug https://bugs.documentfoundation.org/show_bug.cgi?id=62601 but it isn't the same and it isn't fixed. Steps to Reproduce: 1. Write "This is happiness." in a document (and don't put any font effects on it). 2. Open the CTRL+H search dialog and in Other options -> Format -> Font Effects, set "Effects:" to "Capitals" 3. Close the search dialog and try to do a CTRL+F search for the string "happiness". Actual Results: "happiness" isn't found. Expected Results: "happiness" should be found. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.0.1.1 Build ID: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115148] Metafiles with semi transparent polygons are shown without colors
https://bugs.documentfoundation.org/show_bug.cgi?id=115148 Bartoszchanged: What|Removed |Added CC||gan...@poczta.onet.pl --- Comment #2 from Bartosz --- Created attachment 139845 --> https://bugs.documentfoundation.org/attachment.cgi?id=139845=edit EMF file extracted from PPTX file -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: Branch 'distro/collabora/cp-5.3-desktop' - 6 commits - chart2/inc chart2/qa chart2/source include/oox offapi/com offapi/UnoApi_offapi.mk oox/inc oox/source sd/qa sd/sou
chart2/inc/unonames.hxx |1 chart2/qa/extras/chart2export.cxx| 159 ++ chart2/qa/extras/chart2import.cxx| 154 ++ chart2/qa/extras/data/pptx/tdf115107-2.pptx |binary chart2/qa/extras/data/pptx/tdf115107.pptx|binary chart2/source/chartcore.component|1 chart2/source/model/main/DataPointProperties.cxx | 12 chart2/source/model/main/DataPointProperties.hxx |3 chart2/source/model/main/FormattedString.cxx | 44 +++ chart2/source/model/main/FormattedString.hxx | 19 + chart2/source/view/charttypes/VSeriesPlotter.cxx | 126 +++- chart2/source/view/inc/AbstractShapeFactory.hxx |7 chart2/source/view/inc/OpenglShapeFactory.hxx|7 chart2/source/view/inc/ShapeFactory.hxx |7 chart2/source/view/inc/VSeriesPlotter.hxx|2 chart2/source/view/main/OpenglShapeFactory.cxx | 12 chart2/source/view/main/ShapeFactory.cxx | 94 ++ include/oox/ppt/slidetransition.hxx |4 include/oox/ppt/slidetransitioncontext.hxx |1 offapi/UnoApi_offapi.mk |3 offapi/com/sun/star/chart2/DataPointCustomLabelField.idl | 26 + offapi/com/sun/star/chart2/DataPointCustomLabelFieldType.idl | 33 ++ offapi/com/sun/star/chart2/DataPointProperties.idl |8 offapi/com/sun/star/chart2/XDataPointCustomLabelField.idl| 43 ++ offapi/com/sun/star/presentation/DrawPage.idl|9 oox/inc/drawingml/textfield.hxx |2 oox/source/drawingml/chart/seriesconverter.cxx | 112 ++- oox/source/export/chartexport.cxx| 107 +++ oox/source/ppt/slidetransition.cxx | 30 +- oox/source/ppt/slidetransitioncontext.cxx| 15 - oox/source/token/properties.txt |2 sd/qa/unit/data/ppt/tdf115394.ppt|binary sd/qa/unit/data/pptx/tdf114821.pptx |binary sd/qa/unit/data/pptx/tdf115394-zero.pptx |binary sd/qa/unit/data/pptx/tdf115394.pptx |binary sd/qa/unit/export-tests-ooxml2.cxx | 52 +++ sd/qa/unit/export-tests.cxx | 39 ++ sd/qa/unit/import-tests.cxx | 108 +++ sd/source/filter/eppt/eppt.cxx | 26 + sd/source/filter/eppt/pptx-epptooxml.cxx | 161 +++ sd/source/filter/ppt/pptin.cxx |6 sd/source/ui/inc/unoprnms.hxx|1 sd/source/ui/unoidl/unopage.cxx |2 sw/qa/extras/ooxmlexport/data/graphic-object-fliph.docx |binary sw/qa/extras/ooxmlexport/ooxmlexport9.cxx|6 sw/source/filter/ww8/docxattributeoutput.cxx | 18 + writerfilter/source/dmapper/GraphicImport.cxx| 11 47 files changed, 1375 insertions(+), 98 deletions(-) New commits: commit 2ef5ccadeff6fdcb427fde71b0d2796a0afde057 Author: Szymon KłosDate: Mon Feb 12 20:39:14 2018 +0100 tdf#114821 import/export/place complex data labels in charts Change-Id: Ia44abcebb4febcabb1704aef85e396730ac2cd6f diff --git a/chart2/inc/unonames.hxx b/chart2/inc/unonames.hxx index 867a155e14aa..44c3bf67d3cb 100644 --- a/chart2/inc/unonames.hxx +++ b/chart2/inc/unonames.hxx @@ -29,6 +29,7 @@ #define CHART_UNONAME_LABEL_BORDER_DASH "LabelBorderDash" #define CHART_UNONAME_LABEL_BORDER_DASHNAME "LabelBorderDashName" #define CHART_UNONAME_LABEL_BORDER_TRANS"LabelBorderTransparency" +#define CHART_UNONAME_CUSTOM_LABEL_FIELDS "CustomLabelFields" #endif diff --git a/chart2/qa/extras/chart2export.cxx b/chart2/qa/extras/chart2export.cxx index 5975c7a3cfa2..77c5ddffb9cb 100644 --- a/chart2/qa/extras/chart2export.cxx +++ b/chart2/qa/extras/chart2export.cxx @@ -13,6 +13,8 @@ #include #include +#include +#include #include #include #include @@ -100,6 +102,8 @@ public: void testMultipleAxisXLSX(); void testAxisTitleRotationXLSX(); void testAxisCrossBetweenXSLX(); +void testCustomDataLabel(); +void testCustomDataLabelMultipleSeries(); CPPUNIT_TEST_SUITE(Chart2ExportTest); CPPUNIT_TEST(testErrorBarXLSX); @@ -164,6 +168,8 @@ public: CPPUNIT_TEST(testMultipleAxisXLSX); CPPUNIT_TEST(testAxisTitleRotationXLSX); CPPUNIT_TEST(testAxisCrossBetweenXSLX); +CPPUNIT_TEST(testCustomDataLabel); +
[Libreoffice-bugs] [Bug 35077] [UI] Add an OPTION to switch off special effects, such as flashing lines around copy source cell(s)
https://bugs.documentfoundation.org/show_bug.cgi?id=35077 --- Comment #34 from crx...@hotmail.com --- (In reply to MarjaE from comment #33) > Won't that hide this from other users who need to protect themselves? I > think this should be taken as an enhancement request, to make it easier to > find these accessibility settings, when they exist. I agree. I don't think this issue should be closed as "resolved" quite yet... I am VERY glad there is an "expert configuration" option. This will help a lot of people (if they can ever find it). However, I thought part of the point of this bug/enhancement report/request was to also have something more visible for users to use in the UI to control it. For example- in Tools-> Options-> Accessibility-> Misc Options there are already checkboxes for "allow animated graphics" and "allow animated text". It seems logical that if a user said they don't want to see animated graphics, that would include animated graphics of the selection process (or any other screen animation). Perhaps not, but it seems plausible. And if not, then if we have THOSE two available in options, why not add an "allow copy/paste animation" or "allow selection animation" option right there with them? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-commits] core.git: formula/source sc/source
formula/source/core/api/token.cxx | 10 +- sc/source/core/tool/interpr4.cxx |4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) New commits: commit a6c659283ab02cb59feda39b67e1837ed8c32730 Author: Eike RathkeDate: Mon Feb 12 22:52:05 2018 +0100 Use FormulaCompiler::IsOpCodeJumpCommand() where applicable Change-Id: I295e842da0192c21d318357caa574062085acd9d diff --git a/formula/source/core/api/token.cxx b/formula/source/core/api/token.cxx index cfd759562d59..05ca4cf5e1e9 100644 --- a/formula/source/core/api/token.cxx +++ b/formula/source/core/api/token.cxx @@ -86,7 +86,7 @@ bool FormulaToken::IsFunction() const eOp != ocTableRef && (GetByte() != 0 // x parameters || (SC_OPCODE_START_NO_PAR <= eOp && eOp < SC_OPCODE_STOP_NO_PAR) // no parameter -|| (ocIf == eOp || ocIfError == eOp || ocIfNA == eOp || ocChoose == eOp ) // @ jump commands +|| FormulaCompiler::IsOpCodeJumpCommand( eOp ) // @ jump commands || (SC_OPCODE_START_1_PAR <= eOp && eOp < SC_OPCODE_STOP_1_PAR) // one parameter || (SC_OPCODE_START_2_PAR <= eOp && eOp < SC_OPCODE_STOP_2_PAR) // x parameters (cByte==0 in // FuncAutoPilot) @@ -101,10 +101,10 @@ bool FormulaToken::IsFunction() const sal_uInt8 FormulaToken::GetParamCount() const { if ( eOp < SC_OPCODE_STOP_DIV && eOp != ocExternal && eOp != ocMacro && - eOp != ocIf && eOp != ocIfError && eOp != ocIfNA && eOp != ocChoose && + !FormulaCompiler::IsOpCodeJumpCommand( eOp ) && eOp != ocPercentSign ) return 0; // parameters and specials -// ocIf, ocIfError, ocIfNA and ocChoose not for FAP, have cByte then +// ocIf... jump commands not for FAP, have cByte then //2do: bool parameter whether FAP or not? else if ( GetByte() ) return GetByte(); // all functions, also ocExternal and ocMacro @@ -117,7 +117,7 @@ sal_uInt8 FormulaToken::GetParamCount() const return 0; // no parameter else if (SC_OPCODE_START_1_PAR <= eOp && eOp < SC_OPCODE_STOP_1_PAR) return 1; // one parameter -else if ( eOp == ocIf || eOp == ocIfError || eOp == ocIfNA || eOp == ocChoose ) +else if (FormulaCompiler::IsOpCodeJumpCommand( eOp )) return 1; // only the condition counts as parameter else return 0; // all the rest, no Parameter, or @@ -893,7 +893,7 @@ bool FormulaTokenArray::HasMatrixDoubleRefOps() } if ( eOp == ocPush || lcl_IsReference( eOp, t->GetType() ) ) pStack[sp++] = t; -else if ( eOp == ocIf || eOp == ocIfError || eOp == ocIfNA || eOp == ocChoose ) +else if (FormulaCompiler::IsOpCodeJumpCommand( eOp )) { // ignore Jumps, pop previous Result (Condition) if ( sp ) --sp; diff --git a/sc/source/core/tool/interpr4.cxx b/sc/source/core/tool/interpr4.cxx index 942911d29ff2..c1cd4f835398 100644 --- a/sc/source/core/tool/interpr4.cxx +++ b/sc/source/core/tool/interpr4.cxx @@ -3987,7 +3987,7 @@ StackVar ScInterpreter::Interpret() nCurFmtType = SvNumFormatType::UNDEFINED; } else if (pTokenMatrixMap && - !(eOp == ocIf || eOp == ocIfError || eOp == ocIfNA || eOp == ocChoose) && + !FormulaCompiler::IsOpCodeJumpCommand( eOp ) && ((aTokenMatrixMapIter = pTokenMatrixMap->find( pCur)) != pTokenMatrixMap->end()) && (*aTokenMatrixMapIter).second->GetType() != svJumpMatrix) @@ -4008,7 +4008,7 @@ StackVar ScInterpreter::Interpret() nFuncFmtType = SvNumFormatType::NUMBER; nFuncFmtIndex = 0; -if ( eOp == ocIf || eOp == ocChoose || eOp == ocIfError || eOp == ocIfNA ) +if (FormulaCompiler::IsOpCodeJumpCommand( eOp )) nStackBase = sp;// don't mess around with the jumps else { ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 114998] Externally Linked Data should update when pressing F9
https://bugs.documentfoundation.org/show_bug.cgi?id=114998 --- Comment #7 from m.a.riosv--- (In reply to Heiko Tietze from comment #6) > (In reply to m.a.riosv from comment #5) > > But hard recalc does the update [Ctrl+Shift+F9] > > Not for me, I need to change the formula (Linux/Fresh). And anyway, as long > we do not understand webservice as an add-in functions it shouldn't depend > on normal vs. hard recalculate. A formula like: =MID(WEBSERVICE("http://tycho.usno.navy.mil/timer.html;);166;21)(TODAY();"") works for me with [F9], because it has a valatile function like TODAY() With autoupdate it's calculated every time some cell is modified, it's how volatile funcitions work. IMHO having WEBSERVICE() as volatile could make inoperable the spreedsheet when large files/pages are retrieved. If I'm not wrong one of the main purpose of the function is to work in combination with FILTERXLM(). Maybe having the Eike opinion will be the best. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs