[Libreoffice-commits] core.git: sw/source
sw/source/core/txtnode/fntcache.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 6de6231fa9266b64aac87ee3415e4855bbaeec4e
Author: Khaled Hosny
AuthorDate: Mon Sep 26 06:43:37 2022 +0200
Commit: خالد حسني
CommitDate: Mon Sep 26 07:53:40 2022 +0200
tdf#150726: Fix previous fix
Fix regression from:
commit 092e37a284ea8b8bc1e8dabbbeb001c98012a996
Author: Khaled Hosny
Date: Sun Sep 25 11:37:05 2022 +0200
tdf#150726: Pass full string to DrawTextArray() when drawing bullet
Since we are no longer copying the string, we need to use the actual
rInf.GetIdx() here as well.
Change-Id: Ic68593407cb313785c9d734e4a3a3687e2ba4eee
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140582
Tested-by: Jenkins
Reviewed-by: خالد حسني
diff --git a/sw/source/core/txtnode/fntcache.cxx
b/sw/source/core/txtnode/fntcache.cxx
index fe095aa5105b..290ff8cc1276 100644
--- a/sw/source/core/txtnode/fntcache.cxx
+++ b/sw/source/core/txtnode/fntcache.cxx
@@ -1340,7 +1340,7 @@ void SwFntObj::DrawText( SwDrawTextInfo )
aKernArray, aKashidaArray, sal_Int32(rInf.GetIdx()),
1 );
if( bBullet )
rInf.GetOut().DrawTextArray( aTextOriginPos, rInf.GetText(),
aKernArray, {},
- rInf.GetIdx() ? 1 : 0, 1 );
+ sal_Int32(rInf.GetIdx()), 1 );
}
else
{
[Libreoffice-bugs] [Bug 33240] RPT: grouping/sorting silently ignored with "analyze sql: no"
https://bugs.documentfoundation.org/show_bug.cgi?id=33240 --- Comment #15 from Robert Großkopf --- Bug is still the same in LO 7.3.6.2 on OpenSUSE 15.3 64bit rpm Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142462] LO BASE FILESAVE- too many unwanted backup copies lead to "low disk space" alarm
https://bugs.documentfoundation.org/show_bug.cgi?id=142462 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8639 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108542] [META] Chart label bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108542 Bug 108542 depends on bug 41741, which changed state. Bug 41741 Summary: VIEWING: Callout text size changes when modification in data source https://bugs.documentfoundation.org/show_bug.cgi?id=41741 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41741] VIEWING: Callout text size changes when modification in data source
https://bugs.documentfoundation.org/show_bug.cgi?id=41741 Rainer Bielefeld Retired changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from Rainer Bielefeld Retired --- I saw some problems with "Manueller Eingriff ..." callout (character size too big, different text colors using different LibO versions) with LibO 4.0.0. and 6.0.7.3 No problems at all any longer reproducible with Installation of Version: 7.3.3.2 (x64) Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE | Calc: threaded | Elementary Theme | My normal User Profile: Text size,background and character color seem ok. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 --- Comment #16 from Buovjaga --- (In reply to tex.avery2 from comment #15) > Hello, > > Same problem with the new Macbook pro 14 pouces, Monterey 12.6. > > Please, try to correct this bug ! Would be easier, if someone bisected it like I said in comment 11. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 Buovjaga changed: What|Removed |Added Hardware|ARM |All Version|7.4.1.2 release |7.2.1.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117173] Search Dialog does not provide search results to Assistive Technology tools at 5.2 and later, results are recorded to GUI without accessible event as text in SetSearchL
https://bugs.documentfoundation.org/show_bug.cgi?id=117173 --- Comment #19 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/947fe0d89dee75ee43515ef7dfb43837d65a45bc tdf#119788 tdf#117173 add accessibility NOTIFICATION role It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: offapi/com svx/source svx/uiconfig vcl/osx vcl/qt5 vcl/source vcl/unx winaccessibility/source
offapi/com/sun/star/accessibility/AccessibleRole.idl |7 +
svx/source/dialog/srchdlg.cxx | 14 ++
svx/uiconfig/ui/findreplacedialog.ui |3 +-
vcl/osx/a11yrolehelper.mm |2 +
vcl/qt5/QtAccessibleWidget.cxx|6
vcl/source/window/builder.cxx |2 -
vcl/unx/gtk3/a11y/atkwrapper.cxx |2 +
winaccessibility/source/service/AccComponentEventListener.cxx |1
winaccessibility/source/service/AccObject.cxx |6 ++--
winaccessibility/source/service/AccObjectWinManager.cxx |1
10 files changed, 35 insertions(+), 9 deletions(-)
New commits:
commit 947fe0d89dee75ee43515ef7dfb43837d65a45bc
Author: Jim Raykowski
AuthorDate: Thu Sep 8 19:27:31 2022 -0800
Commit: Jim Raykowski
CommitDate: Mon Sep 26 05:55:25 2022 +0200
tdf#119788 tdf#117173 add accessibility NOTIFICATION role
and use it to make screen readers announce notifications from the
'Find and Replace' dialog
Change-Id: Ifcf9304883e2e824ea1b7998d7767e474b87c8b6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139709
Tested-by: Jenkins
Reviewed-by: Michael Weghorn
diff --git a/offapi/com/sun/star/accessibility/AccessibleRole.idl
b/offapi/com/sun/star/accessibility/AccessibleRole.idl
index 6c7e9fbcf790..c8e8ccc03ec2 100644
--- a/offapi/com/sun/star/accessibility/AccessibleRole.idl
+++ b/offapi/com/sun/star/accessibility/AccessibleRole.idl
@@ -737,6 +737,13 @@ constants AccessibleRole
*/
const short STATIC = 86;
+/** Notification text role.
+
+An object that presents information to the user when the SHOWING
state change event is
+ fired for the object.
+*/
+const short NOTIFICATION = 87;
+
};
}; }; }; };
diff --git a/svx/source/dialog/srchdlg.cxx b/svx/source/dialog/srchdlg.cxx
index 4f2378881867..69483c124770 100644
--- a/svx/source/dialog/srchdlg.cxx
+++ b/svx/source/dialog/srchdlg.cxx
@@ -332,7 +332,6 @@ SvxSearchDialog::SvxSearchDialog(weld::Window* pParent,
SfxChildWindow* pChildWi
m_xSearchTmplLB->make_sorted();
m_xSearchAttrText->hide();
-m_xSearchLabel->show();
m_xReplaceTmplLB->make_sorted();
m_xReplaceAttrText->hide();
@@ -574,6 +573,13 @@ void SvxSearchDialog::SetSaveToModule(bool b)
void SvxSearchDialog::SetSearchLabel(const OUString& rStr)
{
m_xSearchLabel->set_label(rStr);
+if (!rStr.isEmpty())
+{
+// hide/show to fire SHOWING state change event so search label text
+// is announced by screen reader
+m_xSearchLabel->hide();
+m_xSearchLabel->show();
+}
if (rStr == SvxResId(RID_SVXSTR_SEARCH_NOT_FOUND))
m_xSearchLB->set_entry_message_type(weld::EntryMessageType::Error);
@@ -1360,9 +1366,6 @@ IMPL_LINK(SvxSearchDialog, CommandHdl_Impl,
weld::Button&, rBtn, void)
nModifyFlag = ModifyFlags::NONE;
const SfxPoolItem* ppArgs[] = { pSearchItem.get(), nullptr };
rBindings.ExecuteSynchron( FID_SEARCH_NOW, ppArgs );
-
-// grabbing focus to the search combo box makes the search label read
by the screen reader
-m_xSearchLB->grab_focus();
}
else if ( == m_xCloseBtn.get() )
{
@@ -2208,7 +2211,8 @@ void SvxSearchDialog::SetModifyFlag_Impl( const
weld::Widget* pCtrl )
{
nModifyFlag |= ModifyFlags::Search;
m_xSearchLB->set_entry_message_type(weld::EntryMessageType::Normal);
-SvxSearchDialogWrapper::SetSearchLabel("");
+if (!SvxSearchDialogWrapper::GetSearchLabel().isEmpty())
+SvxSearchDialogWrapper::SetSearchLabel("");
}
else if ( m_xReplaceLB.get() == pCtrl )
nModifyFlag |= ModifyFlags::Replace;
diff --git a/svx/uiconfig/ui/findreplacedialog.ui
b/svx/uiconfig/ui/findreplacedialog.ui
index 4c1e9d2bc45f..a8401616d339 100644
--- a/svx/uiconfig/ui/findreplacedialog.ui
+++ b/svx/uiconfig/ui/findreplacedialog.ui
@@ -173,6 +173,7 @@
+True
False
True
True
@@ -181,7 +182,7 @@
0
-static
+notification
diff --git a/vcl/osx/a11yrolehelper.mm b/vcl/osx/a11yrolehelper.mm
index 0ea7075277eb..5cb75c94a86f 100644
--- a/vcl/osx/a11yrolehelper.mm
+++ b/vcl/osx/a11yrolehelper.mm
@@ -126,6 +126,7 @@ using namespace ::com::sun::star::uno;
MAP( AccessibleRole::DOCUMENT_SPREADSHEET, NSAccessibilityGroupRole );
MAP( AccessibleRole::DOCUMENT_TEXT, NSAccessibilityGroupRole );
MAP( AccessibleRole::STATIC,
[Libreoffice-bugs] [Bug 119788] a11y: Distinguish between role STATIC and new role NOTIFICATION
https://bugs.documentfoundation.org/show_bug.cgi?id=119788 --- Comment #3 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/947fe0d89dee75ee43515ef7dfb43837d65a45bc tdf#119788 tdf#117173 add accessibility NOTIFICATION role It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119788] a11y: Distinguish between role STATIC and new role NOTIFICATION
https://bugs.documentfoundation.org/show_bug.cgi?id=119788 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150658] The behavior of the Formatting toolbar has changed in 7.4.0.3 from 7.3 and prior when copying and pasting individual Writer table rows.
https://bugs.documentfoundation.org/show_bug.cgi?id=150658 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150912] Italic and bold graphic glitch with Noto fonts on Arch Linux KDE Plasma when scrolling or editing text
https://bugs.documentfoundation.org/show_bug.cgi?id=150912 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150906] Merged cell collision with application border in "right-to-left sheet" mode
https://bugs.documentfoundation.org/show_bug.cgi?id=150906 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150704] Inserting a new paragraph in Writer generates a lot of warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=150704 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150702] Inserting a chart in Writer generates a lot of warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=150702 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93926] Correct word is corrected to wrong word (Differenzeierbarkit)
https://bugs.documentfoundation.org/show_bug.cgi?id=93926 --- Comment #9 from QA Administrators --- Dear michelbach94, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81736] Writer cannot import variable Ref fields from .doc or .docx and instead displays text "Show variable" and "Set variable"
https://bugs.documentfoundation.org/show_bug.cgi?id=81736 --- Comment #17 from QA Administrators --- Dear Pablo Rodríguez, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63412] PRINTING Handout: all text in a slide becomes raster picture if raster picture is overlapping any text.
https://bugs.documentfoundation.org/show_bug.cgi?id=63412 --- Comment #16 from QA Administrators --- Dear Rick Yorgason, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49259] Writer is too jumpy with images and right clicks
https://bugs.documentfoundation.org/show_bug.cgi?id=49259 --- Comment #9 from QA Administrators --- Dear Ruslan Kabatsayev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41741] VIEWING: Callout text size changes when modification in data source
https://bugs.documentfoundation.org/show_bug.cgi?id=41741 --- Comment #8 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 33240] RPT: grouping/sorting silently ignored with "analyze sql: no"
https://bugs.documentfoundation.org/show_bug.cgi?id=33240 --- Comment #14 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136971] Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=136971 --- Comment #5 from QA Administrators --- Dear sdc.blanco, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132820] UI: Height input box smaller compared to width (document specific)
https://bugs.documentfoundation.org/show_bug.cgi?id=132820 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125154] writer calculation using variable within table does not work with formated numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=125154 --- Comment #6 from QA Administrators --- Dear Daniel Frost, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129223] EDITING: Crash if I copy big amount of data and [Windows]+[V] copy history enabled.
https://bugs.documentfoundation.org/show_bug.cgi?id=129223 --- Comment #6 from QA Administrators --- Dear jorge.alfe.512, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111086] Assertion failure after undo (!"EmptyProperties::SetObjectItemSet() should never be called")
https://bugs.documentfoundation.org/show_bug.cgi?id=111086 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151181] New: I can't find "Edit Style..." in the keyboard customization functions
https://bugs.documentfoundation.org/show_bug.cgi?id=151181 Bug ID: 151181 Summary: I can't find "Edit Style..." in the keyboard customization functions Product: LibreOffice Version: unspecified Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@linna.com Description: I wanted to set a custom keyboard shortcut for "Edit Style..." but couldn't find it. This is on 7.4.2.1 but that version doesn't appear in the version list. Steps to Reproduce: 1. Choose Tools->Customize... and click Keyboard 2. Type "Edit Style" or "Edit" or "Style" in the Functions search field Actual Results: "Edit Style..." does not appear. Expected Results: "Edit Style..." should appear. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151180] Deleting keyboard shortcuts didn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151180 --- Comment #1 from Nik Gervae --- Update: I tried removing the keyboard shortcuts for Left/Center/Right/Justified and they also are still in the menus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/sifr icon-themes/sifr_dark icon-themes/sifr_dark_svg icon-themes/sifr_svg
dev/null|binary icon-themes/sifr/cmd/32/autocorrectdlg.png |binary icon-themes/sifr/cmd/32/autoformat.png |binary icon-themes/sifr/cmd/32/autopilotmenu.png |binary icon-themes/sifr/cmd/32/choosedesign.png|binary icon-themes/sifr/cmd/32/dbnewformautopilot.png |binary icon-themes/sifr/cmd/32/dbnewtableautopilot.png |binary icon-themes/sifr/cmd/32/deletetable.png |binary icon-themes/sifr/cmd/32/duplicatesheet.png |binary icon-themes/sifr/cmd/32/editglossary.png|binary icon-themes/sifr/cmd/32/hide.png|binary icon-themes/sifr/cmd/32/inscellsctrl.png|binary icon-themes/sifr/cmd/32/insert.png |binary icon-themes/sifr/cmd/32/insertcell.png |binary icon-themes/sifr/cmd/32/jumptonexttablejumptoprevtable.png |binary icon-themes/sifr/cmd/32/jumptoprevtable.png |binary icon-themes/sifr/cmd/32/marks.png |binary icon-themes/sifr/cmd/32/move.png|binary icon-themes/sifr/cmd/32/name.png|binary icon-themes/sifr/cmd/32/normalviewmode.png |binary icon-themes/sifr/cmd/32/optimizetable.png |binary icon-themes/sifr/cmd/32/outlinecollapse.png |binary icon-themes/sifr/cmd/32/outlinecollapseall.png |binary icon-themes/sifr/cmd/32/outlineexpand.png |binary icon-themes/sifr/cmd/32/outlineexpandall.png|binary icon-themes/sifr/cmd/32/outlineformat.png |binary icon-themes/sifr/cmd/32/pagebreakmode.png |binary icon-themes/sifr/cmd/32/presentationminimizer.png |binary icon-themes/sifr/cmd/32/printpagepreview.png|binary icon-themes/sifr/cmd/32/remove.png |binary icon-themes/sifr/cmd/32/selecttable.png |binary icon-themes/sifr/cmd/32/selecttables.png|binary icon-themes/sifr/cmd/32/setdocumentproperties.png |binary icon-themes/sifr/cmd/32/sharedocument.png |binary icon-themes/sifr/cmd/32/show.png|binary icon-themes/sifr/cmd/32/tabledesign.png |binary icon-themes/sifr/cmd/32/tableselectall.png |binary icon-themes/sifr/cmd/32/togglesheetgrid.png |binary icon-themes/sifr/cmd/32/usewizards.png |binary icon-themes/sifr/cmd/lc_autocorrectdlg.png |binary icon-themes/sifr/cmd/lc_autoformat.png |binary icon-themes/sifr/cmd/lc_autopilotmenu.png |binary icon-themes/sifr/cmd/lc_choosedesign.png|binary icon-themes/sifr/cmd/lc_dbnewformautopilot.png |binary icon-themes/sifr/cmd/lc_dbnewtableautopilot.png |binary icon-themes/sifr/cmd/lc_deletetable.png |binary icon-themes/sifr/cmd/lc_duplicatesheet.png |binary icon-themes/sifr/cmd/lc_editglossary.png|binary icon-themes/sifr/cmd/lc_hide.png|binary icon-themes/sifr/cmd/lc_inscellsctrl.png|binary icon-themes/sifr/cmd/lc_insert.png |binary icon-themes/sifr/cmd/lc_insertcell.png |binary icon-themes/sifr/cmd/lc_marks.png |binary icon-themes/sifr/cmd/lc_move.png|binary icon-themes/sifr/cmd/lc_name.png|binary icon-themes/sifr/cmd/lc_normalviewmode.png |binary icon-themes/sifr/cmd/lc_optimizetable.png |binary icon-themes/sifr/cmd/lc_outlinecollapse.png |binary icon-themes/sifr/cmd/lc_outlinecollapseall.png |binary icon-themes/sifr/cmd/lc_outlineexpand.png |binary icon-themes/sifr/cmd/lc_outlineexpandall.png|binary icon-themes/sifr/cmd/lc_outlineformat.png |binary icon-themes/sifr/cmd/lc_pagebreakmode.png |binary icon-themes/sifr/cmd/lc_presentationminimizer.png |binary icon-themes/sifr/cmd/lc_printpagepreview.png
[Libreoffice-bugs] [Bug 151180] New: Deleting keyboard shortcuts didn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151180 Bug ID: 151180 Summary: Deleting keyboard shortcuts didn't work Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@linna.com Description: I am using a laptop without dedicated F-keys so I went through the Customization/Keyboard thing and deleted all those keyboard shortcuts, but they are still on the menus and they still work. Steps to Reproduce: 1. Open Tools->Customization... and click Keyboard. 2. Delete any of the keyboard shortcuts with F-keys. 3. Open a menu that has one of the commands you deleted. Actual Results: The keyboard shortcut is still listed and still triggers the menu command. Expected Results: The keyboard shortcut should be gone. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151179] New: I can't find command+backslash in the Customize keyboard shortcuts list
https://bugs.documentfoundation.org/show_bug.cgi?id=151179 Bug ID: 151179 Summary: I can't find command+backslash in the Customize keyboard shortcuts list Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@linna.com Description: I would like to use command+backslash for a keyboard shortcut but it doesn't appear to be listed. I noticed that if I type a shortcut, it gets selected, but nothing happens if I press command+\. Steps to Reproduce: 1. Open Tools->Customization... and click Keyboard. 2. Press command+\. Actual Results: Nothing happens. Expected Results: I hoped to be able to select that keyboard shortcut and assign a command to it. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151178] Include support for Ge'ez zema using multi-line phonetic guides | enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=151178 --- Comment #1 from dawishwis...@gmail.com --- Created attachment 182673 --> https://bugs.documentfoundation.org/attachment.cgi?id=182673=edit example of what i want to be able to do -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151178] New: Include support for Ge'ez zema using multi-line phonetic guides | enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=151178 Bug ID: 151178 Summary: Include support for Ge'ez zema using multi-line phonetic guides | enhancement Product: LibreOffice Version: 7.4.1.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dawishwis...@gmail.com Description: FORMATTING In Ge'ez there is zema milikits these are little marks above words that indicate how the hymns should be said. In order to replicate this, phonetic guides are used. However, phonetic guides aren't supported in impress. Not only that, some hymns have more than one way of saying the hymn which is why I'm also asking the phonetic guides to be able to have more than one line. here is an example: https://user-images.githubusercontent.com/8098333/190934189-b9e5f794-2036-47a2-8a6a-c6fd2f09ec62.png Steps to Reproduce: 1.type the hymn 2.try to use phonetic guide, doesnt work 2b. try to type the phonetic guides in writer 3. unable to get phonetic guides for multiple lines Actual Results: 1.type the hymn 2.try to use phonetic guide, doesnt work 2b. try to type the phonetic guides in writer 3. unable to get phonetic guides for multiple lines Expected Results: expected something like this https://user-images.githubusercontent.com/8098333/190934189-b9e5f794-2036-47a2-8a6a-c6fd2f09ec62.png Reproducible: Always User Profile Reset: Yes Additional Info: maybe make a separate feature since ge'ez isnt from asian origin, like a separate ge'ez milikit guide. also churches primarily use powerpoint so if you can add it into impress first as opposed to writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87687] Merging cells does not move references in equations (Comment 6)
https://bugs.documentfoundation.org/show_bug.cgi?id=87687 --- Comment #13 from Tex2002ans --- Still not working. Followed steps in comment #6. Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150473] Function description in "Functions" sidebar should have minimum height
https://bugs.documentfoundation.org/show_bug.cgi?id=150473 Rafael Lima changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: uitest/packaging
uitest/packaging/README.md |3 +-- uitest/packaging/setup.py |3 ++- 2 files changed, 3 insertions(+), 3 deletions(-) New commits: commit d3050ff4a1355f7ebd3d4e7ddc8fb64f2b8894dd Author: Hossein AuthorDate: Fri Aug 19 15:29:35 2022 +0200 Commit: Adolfo Jayme Barrientos CommitDate: Mon Sep 26 00:26:05 2022 +0200 Use Markdown instead of reStructuredText Use Markdown markup instead of reStructuredText for uitest/packaging/README.rst Change from reStructuredText to Markdown in setup.py is done according to this guide: Making a PyPI-friendly README https://packaging.python.org/en/latest/guides/making-a-pypi-friendly-readme/ Change-Id: I12cbde53518d7ceadec034827d8cb00380df1547 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/138555 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/uitest/packaging/README.rst b/uitest/packaging/README.md similarity index 76% rename from uitest/packaging/README.rst rename to uitest/packaging/README.md index 45d8716f6586..41dacf520414 100644 --- a/uitest/packaging/README.rst +++ b/uitest/packaging/README.md @@ -1,4 +1,3 @@ -Connection code for LibreOffice's pyUNO -=== +# Connection code for LibreOffice's pyUNO This code allows out-of-process communication with a LibreOffice instance. The instance can either be started by the script or a connection to a running LibreOffice instance. The code contains several safety checks for hanging and crashed LibreOffice instances. diff --git a/uitest/packaging/setup.py b/uitest/packaging/setup.py index 9aa32054ccc2..dcaa24512b09 100644 --- a/uitest/packaging/setup.py +++ b/uitest/packaging/setup.py @@ -5,7 +5,7 @@ from os import path here = path.abspath(path.dirname(__file__)) # Get the long description from the README file -with open(path.join(here, 'README.rst'), encoding='utf-8') as f: +with open(path.join(here, 'README.md'), encoding='utf-8') as f: long_description = f.read() setup( @@ -13,6 +13,7 @@ setup( version="0.0.1", description="Connection code for LibreOffice's pyUNO", long_description=long_description, +long_description_content_type='text/markdown', url="http://www.libreoffice.org;, author="The LibreOffice developers", author_email="libreoffice@lists.freedesktop.org",
[Libreoffice-commits] core.git: icon-themes/sifr icon-themes/sifr_dark icon-themes/sifr_dark_svg icon-themes/sifr_svg
icon-themes/sifr/cmd/32/configuredialog.png |binary icon-themes/sifr/cmd/32/datafilterautofilter.png |binary icon-themes/sifr/cmd/32/datafilterspecialfilter.png |binary icon-themes/sifr/cmd/32/datafilterstandardfilter.png |binary icon-themes/sifr/cmd/32/dbsortingandgrouping.png |binary icon-themes/sifr/cmd/32/formfiltered.png |binary icon-themes/sifr/cmd/32/formfilternavigator.png |binary icon-themes/sifr/cmd/32/goalseekdialog.png |binary icon-themes/sifr/cmd/32/groupbox.png |binary icon-themes/sifr/cmd/32/insertreferencefield.png |binary icon-themes/sifr/cmd/32/ko/bold.png |binary icon-themes/sifr/cmd/32/ko/charfontname.png |binary icon-themes/sifr/cmd/32/ko/color.png |binary icon-themes/sifr/cmd/32/ko/datasort.png |binary icon-themes/sifr/cmd/32/ko/fontdialog.png|binary icon-themes/sifr/cmd/32/ko/grow.png |binary icon-themes/sifr/cmd/32/ko/insertfixedtext.png |binary icon-themes/sifr/cmd/32/ko/italic.png|binary icon-themes/sifr/cmd/32/ko/outlinefont.png |binary icon-themes/sifr/cmd/32/ko/overline.png |binary icon-themes/sifr/cmd/32/ko/resetattributes.png |binary icon-themes/sifr/cmd/32/ko/scaletext.png |binary icon-themes/sifr/cmd/32/ko/shadowed.png |binary icon-themes/sifr/cmd/32/ko/shrink.png|binary icon-themes/sifr/cmd/32/ko/sortascending.png |binary icon-themes/sifr/cmd/32/ko/sortdescending.png|binary icon-themes/sifr/cmd/32/ko/strikeout.png |binary icon-themes/sifr/cmd/32/ko/text.png |binary icon-themes/sifr/cmd/32/ko/textdirectionlefttoright.png |binary icon-themes/sifr/cmd/32/ko/textdirectiontoptobottom.png |binary icon-themes/sifr/cmd/32/ko/underline.png |binary icon-themes/sifr/cmd/32/ko/underlinedouble.png |binary icon-themes/sifr/cmd/32/namegroup.png|binary icon-themes/sifr/cmd/32/paralefttoright.png |binary icon-themes/sifr/cmd/32/pararighttoleft.png |binary icon-themes/sifr/cmd/32/removefiltersort.png |binary icon-themes/sifr/cmd/32/textdirectionlefttoright.png |binary icon-themes/sifr/cmd/32/textdirectiontoptobottom.png |binary icon-themes/sifr/cmd/ko/lc_bold.png |binary icon-themes/sifr/cmd/ko/lc_charfontname.png |binary icon-themes/sifr/cmd/ko/lc_color.png |binary icon-themes/sifr/cmd/ko/lc_datasort.png |binary icon-themes/sifr/cmd/ko/lc_fontdialog.png|binary icon-themes/sifr/cmd/ko/lc_grow.png |binary icon-themes/sifr/cmd/ko/lc_insertfixedtext.png |binary icon-themes/sifr/cmd/ko/lc_italic.png|binary icon-themes/sifr/cmd/ko/lc_outlinefont.png |binary icon-themes/sifr/cmd/ko/lc_overline.png |binary icon-themes/sifr/cmd/ko/lc_resetattributes.png |binary icon-themes/sifr/cmd/ko/lc_scaletext.png |binary icon-themes/sifr/cmd/ko/lc_shadowed.png |binary icon-themes/sifr/cmd/ko/lc_shrink.png|binary icon-themes/sifr/cmd/ko/lc_sortascending.png |binary icon-themes/sifr/cmd/ko/lc_sortdescending.png|binary icon-themes/sifr/cmd/ko/lc_strikeout.png |binary icon-themes/sifr/cmd/ko/lc_text_marquee.png |binary icon-themes/sifr/cmd/ko/lc_textdirectionlefttoright.png |binary icon-themes/sifr/cmd/ko/lc_textdirectiontoptobottom.png |binary icon-themes/sifr/cmd/ko/lc_underline.png |binary icon-themes/sifr/cmd/ko/lc_underlinedouble.png |binary icon-themes/sifr/cmd/ko/sc_bold.png |binary icon-themes/sifr/cmd/ko/sc_charfontname.png |binary icon-themes/sifr/cmd/ko/sc_color.png |binary icon-themes/sifr/cmd/ko/sc_datasort.png |binary icon-themes/sifr/cmd/ko/sc_fontdialog.png|binary icon-themes/sifr/cmd/ko/sc_grow.png |binary icon-themes/sifr/cmd/ko/sc_insertfixedtext.png |binary icon-themes/sifr/cmd/ko/sc_italic.png
[Libreoffice-bugs] [Bug 56408] Writer always breaks lines at text direction change
https://bugs.documentfoundation.org/show_bug.cgi?id=56408 --- Comment #25 from Eyal Rozenberg --- (In reply to خالد حسني from comment #17) > This is a bug, change in direction does not create line breaking opportunity. The first part of this statement does not follow from the second. That is, the second part is true, but there already is a breaking opportunity before and after the parentheses regardless of the change in direction. > There is even an easy way to check this ... and checking shows the line breaking opportunity. To me it seems this is a bug because the parenthesized word would still fit on the first line of the two in the sample document. So, it's about why LO thinks it _must_ break as opposed to it mistakenly thinking it _can_ break. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145266] Writer crashes when inserting formula object
https://bugs.documentfoundation.org/show_bug.cgi?id=145266 tex.ave...@aliceadsl.fr changed: What|Removed |Added Version|7.2.1.2 release |7.4.1.2 release Hardware|x86-64 (AMD64) |ARM --- Comment #15 from tex.ave...@aliceadsl.fr --- Hello, Same problem with the new Macbook pro 14 pouces, Monterey 12.6. Please, try to correct this bug ! Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61444] Text layout broken across formatting changes (color, underline, etc.)
https://bugs.documentfoundation.org/show_bug.cgi?id=61444 --- Comment #41 from خالد حسني --- (In reply to Munzir Taha from comment #40) > @خالد حسني > As usual, your fixes are outstanding. I will test as soon as there is a > build available. > > Yes, I am aware that less broken results show when formatting marks are > hidden as in the original bug I filed. So, now remains the broken characters > like LAM ALEF combinations and ligatures. > > I am not sure whether breaking shaping should be the same bug as breaking > kerning.zYes, broken Arabic ligature shaping is similar to kerning because > the text is still correct though not suitable for professional work. > However, breaking shaping is more serious and the text is incorrect and can > be handled in a different way. Kerning (glyph positioning in general) and shaping (glyph substitution in general) are done in the same step, there is no way to fix one but not the other, regardless which is more severe. The underlying issue is the same; when LibreOffice sees a formatting change it splits the text and processes each portion separately. > In Scribus e.g. the kerning doesn't break due to color changes. For Arabic, > Scribus still doesn't know how to handle the coloring for single characters > of combinations correctly so it changes the color of the whole ligature, > which is not perfect but at least the shaping is intact. This is orthogonal to the issue here. There is no single answer for how to partially color a ligature, since it is a single glyph. Some applications will apply the color of the first component to the ligature (Chrome and I think MS Office do this), others will use a mask and color the part of the glyph up to where the cursor is inserted (Firefox is actually the only application I know that does this, and it is not without issues, see https://faultlore.com/blah/text-hates-you/#style-can-change-mid-ligature). This issue is about the shaping part, once this is done (if it ever gets done, it is not a simple task), we can then decide how to partially color ligature glyphs). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61444] Text layout broken across formatting changes (color, underline, etc.)
https://bugs.documentfoundation.org/show_bug.cgi?id=61444 --- Comment #40 from Munzir Taha --- @خالد حسني As usual, your fixes are outstanding. I will test as soon as there is a build available. Yes, I am aware that less broken results show when formatting marks are hidden as in the original bug I filed. So, now remains the broken characters like LAM ALEF combinations and ligatures. I am not sure whether breaking shaping should be the same bug as breaking kerning. Yes, broken Arabic ligature shaping is similar to kerning because the text is still correct though not suitable for professional work. However, breaking shaping is more serious and the text is incorrect and can be handled in a different way. In Scribus e.g. the kerning doesn't break due to color changes. For Arabic, Scribus still doesn't know how to handle the coloring for single characters of combinations correctly so it changes the color of the whole ligature, which is not perfect but at least the shaping is intact. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151177] New: Added page background images disappear from library
https://bugs.documentfoundation.org/show_bug.cgi?id=151177 Bug ID: 151177 Summary: Added page background images disappear from library Product: LibreOffice Version: 7.4.1.2 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@linna.com Description: I added some images to use as page backgrounds, expecting them to remain availalble to choose in the catalogue of images. But they disappear randomly. Steps to Reproduce: 1.Add an image to a Page Style/Area. 2.Apply it, or not, doesn't seem to matter. 3.Close the Page Style dialog. 4.Reopen the Page Style dialog. Actual Results: The added images aren't there, most of the time. Expected Results: The added images should be there. Reproducible: Sometimes User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #8 from tor...@yahoo.com --- Created attachment 182670 --> https://bugs.documentfoundation.org/attachment.cgi?id=182670=edit file with various tabs and indents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #8 from tor...@yahoo.com --- Created attachment 182670 --> https://bugs.documentfoundation.org/attachment.cgi?id=182670=edit file with various tabs and indents. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #7 from tor...@yahoo.com --- (In reply to Heiko Tietze from comment #6) > the sample document has quite many modifications to the default. ● Does Writer get confused by many modifications? How many? > > I don't see an issue. ● You might see it with the new document, tabs6.odt: *Elements AA, BB, BC, HH and DD conform to specs and user expectations; *CC looks like BB and DD but was obtained by hitting the TabKey twice —unexpected. If TabKey had ignored the indent, a single TabKey hit would have entered a Tab filled by underline beginning at the left margin (according to hangingIndent definition), like AA or BC. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #7 from tor...@yahoo.com --- (In reply to Heiko Tietze from comment #6) > the sample document has quite many modifications to the default. ● Does Writer get confused by many modifications? How many? > > I don't see an issue. ● You might see it with the new document, tabs6.odt: *Elements AA, BB, BC, HH and DD conform to specs and user expectations; *CC looks like BB and DD but was obtained by hitting the TabKey twice —unexpected. If TabKey had ignored the indent, a single TabKey hit would have entered a Tab filled by underline beginning at the left margin (according to hangingIndent definition), like AA or BC. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151154] Change category "draw" in Template Manager and make it translatable
https://bugs.documentfoundation.org/show_bug.cgi?id=151154
--- Comment #4 from Rafael Lima ---
Created attachment 182669
--> https://bugs.documentfoundation.org/attachment.cgi?id=182669=edit
Template Manager categories after patch
(In reply to Laurent BP from comment #3)
> I tried to deep in this bug but I was not able to find a solution.
>
> Categories name are defined in TEMPLATE_LONG_NAMES_ARY[]:
> https://opengrok.libreoffice.org/xref/core/sfx2/inc/doctempl.
> hrc?r=144057a5#27
> I added a line
> +NC_("TEMPLATE_LONG_NAMES_ARY", "Draw"),
>
> as well as in TEMPLATE_SHORT_NAMES_ARY[]:
> https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/doctemplates.
> cxx?r=91ba9654#483
> I added a line at the same position
> +"draw",
This is exactly what I did. However, for it to take effect you need to be on a
clear user profile. You need to either be on safe mode or apply the "Reset
settings and user interface modifications" option to see the new category name.
Here's a screenshot I took after applying the patch and resetting the user
profile.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sc/inc
sc/inc/document.hxx |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 2a0ea9c49084e31e5ef01bd824be53882e97f4a7 Author: Luboš Luňák AuthorDate: Mon May 9 11:10:43 2022 +0200 Commit: Szymon Kłos CommitDate: Sun Sep 25 21:18:30 2022 +0200 make ScDocument::FetchTable() public I don't see why it should be private, it's range checked, so there should be no harm. Especially when a number of classes get declared as friends to get access to it anyway. Change-Id: I333d749aa9d09aaf9dcbabf43d67a67d1257a132 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134051 Tested-by: Jenkins Reviewed-by: Luboš Luňák Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139471 Tested-by: Jenkins CollaboraOffice diff --git a/sc/inc/document.hxx b/sc/inc/document.hxx index 1c26604a4fb5..4f06b4b6473b 100644 --- a/sc/inc/document.hxx +++ b/sc/inc/document.hxx @@ -2655,9 +2655,6 @@ private: ScDocument& mrDoc; }; -ScTable* FetchTable( SCTAB nTab ); -const ScTable* FetchTable( SCTAB nTab ) const; - voidMergeNumberFormatter(const ScDocument& rSrcDoc); voidImplCreateOptions(); // Suggestion: switch to on-demand? @@ -2682,6 +2679,9 @@ private: boolHasPartOfMerged( const ScRange& rRange ); public: +ScTable* FetchTable( SCTAB nTab ); +const ScTable* FetchTable( SCTAB nTab ) const; + ScRefCellValue GetRefCellValue( const ScAddress& rPos ); private: ScRefCellValue GetRefCellValue( const ScAddress& rPos, sc::ColumnBlockPosition& rBlockPos );
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/docnum.cxx | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
New commits:
commit 415bdf0c0aaa791122d5ef5f81a5409974dd646c
Author: Noel Grandin
AuthorDate: Sun Sep 25 19:22:15 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 21:00:40 2022 +0200
use more SwPosition::Assign
part of the process of hiding the internals of SwPosition
Change-Id: I69f153abdc9789f327a7b5373560a97e90d622a2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140575
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/docnum.cxx b/sw/source/core/doc/docnum.cxx
index 7462b608df99..5975288c6cd7 100644
--- a/sw/source/core/doc/docnum.cxx
+++ b/sw/source/core/doc/docnum.cxx
@@ -1582,15 +1582,9 @@ static bool lcl_GotoNextPrevNum( SwPosition& rPos, bool
bNext,
if( !bRet && !bOverUpper && pLast ) // do not iterate over higher
numbers, but still to the end
{
if( bNext )
-{
-rPos.nNode = aIdx;
-if( aIdx.GetNode().IsContentNode() )
-rPos.nContent.Assign( aIdx.GetNode().GetContentNode(), 0 );
-}
+rPos.Assign(aIdx);
else
-{
rPos.Assign( *pLast );
-}
bRet = true;
}
@@ -2376,9 +2370,10 @@ bool SwDoc::MoveParagraphImpl(SwPaM& rPam, SwNodeOffset
const nOffset,
}
if( pREnd->GetNodeIndex() != nRedlEndNd )
{
-pREnd->nNode = nRedlEndNd;
+pREnd->Assign(nRedlEndNd);
SwContentNode* pCNd = pREnd->GetNode().GetContentNode();
-pREnd->nContent.Assign( pCNd, pCNd ? pCNd->Len() : 0 );
+if(pCNd)
+pREnd->SetContent( pCNd->Len() );
}
}
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/DocumentFieldsManager.cxx |3 +--
sw/source/core/doc/DocumentLayoutManager.cxx |3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
New commits:
commit 1988782c8131d307aff14bdaf7feabd8a5bc3214
Author: Noel Grandin
AuthorDate: Sun Sep 25 19:18:47 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 21:00:24 2022 +0200
use more SwPosition::SetContent
part of the process of hiding the internals of SwPosition
Change-Id: Idc0b3c68d8f2c560868eacf5679e8a1f133cf80b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140574
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/DocumentFieldsManager.cxx
b/sw/source/core/doc/DocumentFieldsManager.cxx
index 448d821b54df..a0eb50754f0c 100644
--- a/sw/source/core/doc/DocumentFieldsManager.cxx
+++ b/sw/source/core/doc/DocumentFieldsManager.cxx
@@ -509,8 +509,7 @@ bool DocumentFieldsManager::UpdateField(SwTextField *
pDstTextField, SwField & r
{
if (m_rDoc.GetIDocumentUndoRedo().DoesUndo())
{
-SwPosition aPosition( pDstTextField->GetTextNode() );
-aPosition.nContent = pDstTextField->GetStart();
+SwPosition aPosition( pDstTextField->GetTextNode(),
pDstTextField->GetStart() );
m_rDoc.GetIDocumentUndoRedo().AppendUndo(
std::make_unique( aPosition, *pDstField,
rSrcField, pMsgHint, bUpdateFields) );
diff --git a/sw/source/core/doc/DocumentLayoutManager.cxx
b/sw/source/core/doc/DocumentLayoutManager.cxx
index add587bd790c..bbe90610e8b9 100644
--- a/sw/source/core/doc/DocumentLayoutManager.cxx
+++ b/sw/source/core/doc/DocumentLayoutManager.cxx
@@ -302,8 +302,7 @@ void DocumentLayoutManager::DelLayoutFormat( SwFrameFormat
*pFormat )
{
// don't delete, set pointer to 0
const_cast(pAttr->GetFlyCnt()).SetFlyFormat();
-SwContentIndex aIdx( pPos->nContent );
-pTextNd->EraseText( aIdx, 1 );
+pTextNd->EraseText( *pPos, 1 );
}
}
}
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/docfmt.cxx | 16
1 file changed, 8 insertions(+), 8 deletions(-)
New commits:
commit 63f1484e460700b101825b8c00b87f6592d4a5d0
Author: Noel Grandin
AuthorDate: Sun Sep 25 19:15:07 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 21:00:00 2022 +0200
use more SwPosition::SetContent
part of the process of hiding the internals of SwPosition
Change-Id: I026a5480ede5e640550b39e8b030de303870cfc9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140573
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/docfmt.cxx b/sw/source/core/doc/docfmt.cxx
index 51c0e935e7b2..ff8d5b0100f7 100644
--- a/sw/source/core/doc/docfmt.cxx
+++ b/sw/source/core/doc/docfmt.cxx
@@ -259,12 +259,12 @@ void SwDoc::ResetAttrs( const SwPaM ,
oExtraPaM.emplace( *rRg.GetPoint() );
pPam = &*oExtraPaM;
-SwContentIndex& rSt = pPam->GetPoint()->nContent;
-sal_Int32 nMkPos, nPtPos = rSt.GetIndex();
+SwPosition& rSt = *pPam->GetPoint();
+sal_Int32 nMkPos, nPtPos = rSt.GetContentIndex();
// Special case: if the Cursor is located within a URL attribute, we
take over it's area
SwTextAttr const*const pURLAttr(
-pTextNd->GetTextAttrAt(rSt.GetIndex(), RES_TXTATR_INETFMT));
+pTextNd->GetTextAttrAt(rSt.GetContentIndex(), RES_TXTATR_INETFMT));
if (pURLAttr && !pURLAttr->GetINetFormat().GetValue().isEmpty())
{
nMkPos = pURLAttr->GetStart();
@@ -286,15 +286,15 @@ void SwDoc::ResetAttrs( const SwPaM ,
}
else
{
-nPtPos = nMkPos = rSt.GetIndex();
+nPtPos = nMkPos = rSt.GetContentIndex();
if( bTextAttr )
pTextNd->DontExpandFormat( nPtPos );
}
}
-rSt = nMkPos;
+rSt.SetContent(nMkPos);
pPam->SetMark();
-pPam->GetPoint()->nContent = nPtPos;
+pPam->GetPoint()->SetContent(nPtPos);
}
// #i96644#
@@ -1647,7 +1647,7 @@ void SwDoc::MoveLeftMargin(const SwPaM& rPam, bool
bRight, bool bModulus,
const SvxTabStopItem& rTabItem = GetDefault( RES_PARATR_TABSTOP );
const sal_Int32 nDefDist = rTabItem.Count() ? rTabItem[0].GetTabPos() :
1134;
const SwPosition = *rPam.Start(), = *rPam.End();
-SwNodeIndex aIdx( rStt.nNode );
+SwNodeIndex aIdx( rStt.GetNode() );
while( aIdx <= rEnd.GetNode() )
{
SwTextNode* pTNd = aIdx.GetNode().GetTextNode();
@@ -1805,7 +1805,7 @@ void SwDoc::SetTextFormatCollByAutoFormat( const
SwPosition& rPos, sal_uInt16 nP
if (pSet && pSet->Count())
{
aPam.SetMark();
-aPam.GetMark()->nContent.Assign(pTNd, pTNd->GetText().getLength());
+aPam.GetMark()->SetContent(pTNd->GetText().getLength());
// sw_redlinehide: don't need layout currently because the only caller
// passes in the properties node
assert(static_cast(pTNd->getLayoutFrame(nullptr))->GetTextNodeForParaProps() == pTNd);
[Libreoffice-bugs] [Bug 151174] sidebar transparency slider isn't hidden when it does not apply
https://bugs.documentfoundation.org/show_bug.cgi?id=151174 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Status|UNCONFIRMED |NEW Keywords||bibisectRequest Ever confirmed|0 |1 --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Confirm the problem in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 943177e0f8074753db25d9a56d15f8010a755ffc CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded I couldn't to bisect it myself because the Area section layout was changed inside 7.4 development path and there is no the transparency slider in oldest step in bisect repo for Linear variant at least (I just try to triage the report with Linear variant). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102283 Bug 102283 depends on bug 42859, which changed state. Bug 42859 Summary: Add settings button for Slide pane to make it easy to configure https://bugs.documentfoundation.org/show_bug.cgi?id=42859 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107817] [META] Impress UI/UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107817 Bug 107817 depends on bug 42859, which changed state. Bug 42859 Summary: Add settings button for Slide pane to make it easy to configure https://bugs.documentfoundation.org/show_bug.cgi?id=42859 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42859] Add settings button for Slide pane to make it easy to configure
https://bugs.documentfoundation.org/show_bug.cgi?id=42859 V Stuart Foote changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #13 from V Stuart Foote --- The ++F10 global LibreOffice dock window frame action works well on this and other panels without a specific View -> Dock frame menu. WFM and IMHO => WF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151154] Change category "draw" in Template Manager and make it translatable
https://bugs.documentfoundation.org/show_bug.cgi?id=151154
Laurent BP changed:
What|Removed |Added
CC||jumbo4...@yahoo.fr
--- Comment #3 from Laurent BP ---
I tried to deep in this bug but I was not able to find a solution.
Categories name are defined in TEMPLATE_LONG_NAMES_ARY[]:
https://opengrok.libreoffice.org/xref/core/sfx2/inc/doctempl.hrc?r=144057a5#27
I added a line
+NC_("TEMPLATE_LONG_NAMES_ARY", "Draw"),
as well as in TEMPLATE_SHORT_NAMES_ARY[]:
https://opengrok.libreoffice.org/xref/core/sfx2/source/doc/doctemplates.cxx?r=91ba9654#483
I added a line at the same position
+"draw",
In addition, templates directories are declared in directory_ooo.scp
https://opengrok.libreoffice.org/xref/core/scp2/source/ooo/directory_ooo.scp?r=14c7bc1c#602
I added this declaration:
+Directory gid_Dir_Template_Common_Draw
+ParentID = gid_Dir_Template_Common;
+DosName = "draw";
+End
+
But all that has no effect :-( I'm still missing something
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151170] Need mechanism for re-centering "Slides pane" onto current slide with edit focus
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 V Stuart Foote changed: What|Removed |Added Summary|Need mechanism for |Need mechanism for |re-centering slide pane |re-centering "Slides pane" |(slide sorter) on current |onto current slide with |slide |edit focus -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering "Slides pane" onto current slide with edit focus
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 V Stuart Foote changed: What|Removed |Added Summary|Need mechanism for |Need mechanism for |re-centering slide pane |re-centering "Slides pane" |(slide sorter) on current |onto current slide with |slide |edit focus -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102283 V Stuart Foote changed: What|Removed |Added Depends on||151170 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151170 [Bug 151170] Need mechanism for re-centering slide pane (slide sorter) on current slide -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 151170] Need mechanism for re-centering slide pane (slide sorter) on current slide
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 V Stuart Foote changed: What|Removed |Added Blocks||102283 OS|Linux (All) |All CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||olivier.hallot@libreoffice. ||org, sdc.bla...@youmail.dk, ||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #1) +1, the slide/page "Slides/Pages pane" needs a control to scroll the pane to expose the active slide/page with edit focus. Currently, except for the dragging the thumb of the scrollbar, it is much too easy to unintentionally change focus to a different slide/page present in the pane. Providing an UNO action to scroll the pane to expose the Slide/Page with edit focus--for use on keyboard, menu and context menu actions would be very helpful. =-=-= As an aside for documentation: > I never get the name of this part of the window right... do we call it the > slide sorter? The slide pane? The slide side-bar? It is the sd "LEFT PANE", with UNO cmds available to toggle it inactive. In Impress it is uno.leftPaneImpress and menu labeled 'Slide Pane' In Draw it is uno.leftPaneDraw and menu labeled 'Page Pane' But in the Impress UI it is labeled 'Slides', and in Draw UI it is labeled 'Pages' Functionally the sd Left Pane, aka "Slides pane" or "Pages pane" in the module guides documentation, can be used to manage slides/pages, e.g. add, duplicate, hide, delete, move for the listed slide/page objects. The Left Pane is incorrectly referred to as the 'Slide Sorter'. That labeling is for a specific editing "view mode" of the Impress workspace--not available in Draw. And the LO help even has the toggle article named "slidesorter.html" adding to the confusion, and that all could probably be clarified. @Olvier, Seth? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102283 [Bug 102283] [META] Slide/page pane bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 151170] Need mechanism for re-centering slide pane (slide sorter) on current slide
https://bugs.documentfoundation.org/show_bug.cgi?id=151170 V Stuart Foote changed: What|Removed |Added Blocks||102283 OS|Linux (All) |All CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||olivier.hallot@libreoffice. ||org, sdc.bla...@youmail.dk, ||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #1) +1, the slide/page "Slides/Pages pane" needs a control to scroll the pane to expose the active slide/page with edit focus. Currently, except for the dragging the thumb of the scrollbar, it is much too easy to unintentionally change focus to a different slide/page present in the pane. Providing an UNO action to scroll the pane to expose the Slide/Page with edit focus--for use on keyboard, menu and context menu actions would be very helpful. =-=-= As an aside for documentation: > I never get the name of this part of the window right... do we call it the > slide sorter? The slide pane? The slide side-bar? It is the sd "LEFT PANE", with UNO cmds available to toggle it inactive. In Impress it is uno.leftPaneImpress and menu labeled 'Slide Pane' In Draw it is uno.leftPaneDraw and menu labeled 'Page Pane' But in the Impress UI it is labeled 'Slides', and in Draw UI it is labeled 'Pages' Functionally the sd Left Pane, aka "Slides pane" or "Pages pane" in the module guides documentation, can be used to manage slides/pages, e.g. add, duplicate, hide, delete, move for the listed slide/page objects. The Left Pane is incorrectly referred to as the 'Slide Sorter'. That labeling is for a specific editing "view mode" of the Impress workspace--not available in Draw. And the LO help even has the toggle article named "slidesorter.html" adding to the confusion, and that all could probably be clarified. @Olvier, Seth? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102283 [Bug 102283] [META] Slide/page pane bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103381 Bug 103381 depends on bug 146844, which changed state. Bug 146844 Summary: PIVOTTABLE Repeated pivot item labels are text, even if original is number https://bugs.documentfoundation.org/show_bug.cgi?id=146844 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146844] PIVOTTABLE Repeated pivot item labels are text, even if original is number
https://bugs.documentfoundation.org/show_bug.cgi?id=146844 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> --- Nice, thanks. So closed as WFM (because we don't know what was the patch) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: compilerplugins/clang include/svl svl/source sw/inc sw/source
compilerplugins/clang/unusedmethods.results |2 -
include/svl/hint.hxx|1
svl/source/items/poolitem.cxx |1
sw/inc/hintids.hxx |2 -
sw/inc/hints.hxx| 15
sw/source/core/attr/hints.cxx | 10 ++---
sw/source/core/text/txtfrm.cxx | 47 ++--
sw/source/core/txtnode/ndtxt.cxx| 13 +++
8 files changed, 45 insertions(+), 46 deletions(-)
New commits:
commit eb1294a60783ceb450cefd6891d6eafa0021aadc
Author: Bjoern Michaelsen
AuthorDate: Sun Sep 25 11:34:10 2022 +0200
Commit: Bjoern Michaelsen
CommitDate: Sun Sep 25 20:01:53 2022 +0200
unwrap SwDelChr to plain SfxHint
Change-Id: Ief37a8025181b6cc8a6e484e2726d8a8d92f57ea
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140567
Tested-by: Jenkins
Reviewed-by: Bjoern Michaelsen
diff --git a/compilerplugins/clang/unusedmethods.results
b/compilerplugins/clang/unusedmethods.results
index be732177c36b..524af6ade80c 100644
--- a/compilerplugins/clang/unusedmethods.results
+++ b/compilerplugins/clang/unusedmethods.results
@@ -1592,8 +1592,6 @@ include/svl/typedwhich.hxx:31
TypedWhichId::TypedWhichId(TypedWhichId,typename
enable_if, int>::type)
include/svl/typedwhich.hxx:31
TypedWhichId::TypedWhichId(TypedWhichId,typename
enable_if, int>::type)
-include/svl/typedwhich.hxx:31
- TypedWhichId::TypedWhichId(TypedWhichId,typename
enable_if, int>::type)
include/svl/typedwhich.hxx:31
TypedWhichId::TypedWhichId(TypedWhichId,typename
enable_if, int>::type)
include/svl/typedwhich.hxx:31
diff --git a/include/svl/hint.hxx b/include/svl/hint.hxx
index 4b4677cd768d..22f0bb8eb7e2 100644
--- a/include/svl/hint.hxx
+++ b/include/svl/hint.hxx
@@ -142,6 +142,7 @@ enum class SfxHintId {
SwNameChanged, // this can possibly be replaced by the generic NameChanged
above
SwInsertText,
SwDeleteText,
+SwDeleteChar,
ThisIsAnSdrHint
};
diff --git a/svl/source/items/poolitem.cxx b/svl/source/items/poolitem.cxx
index 32dfebb51747..225678340a1c 100644
--- a/svl/source/items/poolitem.cxx
+++ b/svl/source/items/poolitem.cxx
@@ -434,7 +434,6 @@
// class SwMsgPoolItem : public SfxPoolItem
// class SwPtrMsgPoolItem : public SwMsgPoolItem
// class SwFormatChg: public SwMsgPoolItem
-// class SwDelChr: public SwMsgPoolItem
// class SwUpdateAttr : public SwMsgPoolItem
// class SwRefMarkFieldUpdate : public SwMsgPoolItem
// class SwDocPosUpdate : public SwMsgPoolItem
diff --git a/sw/inc/hintids.hxx b/sw/inc/hintids.hxx
index afe2df275aaa..497635f71f5b 100644
--- a/sw/inc/hintids.hxx
+++ b/sw/inc/hintids.hxx
@@ -133,7 +133,6 @@ class SwTableBoxNumFormat;
class SwTextGridItem;
class SwTransparencyGrf;
class SwFormatRuby;
-class SwDelChr;
class SwRefMarkFieldUpdate;
class SwTableFormulaUpdate;
class SwAutoFormatGetDocNode;
@@ -422,7 +421,6 @@ constexpr sal_uInt16 RES_MSG_BEGIN(RES_FMT_END);
constexpr TypedWhichId RES_OBJECTDYING(RES_MSG_BEGIN); // 161
constexpr TypedWhichId RES_FMT_CHG(162);
constexpr TypedWhichId RES_ATTRSET_CHG(163);
-constexpr TypedWhichId RES_DEL_CHR(165);
constexpr TypedWhichId RES_UPDATE_ATTR(167);
constexpr TypedWhichId RES_REFMARKFLD_UPDATE(168);
constexpr TypedWhichId RES_DOCPOS_UPDATE(169);
diff --git a/sw/inc/hints.hxx b/sw/inc/hints.hxx
index 78952b288193..777825ae4969 100644
--- a/sw/inc/hints.hxx
+++ b/sw/inc/hints.hxx
@@ -76,13 +76,6 @@ public:
SwFormatChg( SwFormat *pFormat );
};
-class SwDelChr final : public SwMsgPoolItem
-{
-public:
-sal_Int32 nPos;
-
-SwDelChr( sal_Int32 nP );
-};
namespace sw {
@@ -119,6 +112,14 @@ public:
DeleteText( sal_Int32 nS, sal_Int32 nL );
};
+class DeleteChar final : public SfxHint
+{
+public:
+const sal_Int32 m_nPos;
+
+DeleteChar( const sal_Int32 nPos );
+};
+
/// new delete redline is created
class RedlineDelText final : public SfxHint
{
diff --git a/sw/source/core/attr/hints.cxx b/sw/source/core/attr/hints.cxx
index 76a5113eed46..3257d5736900 100644
--- a/sw/source/core/attr/hints.cxx
+++ b/sw/source/core/attr/hints.cxx
@@ -33,11 +33,6 @@ SwFormatChg::SwFormatChg( SwFormat* pFormat )
}
-SwDelChr::SwDelChr( sal_Int32 nP )
-: SwMsgPoolItem( RES_DEL_CHR ), nPos( nP )
-{
-}
-
namespace sw {
@@ -59,6 +54,11 @@ DeleteText::DeleteText( const sal_Int32 nS, const sal_Int32
nL )
{
}
+DeleteChar::DeleteChar( const sal_Int32 nPos )
+: SfxHint( SfxHintId::SwDeleteChar ), m_nPos( nPos )
+{
+}
+
RedlineDelText::RedlineDelText(sal_Int32 const nS, sal_Int32 const nL)
: nStart(nS), nLen(nL)
{
diff --git a/sw/source/core/text/txtfrm.cxx b/sw/source/core/text/txtfrm.cxx
index 1de6c91cc633..22a8a0bc0ae1 100644
--- a/sw/source/core/text/txtfrm.cxx
+++ b/sw/source/core/text/txtfrm.cxx
@@ -1977,6 +1977,7 @@ void SwTextFrame::SwClientNotify(SwModify const& rModify,
SfxHint
[Libreoffice-bugs] [Bug 146844] PIVOTTABLE Repeated pivot item labels are text, even if original is number
https://bugs.documentfoundation.org/show_bug.cgi?id=146844 --- Comment #3 from Nis Jørgensen --- Confirming that this is fixed in 7.4.1.2. I am not certain of procedures around here, but I believe the status of this bug could be changed to RESOLVED. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/doc/doccorr.cxx |2 +-
sw/source/core/doc/docedt.cxx |4 ++--
sw/source/core/doc/docfld.cxx |3 +--
3 files changed, 4 insertions(+), 5 deletions(-)
New commits:
commit b0cab944460816b96921bf4efd76e25d1cf75816
Author: Noel Grandin
AuthorDate: Sun Sep 25 18:23:19 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 19:36:39 2022 +0200
use more SwPosition::SetContent
part of the process of hiding the internals of SwPosition
Change-Id: I466640e5cf7aac57b0248e9a5069e75ccd7e779a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140572
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/doc/doccorr.cxx b/sw/source/core/doc/doccorr.cxx
index b4167611f8e9..a98fedb58708 100644
--- a/sw/source/core/doc/doccorr.cxx
+++ b/sw/source/core/doc/doccorr.cxx
@@ -176,7 +176,7 @@ void SwDoc::CorrAbs(const SwNode& rOldNode,
SwPaM const aPam(rOldNode, 0,
rOldNode, pContentNode ? pContentNode->Len() : 0);
SwPosition aNewPos(rNewPos);
-aNewPos.nContent += nOffset;
+aNewPos.AdjustContent(nOffset);
getIDocumentMarkAccess()->correctMarksAbsolute(rOldNode, rNewPos, nOffset);
// fix redlines
diff --git a/sw/source/core/doc/docedt.cxx b/sw/source/core/doc/docedt.cxx
index 56eb5a6065aa..daf3a00d83dd 100644
--- a/sw/source/core/doc/docedt.cxx
+++ b/sw/source/core/doc/docedt.cxx
@@ -84,9 +84,9 @@ void RestFlyInRange( SaveFlyArr & rArr, const SwPosition&
rStartPos,
}
else
{
-aPos.nNode = rStartPos.GetNodeIndex() + rSave.nNdDiff;
+aPos.Assign(rStartPos.GetNodeIndex() + rSave.nNdDiff);
assert(aPos.GetNode().GetContentNode());
-aPos.nContent.Assign(aPos.GetNode().GetContentNode(),
+aPos.SetContent(
rSave.nNdDiff == SwNodeOffset(0)
? rStartPos.GetContentIndex() + rSave.nContentIndex
: rSave.nContentIndex);
diff --git a/sw/source/core/doc/docfld.cxx b/sw/source/core/doc/docfld.cxx
index f6f9cc210824..03afc4668401 100644
--- a/sw/source/core/doc/docfld.cxx
+++ b/sw/source/core/doc/docfld.cxx
@@ -193,8 +193,7 @@ void SetGetExpField::GetPosOfContent( SwPosition& rPos )
const
if( pNd )
{
-rPos.nNode = *pNd;
-rPos.nContent.Assign( static_cast(pNd),
GetCntPosFromContent() );
+rPos.Assign( *static_cast(pNd),
GetCntPosFromContent() );
}
else
{
[Libreoffice-commits] core.git: sw/source
sw/source/core/crsr/findattr.cxx |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
New commits:
commit 16429ec437f4bf2acf33b4b2d968b45548f779b4
Author: Noel Grandin
AuthorDate: Sun Sep 25 18:16:21 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 19:36:22 2022 +0200
use more SwPosition::SetContent
part of the process of hiding the internals of SwPosition
Change-Id: I20052ec81800ce206877bc1781297e5c13fb400c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140571
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sw/source/core/crsr/findattr.cxx b/sw/source/core/crsr/findattr.cxx
index 20d52b2a95c7..79f9e5751906 100644
--- a/sw/source/core/crsr/findattr.cxx
+++ b/sw/source/core/crsr/findattr.cxx
@@ -109,17 +109,16 @@ static void lcl_SetAttrPam( SwPaM& rPam, sal_Int32
nStart, const sal_Int32* pEnd
nContentPos = rPam.GetPoint()->GetContentIndex();
bool bTstEnd = rPam.GetPoint()->GetNode() == rPam.GetMark()->GetNode();
-SwContentNode* pCNd = rPam.GetPointContentNode();
-rPam.GetPoint()->nContent.Assign( pCNd, nStart );
+rPam.GetPoint()->SetContent( nStart );
rPam.SetMark(); // Point == GetMark
// Point points to end of search area or end of attribute
if( pEnd )
{
if( bTstEnd && *pEnd > nContentPos )
-rPam.GetPoint()->nContent = nContentPos;
+rPam.GetPoint()->SetContent(nContentPos);
else
-rPam.GetPoint()->nContent = *pEnd;
+rPam.GetPoint()->SetContent(*pEnd);
}
}
[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=150715 Noel Grandin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=150715 --- Comment #2 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/916d30ba7e8a5293f57ec04258f6c3839736295e tdf#150715 Animations in LO Impress do not work properly It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150715] Animations in LO Impress do not work properly
https://bugs.documentfoundation.org/show_bug.cgi?id=150715 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sd/source
sd/source/core/CustomAnimationEffect.cxx |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
New commits:
commit 916d30ba7e8a5293f57ec04258f6c3839736295e
Author: Noel Grandin
AuthorDate: Sun Sep 25 18:09:25 2022 +0200
Commit: Noel Grandin
CommitDate: Sun Sep 25 19:09:37 2022 +0200
tdf#150715 Animations in LO Impress do not work properly
Revert "updatePathFromSdrPathObj can just call getRange"
This reverts commit 7c52337f9517135db13d75ecbbc10d7e26e01489.
Not sure why this change did not work.
Change-Id: I2c42b9b7ff4b85f3018bea289efd3d934dbe2be1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140570
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sd/source/core/CustomAnimationEffect.cxx
b/sd/source/core/CustomAnimationEffect.cxx
index 52220afe7525..b74179dfb1f7 100644
--- a/sd/source/core/CustomAnimationEffect.cxx
+++ b/sd/source/core/CustomAnimationEffect.cxx
@@ -1606,8 +1606,10 @@ void CustomAnimationEffect::updatePathFromSdrPathObj(
const SdrPathObj& rPathObj
{
::tools::Rectangle aBoundRect(0,0,0,0);
+drawinglayer::primitive2d::Primitive2DContainer xPrimitives;
+
pObj->GetViewContact().getViewIndependentPrimitive2DContainer(xPrimitives);
const drawinglayer::geometry::ViewInformation2D aViewInformation2D;
-const basegfx::B2DRange aRange =
pObj->GetViewContact().getRange(aViewInformation2D);
+const basegfx::B2DRange
aRange(xPrimitives.getB2DRange(aViewInformation2D));
if(!aRange.isEmpty())
{
[Libreoffice-bugs] [Bug 141279] REGRESSION: Overwriting a file open in LibreOffice succeeds in recent builds, should fail
https://bugs.documentfoundation.org/show_bug.cgi?id=141279 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1176 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open
https://bugs.documentfoundation.org/show_bug.cgi?id=151176 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1279 --- Comment #2 from Mike Kaganski --- Indeed, it's strange that Windows (or any software) can't use special file open mode created specifically for backup purposes: note e.g. FILE_FLAG_BACKUP_SEMANTICS in CreateFile documentation [1]. However, it would be still be interesting to learn exact reproduction steps, and the logs; only one thing should be taken into account first. Recently, LibreOffice file locking had been changed (see tdf#141279), so it could change in the last program versions. [1] https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilew -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150616] FILESAVE PDF Table row disappears from complex table after CLI PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=150616 Kevin Suo changed: What|Removed |Added Version|7.4.0.3 release |7.3.2.2 release CC||suokunl...@126.com --- Comment #7 from Kevin Suo --- This also happens in 7.3 branch. The commit which caused this regression was also cherry-picked to 7.3 (version 7.3.2.0.0+) https://gerrit.libreoffice.org/c/core/+/129845 Revise version field to 7.3.2.2 accordingly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open
https://bugs.documentfoundation.org/show_bug.cgi?id=151176 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151176] windows 10 backup failure whenever I have a LibreOffice file open
https://bugs.documentfoundation.org/show_bug.cgi?id=151176 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #1 from Eike Rathke --- Blame Windows for not being able to backup files that are opened exclusive by an application. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: scaddins/inc sc/inc
sc/inc/scfuncs.hrc|4 ++--
scaddins/inc/analysis.hrc |4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
New commits:
commit 7dca847f07c57591d20b6a2c618bfd8bfe62a09f
Author: Eike Rathke
AuthorDate: Sun Sep 25 16:53:52 2022 +0200
Commit: Eike Rathke
CommitDate: Sun Sep 25 17:39:53 2022 +0200
Resolves: tdf#151165 Function Wizard: ISODD()/ISEVEN() truncate to integer
Change-Id: I73d06c6c40ac33f59cf38218b3e696de9aeb0b87
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140569
Reviewed-by: Eike Rathke
Tested-by: Jenkins
diff --git a/sc/inc/scfuncs.hrc b/sc/inc/scfuncs.hrc
index 12d59858260e..830f041c1536 100644
--- a/sc/inc/scfuncs.hrc
+++ b/sc/inc/scfuncs.hrc
@@ -1061,7 +1061,7 @@ const TranslateId SC_OPCODE_RANDOM_ARY[] =
// -=*# Resource for function ISEVEN #*=-
const TranslateId SC_OPCODE_IS_EVEN_ARY[] =
{
-NC_("SC_OPCODE_IS_EVEN", "Returns TRUE if value is an even integer."),
+NC_("SC_OPCODE_IS_EVEN", "Returns TRUE if the value truncated to integer
is even."),
NC_("SC_OPCODE_IS_EVEN", "Value"),
NC_("SC_OPCODE_IS_EVEN", "The value to be tested.")
};
@@ -1069,7 +1069,7 @@ const TranslateId SC_OPCODE_IS_EVEN_ARY[] =
// -=*# Resource for function ISODD #*=-
const TranslateId SC_OPCODE_IS_ODD_ARY[] =
{
-NC_("SC_OPCODE_IS_ODD", "Returns TRUE if value is an odd integer."),
+NC_("SC_OPCODE_IS_ODD", "Returns TRUE if the value truncated to integer is
odd."),
NC_("SC_OPCODE_IS_ODD", "Value"),
NC_("SC_OPCODE_IS_ODD", "The value to be tested.")
};
diff --git a/scaddins/inc/analysis.hrc b/scaddins/inc/analysis.hrc
index e20d7c73f22e..385091151d48 100644
--- a/scaddins/inc/analysis.hrc
+++ b/scaddins/inc/analysis.hrc
@@ -85,14 +85,14 @@ const TranslateId ANALYSIS_Networkdays[] =
const TranslateId ANALYSIS_Iseven[] =
{
-NC_("ANALYSIS_Iseven", "Returns the value 'true' if the number is even"),
+NC_("ANALYSIS_Iseven", "Returns the value 'true' if the number truncated
to integer is even"),
NC_("ANALYSIS_Iseven", "Number"),
NC_("ANALYSIS_Iseven", "The number")
};
const TranslateId ANALYSIS_Isodd[] =
{
-NC_("ANALYSIS_Isodd", "Returns the value 'true' if the number is odd"),
+NC_("ANALYSIS_Isodd", "Returns the value 'true' if the number truncated to
integer is odd"),
NC_("ANALYSIS_Isodd", "Number"),
NC_("ANALYSIS_Isodd", "The number")
};
[Libreoffice-bugs] [Bug 150658] The behavior of the Formatting toolbar has changed in 7.4.0.3 from 7.3 and prior when copying and pasting individual Writer table rows.
https://bugs.documentfoundation.org/show_bug.cgi?id=150658 Dieter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||dgp-m...@gmx.de Resolution|--- |NOTABUG --- Comment #1 from Dieter --- I confirm the described behaviour with Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL but for me it sounds like a bug, that has been fixed. It's the normal behaviour of every text, that you copy and paste (doesn't matter, if source text is from another document, part of a table or not). If you want to retain actual (bold) formatting you have to insert text as unformatted text. => RESOLVED NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 115645] Should be able to permanently delete comments with track changes enabled.
https://bugs.documentfoundation.org/show_bug.cgi?id=115645 --- Comment #12 from gutkowski --- I don't understand how someone could accept merely comment delete. What precisely would you do if you wanted to recover 25 TC erased comments? I disagree with the statement "WontFix" (which stands for "Should Never Be Fixed, even if a developer"). https://cookie-clicker2.co -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 115645] Should be able to permanently delete comments with track changes enabled.
https://bugs.documentfoundation.org/show_bug.cgi?id=115645 --- Comment #12 from gutkowski --- I don't understand how someone could accept merely comment delete. What precisely would you do if you wanted to recover 25 TC erased comments? I disagree with the statement "WontFix" (which stands for "Should Never Be Fixed, even if a developer"). https://cookie-clicker2.co -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61242] Customise comments background color in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=61242 --- Comment #29 from gutkowski --- The nice comments to ranges option, which uses a backdrop color similar to the comment box, has made it even more urgent. https://geometrydash-free.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-4' - sw/inc sw/source
sw/inc/unoredline.hxx |3 +++
sw/source/core/unocore/unoredline.cxx |5 +
2 files changed, 8 insertions(+)
New commits:
commit c80a3ef9f434230ae3d5ffec902edc19f34f75f7
Author: Michael Stahl
AuthorDate: Fri Sep 23 18:11:56 2022 +0200
Commit: Caolán McNamara
CommitDate: Sun Sep 25 17:05:28 2022 +0200
rhbz#2122948 sw: fix ODF import of fieldmark in redline
The problem is that SwXText::compareRegionStarts() calls
SwXText::CreateCursor() which creates a cursor on the last node in the
body text, but it's actually a redline.
Override SwXRedlineText::CreateCursor() to create a cursor in the
redline text.
Complete mystery why SwXText has 2 virtual functions to create
cursors in the first place.
(regression from commit 463178fef5c22f1a04d10e54491852d56e2038b0)
Change-Id: I0f3bcf4eda25f1ac7e1c1b0cf47a920f8302d2b7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/140504
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sw/inc/unoredline.hxx b/sw/inc/unoredline.hxx
index a73ede766af6..3a7273a199d7 100644
--- a/sw/inc/unoredline.hxx
+++ b/sw/inc/unoredline.hxx
@@ -39,6 +39,9 @@ class SwXRedlineText final :
SwNodeIndex m_aNodeIndex;
virtual const SwStartNode *GetStartNode() const override;
+virtual css::uno::Reference< css::text::XTextCursor >
+CreateCursor() override;
+
public:
SwXRedlineText(SwDoc* pDoc, const SwNodeIndex& aNodeIndex);
diff --git a/sw/source/core/unocore/unoredline.cxx
b/sw/source/core/unocore/unoredline.cxx
index 197a5542b072..942243e0cd0f 100644
--- a/sw/source/core/unocore/unoredline.cxx
+++ b/sw/source/core/unocore/unoredline.cxx
@@ -90,6 +90,11 @@ uno::Sequence SwXRedlineText::getImplementationId()
return css::uno::Sequence();
}
+uno::Reference SwXRedlineText::CreateCursor()
+{
+return createTextCursor();
+}
+
uno::Reference SwXRedlineText::createTextCursor()
{
SolarMutexGuard aGuard;
[Libreoffice-bugs] [Bug 107899] [META] PPTX paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107899 Aron Budea changed: What|Removed |Added Depends on||151134 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151134 [Bug 151134] FILESAVE PPTX: indentation of second (and other) textbox(es) shifts to the left -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151134] FILESAVE PPTX: indentation of second (and other) textbox(es) shifts to the left
https://bugs.documentfoundation.org/show_bug.cgi?id=151134 Aron Budea changed: What|Removed |Added Regression By||Attila Bakos (NISZ) Blocks||107899 Keywords||bibisected, bisected, ||regression CC||aron.bu...@gmail.com, ||nem...@numbertext.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||1903, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7152 --- Comment #4 from Aron Budea --- This is actually a regression in 7.2, bibisected to the following commit, bibisected using repo bibisect-linux-64-7.2. Adding CC: to Attila Bakos (NISZ) and László Németh. https://cgit.freedesktop.org/libreoffice/core/commit/?id=b6b02e0b4c9d739836e1f61a886ea45b01e6696e author Attila Bakos (NISZ) 2021-04-20 13:02:44 +0200 committer László Németh2021-04-29 10:48:27 +0200 tdf#111903 tdf#137152 PPTX export: fix placeholders Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107899 [Bug 107899] [META] PPTX paragraph-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56408] Writer always breaks lines at text direction change
https://bugs.documentfoundation.org/show_bug.cgi?id=56408 خالد حسني changed: What|Removed |Added CC||j3frea+documentfoundation@g ||mail.com --- Comment #24 from خالد حسني --- *** Bug 146710 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112812] [META] Hebrew language-specific RTL issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112812 Bug 112812 depends on bug 146710, which changed state. Bug 146710 Summary: Incorrect wrapping of neutral characters in CTL https://bugs.documentfoundation.org/show_bug.cgi?id=146710 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146710] Incorrect wrapping of neutral characters in CTL
https://bugs.documentfoundation.org/show_bug.cgi?id=146710 خالد حسني changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC||kha...@aliftype.com --- Comment #2 from خالد حسني --- *** This bug has been marked as a duplicate of bug 56408 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151165] [EDITING] [DOCUMENTATION] ISODD and ISEVEN behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=151165 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED Version|7.3.6.2 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151176] New: windows 10 backup failure whenever I have a LibreOffice file open
https://bugs.documentfoundation.org/show_bug.cgi?id=151176 Bug ID: 151176 Summary: windows 10 backup failure whenever I have a LibreOffice file open Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: collinca...@gmail.com Description: Over the past few months I've had several (many) automatic Backup failures. Only recently, on a whim, did I try closing LO files before going to bed for the auto Backup. Since then, without fail, it has been successful. Except that, yesterday, on a whim, I manually started Backup with an open LO file running. Fail. If you're interested I will replicate a failure and give you Error notices. whatever. Basically, I remember "Failure to produce shadow copy" "timeout" "refer to VSS & SPP event logs" Steps to Reproduce: 1. see above 2. 3. Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info: Although I've rated it as "minor" it's only minor once I realised the connection between LO and Backup. Getting to that realisation was pure chance! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150409] Style inspector: CJK & CTL properties should never be hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150409 --- Comment #15 from Commit Notification --- Liu Hao committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f65ca3470ea2ede39314668348607dd061d003fe tdf#150409 CJK properties shouldn't be hidden in Style Inspector It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150409] Style inspector: CJK & CTL properties should never be hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150409 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: svx/source
svx/source/sidebar/inspector/InspectorTextPanel.cxx |7 ---
1 file changed, 7 deletions(-)
New commits:
commit f65ca3470ea2ede39314668348607dd061d003fe
Author: Liu Hao
AuthorDate: Wed Aug 24 17:28:24 2022 +0800
Commit: Mike Kaganski
CommitDate: Sun Sep 25 16:33:17 2022 +0200
tdf#150409 CJK properties shouldn't be hidden in Style Inspector
Change-Id: I577e4c90eb000e3f55f5be9e14132a4c1d16fe9a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/138755
Tested-by: خالد حسني
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/svx/source/sidebar/inspector/InspectorTextPanel.cxx
b/svx/source/sidebar/inspector/InspectorTextPanel.cxx
index 0b5da3d2d14e..3ddba2db9e58 100644
--- a/svx/source/sidebar/inspector/InspectorTextPanel.cxx
+++ b/svx/source/sidebar/inspector/InspectorTextPanel.cxx
@@ -58,13 +58,6 @@ InspectorTextPanel::InspectorTextPanel(weld::Widget* pParent)
static bool GetPropertyValues(std::u16string_view rPropName, const uno::Any&
rAny,
OUString& rString)
{
-// Hide Asian and Complex properties
-if (!SvtCJKOptions::IsCJKFontEnabled() && rPropName.find(u"Asian") !=
std::u16string_view::npos)
-return false;
-if (!SvtCTLOptions().IsCTLFontEnabled()
-&& rPropName.find(u"Complex") != std::u16string_view::npos)
-return false;
-
if (bool bValue; rAny >>= bValue)
{
rString = SvxResId(bValue ? RID_TRUE : RID_FALSE); // tdf#139136
[Libreoffice-bugs] [Bug 126574] description of macro security level settings is misleading or wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=126574 --- Comment #3 from Toni Dietze --- The issue is still present on current master: https://git.libreoffice.org/core/+/567b4281b96f56ce48d3feb57522255b06816f9b/xmlsecurity/uiconfig/ui/securitylevelpage.ui I also checked that it is still present in the packaged version on Arch Linux: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US 7.3.6-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98682] Wrong text direction after copy/paste from web browser to LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=98682 خالد حسني changed: What|Removed |Added CC||kha...@aliftype.com --- Comment #30 from خالد حسني --- I think this a feature, not a bug. When opening a blank document in an RTL locale, the default page style will have direction set to Right To Left, and paragraph direction is not explicitly set. This, I think, under the assumption that if you are using an RTL locale you are most likely to be creating RTL documents. The reverse is true as well, if the locale is LTR the page direction will be LTR. The best fix is for the user to set the page direction explicitly, or when mixing RTL and LTR text, set the direction of the paragraphs. We can try to detect paragraph direction based in the pasted content, but this seems to be a fragile thing to do (what if one is pasting into an existing paragraph). Alternatively we might want an “auto” paragraph direction setting that uses the direction from the paragraph content, but that is a much bigger change. My suggestion is to close as NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151156] File not found
https://bugs.documentfoundation.org/show_bug.cgi?id=151156 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- I was having a similar problem using the help when I built it locally. When you press F1 LibreOffice creates a temporary file in /tmp which cannot be accessed by Firefox snap (see [1]). I fixed it by changing the temporary folder used by LO (Tools - Options - Paths). [1] https://bugs.launchpad.net/snapd/+bug/1972762 Try creating a temporary folder in your user directory (f.i. /home/your_user/tmp) and set it as the temporary folder used by LO. Maybe this will fix the issue. -- You are receiving this mail because: You are the assignee for the bug.
