[Libreoffice-bugs] [Bug 32531] Incorrect cursor key movement between table cells of different directionality
https://bugs.documentfoundation.org/show_bug.cgi?id=32531 Eyal changed: What|Removed |Added Version|unspecified |Inherited From OOo --- Comment #31 from Eyal --- The bug is still present as described in my initial report. Checked again with MS Word and it behaves as expected, ie. in a table with mixed directionality cursor movement is consistent with the main directionality. NOTE: In Word, the role of the cursor keys is reversed when switching from the main directionality to the opposite directionality. For example, if the main directionality is LTR, with an RTL word (or table cell) in the middle, then using the right cursor key keeps moving to the next character, even when in the RTL word, so in effect the right cursor key visually moves the cursor to the left. Let's say LLL represents LTR text and RRR represents RTL text. The cursor is at the beginning of the text, and the users just presses the right-arrow key. This is hos the cursor moves: LLL RRR LLL <<< It doesn't matter whether this is plain text or table cells. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146490] UI: Field in a header/footer (like page number) lists a single time in navigator (and only for last page)
https://bugs.documentfoundation.org/show_bug.cgi?id=146490 --- Comment #7 from Jim Raykowski --- (In reply to Telesto from comment #6) > I encountered the same problem in slightly different consternation at bug > 146491. Where it seems - no understanding of the code - that hidden fields > are written to DOCX. Which is likely wrong (polluting the file). Which makes > showing hidden fields in navigator more of a feature Seems the revert patch for bug 146491 only solves that particular issue. I can still make hidden fields appear in the Navigator upon adding a Header to the example file or unchecking the 'Same content on left and right pages' option in the Page Style Header and/or Footer tab(s). Definitely will dig through the code to try to find out why this happens and if it can be changed before throwing in the towel and doing a hack around. Showing hidden fields may be useful when a field is in a hidden section or in folded outline content. -- You are receiving this mail because: You are the assignee for the bug.
Re: Question about cppuhelper/compbase and other compbase1/2/.../12
Those are from the days before we had reliable variable-parameters-templates. We can't remove them because they are part of the published API.
[Libreoffice-bugs] [Bug 61963] UI: 'Group and Outline' impossible with active Filter
https://bugs.documentfoundation.org/show_bug.cgi?id=61963 Rainer Bielefeld Retired changed: What|Removed |Added CC||LibreOffice@bielefeldundbus ||s.de --- Comment #12 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139612] Option "Search criteria = and <> must apply to whole cells" doesn't affect to calculation as must.
https://bugs.documentfoundation.org/show_bug.cgi?id=139612 Mike Kaganski changed: What|Removed |Added CC||hailholyqu...@gmx.de --- Comment #19 from Mike Kaganski --- *** Bug 146657 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 146657] COUNTIF mismatches Text
https://bugs.documentfoundation.org/show_bug.cgi?id=146657 Mike Kaganski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- Generally COUNTIF depends on what is selected at Options->LibreOffice->Calculate, General Calculations/Search criteria = and <> must apply to whole cells. However, until recently, there was bug 139612, fixed in 7.2.5. *** This bug has been marked as a duplicate of bug 139612 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #2 from John --- The file was ODT, not DOC or DOCX I included only the content.xml and not the document itself by intent. I don't want to share my template. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #1 from John --- Created attachment 177405 --> https://bugs.documentfoundation.org/attachment.cgi?id=177405=edit contentxml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: i18nlangtag/source
i18nlangtag/source/isolang/mslangid.cxx |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
New commits:
commit 7650d164a1e9c34ce99bf30bf4198e7ceb21fb5d
Author: Hossein
AuthorDate: Sat Jan 8 23:24:38 2022 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Sun Jan 9 04:58:11 2022 +0100
tdf#146084 No hyphenation warning for Vietnamese
The Vietnamese language does not use hyphenation, so LO should not
warn for lack of hyphenation data. This was described in the commit
message of 151c56ed547490a99d912524c0e56b5d6d4a1939, but the actual
code for fixing the problem for Vietnamese langauge was missing.
This patch, adds the Vietnamese language to the list of languages
that do not use hyphenation, so the warning for the lack of
hyphenation data will no longer be displayed for this language.
As described in the above commit:
"In Vietnamese all words consist of single syllables, so they are
often very short; hyphenation is not allowed at all."
https://tug.org/TUGboat/tb29-1/tb91thanh-vntex.pdf
Hyphenation is declined in Vietnamese orthography since 1975
https://www.quora.com/When-did-hyphenation-decline-in-Vietnamese-orthography
Change-Id: Id8d3681ad0a93065e61e9da2422af64793fbc111
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128177
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/i18nlangtag/source/isolang/mslangid.cxx
b/i18nlangtag/source/isolang/mslangid.cxx
index ad062a8d3dcf..0143ea228596 100644
--- a/i18nlangtag/source/isolang/mslangid.cxx
+++ b/i18nlangtag/source/isolang/mslangid.cxx
@@ -178,7 +178,8 @@ bool MsLangId::usesHyphenation(LanguageType nLang)
primary(LANGUAGE_USER_MALAY_ARABIC_MALAYSIA),
primary(LANGUAGE_SOMALI),
primary(LANGUAGE_SWAHILI),
-primary(LANGUAGE_URDU_PAKISTAN))
+primary(LANGUAGE_URDU_PAKISTAN),
+primary(LANGUAGE_VIETNAMESE))
|| isCJK(nLang))
{
return false;
[Libreoffice-bugs] [Bug 146661] New: Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 Bug ID: 146661 Summary: Linked images are missing Product: LibreOffice Version: 7.2.4.1 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: I don't know how to reproduced, but I'm really pissed off. Two days ago I created a document with 5 linked images. A very simple one, really. One image per page, png/jpg, and a small caption after it. Everything worked fine. Today I opened the document just to see that the first (house.jpg) and third (boris.png) images are missing. No, I don't mean that writer show me "image not found" placeholder. They simply missing. What the heck. I really want to use Writer over Word because it have table styles. But I simply cannot. Writer is actually pre-pre-alpha. How can I use software that will sinetly, like a Japanese shinobi, kill my data, harm my documents? This is the worst possible thing the software can do. Silently. Harm. User's. Files. I would be OK to pay $500 for S T A B L E Writer. But. If LO if so unstable, then maybe you should make a public announce that this is just pre-pre-pre-alpha and nobody should take it seriously unless the version 0.5 is ready? The problem is not just missing images. Few years ago there was a similar bug (now fixed) when Writer silently removed any formatting. That is, you will notice the missing formatting only when you open the document next time. Everybody blame Microsoft FUD (Fear, uncertainty, and doubt) "propaganda" about open-source software. I don't care what Microsoft says, but the bugs like the ones described above do exactly the same: they make me feel fear, uncertainty, and doubt. How can I trust the software after this? It's like one night you awaked and see your wife with a knife near your neck, and she crazy laught. It would be quite hard to trust her after this, right? Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/content.cxx | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
New commits:
commit 35d8a3f15266e5280c9a1255417c47b5ad22a5e6
Author: Jim Raykowski
AuthorDate: Sun Jan 2 22:17:33 2022 -0900
Commit: Jim Raykowski
CommitDate: Sun Jan 9 04:50:29 2022 +0100
SwNavigator: Fix outline select when table is the only content
Prior to this patch for outline content having only a table(s), right-
click on an outline entry without the cursor and choosing 'Select' from
the context menu only selects the outline paragraph when the current
cursor position in the document is after the outline to be selected.
The solution given here is to move the document cursor to the outline
being selected before the outline selection is made.
Change-Id: Ie25bfc81306dfb10a8ced8369e0ee7de0f3eacff
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127884
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/source/uibase/utlui/content.cxx
b/sw/source/uibase/utlui/content.cxx
index 0be83743b438..19bf803c6fe9 100644
--- a/sw/source/uibase/utlui/content.cxx
+++ b/sw/source/uibase/utlui/content.cxx
@@ -4645,10 +4645,16 @@ void SwContentTree::ExecuteContextMenuAction(const
OString& rSelectedPopupEntry)
const ContentTypeId eTypeId = pCnt->GetParent()->GetType();
if (eTypeId == ContentTypeId::OUTLINE)
{
+SwOutlineNodes::size_type nActPos =
reinterpret_cast(
+
m_xTreeView->get_id(*xFirst).toInt64())->GetOutlinePos();
+m_pActiveShell->GotoOutline(nActPos);
m_xTreeView->selected_foreach([this](weld::TreeIter& rEntry){
+SwOutlineNodes::size_type nPos =
reinterpret_cast(
+
m_xTreeView->get_id(rEntry).toInt64())->GetOutlinePos();
m_pActiveShell->SttSelect();
-SwOutlineNodes::size_type nActPos =
reinterpret_cast(m_xTreeView->get_id(rEntry).toInt64())->GetOutlinePos();
-m_pActiveShell->MakeOutlineSel(nActPos, nActPos,
!m_xTreeView->get_row_expanded(rEntry), false); // select children if not
expanded
+// select children if not expanded and don't kill PaMs
+m_pActiveShell->MakeOutlineSel(nPos, nPos,
+
!m_xTreeView->get_row_expanded(rEntry), false);
m_pActiveShell->EndSelect();
return false;
});
[Libreoffice-bugs] [Bug 146398] Gtk3: crash when quickly switching between comments in sidebar after I edited the previous comment
https://bugs.documentfoundation.org/show_bug.cgi?id=146398 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 146417] Create a suggestion for document link if same word linked
https://bugs.documentfoundation.org/show_bug.cgi?id=146417 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 146415] Allow Basic + "Extended" Dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=146415 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 95539] Option + arrow does not work properly when RTL is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=95539 --- Comment #14 from QA Administrators --- Dear Zeev Turchinsky, 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 73494] Font fallback issue with text of mixed directionality in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=73494 --- Comment #10 from QA Administrators --- Dear Khaled Hosny, 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 61963] UI: 'Group and Outline' impossible with active Filter
https://bugs.documentfoundation.org/show_bug.cgi?id=61963 --- Comment #11 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 57422] presenter console RTL support needs completion
https://bugs.documentfoundation.org/show_bug.cgi?id=57422 --- Comment #11 from QA Administrators --- Dear Lior Kaplan, 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 56412] RTL UI: Movement of embedded objects is opposite to the change direction
https://bugs.documentfoundation.org/show_bug.cgi?id=56412 --- Comment #15 from QA Administrators --- Dear Lior Kaplan, 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 54494] improve cursor traversal of combined characters
https://bugs.documentfoundation.org/show_bug.cgi?id=54494 --- Comment #8 from QA Administrators --- Dear Caolán McNamara, 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 45147] right-to-left words appear in the wrong order in the CSV import dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=45147 --- Comment #14 from QA Administrators --- Dear Lior Kaplan, 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 39935] Disabled Asian or CTL language value should default to "None"
https://bugs.documentfoundation.org/show_bug.cgi?id=39935 --- Comment #11 from QA Administrators --- Dear Christophe Strobbe, 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 32531] Incorrect cursor key movement between table cells of different directionality
https://bugs.documentfoundation.org/show_bug.cgi?id=32531 --- Comment #30 from QA Administrators --- Dear Eyal, 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 129892] error loading a huge spreadsheet in ods format (no error in xlsx format)
https://bugs.documentfoundation.org/show_bug.cgi?id=129892 --- Comment #3 from QA Administrators --- Dear johannes.geest, 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 121584] Ctrl+LShift, Ctrl+RShift not setting direction in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=121584 --- Comment #4 from QA Administrators --- Dear Eyal Rozenberg, 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 120615] Ctrl+LShift, Ctrl+RShift not setting direction in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=120615 --- Comment #8 from QA Administrators --- Dear Eyal Rozenberg, 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 120206] When switching keyboard layout, scrolling should not behave as though Scroll Lock was toggled
https://bugs.documentfoundation.org/show_bug.cgi?id=120206 --- Comment #12 from QA Administrators --- Dear Eyal Rozenberg, 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 116828] edit comments are done in place when there are frozen columns, making it invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=116828 --- Comment #6 from QA Administrators --- Dear pajaro, 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 146660] New: Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 Bug ID: 146660 Summary: Applying paragraph styles resets some direct formatting Product: LibreOffice Version: 7.2.4.1 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: Create a document with the following text: ``` Lorem ipsum dolor sit amet Lorem ipsum dolor Lorem ipsum dolor Lorem ipsum dolor sit amet ``` Select the word "ipsum" in the 1st line and press Ctrl+B to apply "Bold" direct formatting to it. Put the cursor in the very **beginning** of the 2nd line, press Shift+End, and then Ctrl+B to make the whole line bold. Put the cursor in the very **end** of the 3rd line, press Shift+Home, and then press Ctrl+B to make this one line bold as well. The 2nd and 3rd lines are now bold, and the word "ipsum" in the first line is also bold. Now select the whole text (for example, by pressing Ctrl+A) and apply some paragraph style to it (for example, Text Body Indent). You will see that the second line is now regular, not bold. (And I think this is wrong from the user's perspective.) The 3rd line and the word "ipsum" on the 1st line are still bold. (Correct, this is what the user would expect, since applying paragraph styles is expected to not clear direct formatting.) Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 --- Comment #2 from davidak --- Created attachment 177404 --> https://bugs.documentfoundation.org/attachment.cgi?id=177404=edit exported svg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 --- Comment #1 from davidak --- Created attachment 177403 --> https://bugs.documentfoundation.org/attachment.cgi?id=177403=edit original file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] New: Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 Bug ID: 146659 Summary: Found scriptable element "script" in the uploaded SVG file. Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bugs.documentfoundation.org+i...@davidak.de Description: When i try to upload an SVG file exported from LibreOffice Impress to Wikimedia Commons, i get the error: Found scriptable element "script" in the uploaded SVG file. The version is 7.1.7.2 which can't get selected from the list. Steps to Reproduce: 1. go to https://commons.wikimedia.org/wiki/Special:UploadWizard 2. upload file 3. get error Actual Results: error: Found scriptable element "script" in the uploaded SVG file. Expected Results: LibreOffice should be compatible with Wikipedia. Reproducible: Always User Profile Reset: No Additional Info: create compatible files -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/app/dndhelp.cxx | 18 +-
vcl/source/window/mouse.cxx | 14 +++---
2 files changed, 20 insertions(+), 12 deletions(-)
New commits:
commit 3a683edd9c77e20255357879fc70ce49c9217fa8
Author: Jan-Marek Glogowski
AuthorDate: Sat Jan 8 21:29:03 2022 +0100
Commit: Jan-Marek Glogowski
CommitDate: Sun Jan 9 00:46:03 2022 +0100
Catch exception if failing to set the drag source
... or the drop target.
This is the "don't trust the comment or lose a day debugging WASM
AKA don't switch of your brain" commit.
The comment was "createInstance can throw any exception", so - no
more createInstance, no more exception! Nope, you're WRONG! While
the uno::Reference<...>::set(..., UNO_QUERY) might itself not
throw an exception, something else from the CreateDragSource or
CreateDropTarget call could.
The symptom was a caught exception when loading the initial Writer
document in SynchronousDispatch::dispatch.
While at it, also apply the clean-ups suggested by Mike Kaganski
in a comment to the original patch after the merge.
Regression from commit 031576105c21b2e0c2585a1236092487d5d193e2
("VCL move platform code from mouse.cxx into plugins").
Change-Id: If80a90a9a6c070d912584f85b9fd10382b98e29c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128175
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/vcl/source/app/dndhelp.cxx b/vcl/source/app/dndhelp.cxx
index d4d6ea059f06..bf0e897dfc7f 100644
--- a/vcl/source/app/dndhelp.cxx
+++ b/vcl/source/app/dndhelp.cxx
@@ -143,25 +143,25 @@ void
vcl::unohelper::DragAndDropWrapper::dropActionChanged( const css::datatrans
}
css::uno::Reference
-vcl::OleDnDHelper(const css::uno::Reference& pDnD,
const sal_IntPtr pWin, DragOrDrop eDoD)
+vcl::OleDnDHelper(const css::uno::Reference& xDnD,
const sal_IntPtr pWin, DragOrDrop eDoD)
{
-if (pWin && pDnD)
+if (pWin && xDnD)
{
if (eDoD == vcl::DragOrDrop::Drag)
-pDnD->initialize({ uno::Any(),
uno::Any(static_cast(pWin)) });
+xDnD->initialize({ uno::Any(),
uno::Any(static_cast(pWin)) });
else
-pDnD->initialize({ uno::Any(static_cast(pWin)),
uno::Any() });
+xDnD->initialize({ uno::Any(static_cast(pWin)),
uno::Any() });
}
-return css::uno::Reference(pDnD);
+return xDnD;
}
css::uno::Reference
-vcl::X11DnDHelper(const css::uno::Reference& pDnD,
const sal_IntPtr pWin)
+vcl::X11DnDHelper(const css::uno::Reference& xDnD,
const sal_IntPtr pWin)
{
-if (pWin && pDnD)
-pDnD->initialize({ uno::Any(Application::GetDisplayConnection()),
+if (pWin && xDnD)
+xDnD->initialize({ uno::Any(Application::GetDisplayConnection()),
uno::Any(static_cast(pWin)) });
-return css::uno::Reference(pDnD);
+return xDnD;
}
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/vcl/source/window/mouse.cxx b/vcl/source/window/mouse.cxx
index a25e226ed9fb..02f6c8a484b1 100644
--- a/vcl/source/window/mouse.cxx
+++ b/vcl/source/window/mouse.cxx
@@ -732,9 +732,17 @@ Reference< css::datatransfer::dnd::XDragSource >
Window::GetDragSource()
if (mpWindowImpl->mpFrameData->mxDragSource.is())
return mpWindowImpl->mpFrameData->mxDragSource;
-SalInstance* pInst = ImplGetSVData()->mpDefInst;
-
mpWindowImpl->mpFrameData->mxDragSource.set(pInst->CreateDragSource(pEnvData),
UNO_QUERY);
-
mpWindowImpl->mpFrameData->mxDropTarget.set(pInst->CreateDropTarget(pEnvData),
UNO_QUERY);
+try
+{
+SalInstance* pInst = ImplGetSVData()->mpDefInst;
+
mpWindowImpl->mpFrameData->mxDragSource.set(pInst->CreateDragSource(pEnvData),
UNO_QUERY);
+
mpWindowImpl->mpFrameData->mxDropTarget.set(pInst->CreateDropTarget(pEnvData),
UNO_QUERY);
+}
+catch (const Exception&)
+{
+mpWindowImpl->mpFrameData->mxDropTarget.clear();
+mpWindowImpl->mpFrameData->mxDragSource.clear();
+}
return mpWindowImpl->mpFrameData->mxDragSource;
#else
return Reference< css::datatransfer::dnd::XDragSource > ();
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 9f55945b125f196226738d4c44e456dbcf511549 Author: Stanislav Horacek AuthorDate: Sun Jan 9 00:06:06 2022 +0100 Commit: Gerrit Code Review CommitDate: Sun Jan 9 00:06:06 2022 +0100 Update git submodules * Update helpcontent2 from branch 'master' to e181836ae842bdafb6c54bfca86e054540f53510 - fix names of TableControl properties showing headers Change-Id: I2ac8de7ea17ed7a24244a59cdb10b14803e76769 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/128144 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index a5cccb45ec8e..e181836ae842 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit a5cccb45ec8ea2e4e45a92668136d4cbe045f7f4 +Subproject commit e181836ae842bdafb6c54bfca86e054540f53510
[Libreoffice-commits] help.git: source/text
source/text/sbasic/shared/03/sf_dialogcontrol.xhp |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e181836ae842bdafb6c54bfca86e054540f53510
Author: Stanislav Horacek
AuthorDate: Sat Jan 8 18:19:50 2022 +0100
Commit: Adolfo Jayme Barrientos
CommitDate: Sun Jan 9 00:06:04 2022 +0100
fix names of TableControl properties showing headers
Change-Id: I2ac8de7ea17ed7a24244a59cdb10b14803e76769
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/128144
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
index 21ed4c301..57fabd184 100644
--- a/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
+++ b/source/text/sbasic/shared/03/sf_dialogcontrol.xhp
@@ -1184,7 +1184,7 @@
alignments: Defines the alignment in
each column as a string in which each character can be "L" (Left), "C"
(Center), "R" (Right) or " " (whitespace, default, meaning left for strings and
right for numeric values). If the length of the string is shorter than the
number of columns in the table, then the last character in the string is used
to define the alignment of the remaining columns.
- The following
example assumes that the dialog myDialog has a
TableControl named Grid1 with "Show
header row" and "Show column row" properties set to "Yes".
+ The following
example assumes that the dialog myDialog has a
TableControl named Grid1 with "Show row
header" and "Show column header" properties set to "Yes".
Dim
myDialog As Object, oTable As Object, tableData As Variant
myDialog = CreateScriptService("Dialog",
"GlobalScope", "Standard", "myDialog")
[Libreoffice-bugs] [Bug 146626] Calc crashes every time on font size operation, in a specific document
https://bugs.documentfoundation.org/show_bug.cgi?id=146626 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #5 from Aron Budea --- No crash with LO 7.2.5.2 / macOS Monterey. -- You are receiving this mail because: You are the assignee for the bug.
Question about cppuhelper/compbase and other compbase1/2/.../12
Hello, I noticed include/cppuhelper had files like: compbase1.hxx compbase2.hxx ... compbase12.hxx It seems the only diff is the number of parameters. But there's also compbase.hxx which can take any number of parameters. May we replace all the use of compabase.hxx by compbase.hxx or is there an interest to keep all of them? Regards, Julien
[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items
https://bugs.documentfoundation.org/show_bug.cgi?id=141869 --- Comment #10 from Eyal Rozenberg --- (In reply to Jean-Baptiste Faure from comment #9) > 3/ Select Text under Type : the list of numbered formula appears in > Selection panel Do you mean select the "Figure" item under "Type"? > 4/ Mose the mouse pointer over one of the values in Selection list : the > extended tooltip appears and it says "Insert reference to" instead of "Refer > using" when you are pointing to a chapter header in the Selection list, > Headings being selected in Type list. I don't get any tooltip when my mouse is on the selection list. Perhaps if you could clarify the previous step? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146658] Libreoffice calc breaks file links when copy Spreadsheet to another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=146658 fre...@wp.pl changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from fre...@wp.pl --- Although the path seemed absolute, the option was set to keep path relative. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146643] reload method applied to a subform with subforms fails to reload all when called from a macro
https://bugs.documentfoundation.org/show_bug.cgi?id=146643 Walter Werner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146658] New: Libreoffice calc breaks file links when copy Spreadsheet to another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=146658 Bug ID: 146658 Summary: Libreoffice calc breaks file links when copy Spreadsheet to another folder Product: LibreOffice Version: 7.2.4.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fre...@wp.pl Description: Libreoffice calc breaks file links when copy Spreadsheet to another folder When linking to other spreadsheets, LO Calc stores something that seem like absolute path to the file. After I copy the Spreadsheet to other folder, and open the spreadsheet in a different location, the link seem broken. Created a simple test case: x:\LibO_test\Somefolder\Datasource\datasource.ods is my linked data source x:\LibO_test\Somefolder\Somespreadsheet.ods is my work spreadsheet where I do a database lookup. The URL is 'file:///X:/LibO_test/Somefolder/Datasource/datasource.ods' Now when I copy the Somespreadsheet.ods to x:\LibO_test\Somespreadsheet.ods , and open it in new location (x:\LibO_test instead of x:\LibO_test\Somefolder) I get broken URL: 'file:///X:/LibO_test/Datasource/datasource.ods' (note the missing "/Somefolder" in the path) Steps to Reproduce: 1. Detailed in description 2. 3. Actual Results: Result in broken file URL Expected Results: Expect to not break absolute file URLs Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: pl-PL Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 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-commits] core.git: svx/source
svx/source/svdraw/svdtrans.cxx | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
New commits:
commit 4c4ce3dc2133199f0d804a686a1e0cd0c9124914
Author: Noel Grandin
AuthorDate: Sat Jan 8 19:06:14 2022 +0200
Commit: Noel Grandin
CommitDate: Sat Jan 8 20:45:19 2022 +0100
tdf#146556 feature 'drag-mirror' is broken
regression from
commit 11e52fe2979b0947814a49b9c17ec373795cbf8e
introduce Degree100 strong_int type
where I tried to introduce a more efficient NormAngle36000
calculation, but it produces the wrong answer.
Change-Id: Iefeb0849984bc59d3ce9191eaf6f064beba94c59
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128143
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/svx/source/svdraw/svdtrans.cxx b/svx/source/svdraw/svdtrans.cxx
index c0a8aa2605f7..2e3b91d47a57 100644
--- a/svx/source/svdraw/svdtrans.cxx
+++ b/svx/source/svdraw/svdtrans.cxx
@@ -405,13 +405,11 @@ Degree100 NormAngle18000(Degree100 a)
return a;
}
-Degree100 NormAngle36000(Degree100 deg100)
+Degree100 NormAngle36000(Degree100 a)
{
-// do an add because we want -90 to end up as 270
-int a = 36000 + deg100.get();
-a %= 36000;
-a = std::abs(a);
-return Degree100(a);
+while (a < 0_deg100) a += 36000_deg100;
+while (a >= 36000_deg100) a -= 36000_deg100;
+return a;
}
sal_uInt16 GetAngleSector(Degree100 nAngle)
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 --- Comment #6 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/4c4ce3dc2133199f0d804a686a1e0cd0c9124914 tdf#146556 feature 'drag-mirror' is broken It will be available in 7.4.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 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 Commit Notification changed: What|Removed |Added Whiteboard||target:7.4.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source
cui/source/options/optgdlg.cxx | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
New commits:
commit 31872a382342060d6e1ecd9168b2a8c7a57d4717
Author: Noel Grandin
AuthorDate: Sat Jan 8 14:20:52 2022 +0200
Commit: Noel Grandin
CommitDate: Sat Jan 8 20:44:57 2022 +0100
fix Options->LibreOffice->View->Visibility->Menu on Windows,
impossible to set to Hide, regression from
commit 131759a3db51140c21594308ed99c71aa7aba43a
Date: Sun Jul 25 16:21:39 2021 +0200
use officecfg for menu options
Change-Id: I5312be2963d15ab85c267ece073e52984b1a34de
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128137
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/cui/source/options/optgdlg.cxx b/cui/source/options/optgdlg.cxx
index 43b529a82718..e0b0bfdf8c5d 100644
--- a/cui/source/options/optgdlg.cxx
+++ b/cui/source/options/optgdlg.cxx
@@ -775,13 +775,8 @@ bool OfaViewTabPage::FillItemSet( SfxItemSet* )
if (m_xMenuIconsLB->get_value_changed_from_saved())
{
-TriState eMenuIcons = m_xMenuIconsLB->get_active() == 0 ?
-TRISTATE_INDET :
-static_cast(m_xMenuIconsLB->get_active() - 1);
-// Output cache of current setting as possibly modified by System
Theme for older version
-bool bMenuIcons =
Application::GetSettings().GetStyleSettings().GetUseImagesInMenus();
-
officecfg::Office::Common::View::Menu::IsSystemIconsInMenus::set(eMenuIcons ==
TRISTATE_INDET, xChanges);
-
officecfg::Office::Common::View::Menu::ShowIconsInMenues::set(bMenuIcons,
xChanges);
+
officecfg::Office::Common::View::Menu::IsSystemIconsInMenus::set(m_xMenuIconsLB->get_active()
== 0, xChanges);
+
officecfg::Office::Common::View::Menu::ShowIconsInMenues::set(m_xMenuIconsLB->get_active()
== 2, xChanges);
bModified = true;
bMenuOptModified = true;
bAppearanceChanged = true;
@@ -931,10 +926,9 @@ void OfaViewTabPage::Reset( const SfxItemSet* )
// WorkingSet
m_xFontShowCB->set_active(officecfg::Office::Common::Font::View::ShowFontBoxWYSIWYG::get());
-bool bMenuIcons =
officecfg::Office::Common::View::Menu::ShowIconsInMenues::get();
bool bSystemMenuIcons =
officecfg::Office::Common::View::Menu::IsSystemIconsInMenus::get();
-TriState eMenuIcons = bSystemMenuIcons ? TRISTATE_INDET :
static_cast(bMenuIcons);
-m_xMenuIconsLB->set_active(eMenuIcons == 2 ? 0 : eMenuIcons + 1);
+bool bMenuIcons =
officecfg::Office::Common::View::Menu::ShowIconsInMenues::get();
+m_xMenuIconsLB->set_active(bSystemMenuIcons ? 0 : (bMenuIcons ? 2 : 1));
m_xMenuIconsLB->save_value();
TriState eContextMenuShortcuts =
static_cast(officecfg::Office::Common::View::Menu::ShortcutsInContextMenus::get());
[Libreoffice-ux-advise] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 Dave Barton changed: What|Removed |Added CC||da...@libreoffice.org --- Comment #4 from Dave Barton --- The results of my checks with Windows 10 and the "official" LibreOffice Linux installations are exactly the same as reported by V Stuart Foote in comment 3. Are you running a distro provided edition? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 Dave Barton changed: What|Removed |Added CC||da...@libreoffice.org --- Comment #4 from Dave Barton --- The results of my checks with Windows 10 and the "official" LibreOffice Linux installations are exactly the same as reported by V Stuart Foote in comment 3. Are you running a distro provided edition? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145919] LO73b1: Graphics test UI not fully localizable
https://bugs.documentfoundation.org/show_bug.cgi?id=145919 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |kelem...@ubuntu.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145919] LO73b1: Graphics test UI not fully localizable
https://bugs.documentfoundation.org/show_bug.cgi?id=145919 --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 177402 --> https://bugs.documentfoundation.org/attachment.cgi?id=177402=edit How it looks after the proposed patch in qtz locale Proposed patch: https://gerrit.libreoffice.org/c/core/+/128087 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added Keywords|needsUXEval | Severity|enhancement |normal OS|All |Linux (All) --- Comment #3 from V Stuart Foote --- OK, my fault. I'm so used to reading between the lines for issue intake I was over thinking it. However, can not confirm on Version: 7.2.5.1 (x64) / LibreOffice Community Build ID: 6d497ff5e83a906a307eb25cce314d40c0b8624f CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded WFM with each opening of the Find & Replace dialog, current session or on new LO launch, will be where it had last been moved to. On Windows at least, its positioning is on the full desktop--the LO application frame position and sizing has no impact. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added Keywords|needsUXEval | Severity|enhancement |normal OS|All |Linux (All) --- Comment #3 from V Stuart Foote --- OK, my fault. I'm so used to reading between the lines for issue intake I was over thinking it. However, can not confirm on Version: 7.2.5.1 (x64) / LibreOffice Community Build ID: 6d497ff5e83a906a307eb25cce314d40c0b8624f CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded WFM with each opening of the Find & Replace dialog, current session or on new LO launch, will be where it had last been moved to. On Windows at least, its positioning is on the full desktop--the LO application frame position and sizing has no impact. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 146657] New: COUNTIF mismatches Text
https://bugs.documentfoundation.org/show_bug.cgi?id=146657 Bug ID: 146657 Summary: COUNTIF mismatches Text Product: LibreOffice Version: 7.1.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hailholyqu...@gmx.de Created attachment 177401 --> https://bugs.documentfoundation.org/attachment.cgi?id=177401=edit Screenshot from the bug within Calc. Dear developers, I found this bug in the German version of LibreOffice Calc, but I presume it will be the same in any other translation. Try this in Calc: Format A1 and A2 as text. Enter in A1: 5 Enter in A2: 5+ (i.e. necessary when entering school grades in Germany) Enter in A3: =ZÄHLENWENN(A1:A2;"5") means: =COUNTIF(...) The result will be: "2". The "+" in A2 is not being noticed by the program. When you open the file in MS Excel, the correct result "1" is displayed. Thank you for your great work, you are creating a fabulous program! Yours sincerely Overlord -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146656] Table styles should update themselves according to the template
https://bugs.documentfoundation.org/show_bug.cgi?id=146656 John changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146656] New: Table styles should update themselves according to the template
https://bugs.documentfoundation.org/show_bug.cgi?id=146656 Bug ID: 146656 Summary: Table styles should update themselves according to the template Product: LibreOffice Version: 7.2.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: If you create 3 tables, apply Academic table style to each of them, then add the background color to the 3rd table, and then update Academic style according to the 3rd table, the background color will be added to the 1st and 2nd tables as well. This is great. But table styles are somewhat broken if you try to use them in your custom templates. Here is what I mean: 1. Create a custom template and save it in the LO templates directory. The template should contain a table with modified Academic style (you should add yellow background to it). Close that template. 2. Then create a document based on it, and save it somewhere. The document should contain 3 tables that are formatted by using the modified, "yellow", Academic style. Close it. 3. Open your template and change the background color of Academic style to green. Close it. 4. Open your document from the step 2. Although you will see the "Update styles / Keep Old Styles" window, the template styles won't be updates. So the "academic" tables in your documents will stay yellow, not green. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-3' - download.lst external/libassuan
download.lst|4 ++-- external/libassuan/ExternalPackage_libassuan.mk |2 +- external/libassuan/w32-build-fixes.patch.1 |5 +++-- 3 files changed, 6 insertions(+), 5 deletions(-) New commits: commit 4f76a8329a8cc31fac1e4a9ee6f4658a6802b854 Author: Thorsten Behrens AuthorDate: Tue Dec 28 21:47:55 2021 +0100 Commit: Caolán McNamara CommitDate: Sat Jan 8 20:00:18 2022 +0100 Update libassuan to 2.5.5 Change-Id: Icd1034f4c6b43605f5d43fe28f7e0d191311daf0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127664 Tested-by: Jenkins Reviewed-by: Thorsten Behrens (cherry picked from commit 568a5bba2a30ab588b52677106bf209d4c0df758) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128084 Reviewed-by: Caolán McNamara diff --git a/download.lst b/download.lst index e7aed759c8ee..854cd3d1a238 100644 --- a/download.lst +++ b/download.lst @@ -146,8 +146,8 @@ export LANGUAGETOOL_SHA256SUM := 48c87e41636783bba438b65fd895821e369ed139e1465fa export LANGUAGETOOL_TARBALL := b63e6340a02ff1cacfeadb2c42286161-JLanguageTool-1.7.0.tar.bz2 export LCMS2_SHA256SUM := 18663985e864100455ac3e507625c438c3710354d85e5cbb7cd4043e11fe10f5 export LCMS2_TARBALL := lcms2-2.12.tar.gz -export LIBASSUAN_SHA256SUM := 91bcb0403866b4e7c4bc1cc52ed4c364a9b5414b3994f718c70303f7f765e702 -export LIBASSUAN_TARBALL := libassuan-2.5.3.tar.bz2 +export LIBASSUAN_SHA256SUM := 8e8c2fcc982f9ca67dcbb1d95e2dc746b1739a4668bc20b3a3c5be632edb34e4 +export LIBASSUAN_TARBALL := libassuan-2.5.5.tar.bz2 export LIBATOMIC_OPS_SHA256SUM := 1d6a279edf81767e74d2ad2c9fce09459bc65f12c6525a40b0cb3e53c089f665 export LIBATOMIC_OPS_TARBALL := libatomic_ops-7.6.8.tar.gz export LIBEOT_SHA256SUM := cf5091fa8e7dcdbe667335eb90a2cfdd0a3fe8f8c7c8d1ece44d9d055736a06a diff --git a/external/libassuan/ExternalPackage_libassuan.mk b/external/libassuan/ExternalPackage_libassuan.mk index 7a08028adbdd..0f24e5e2dec4 100644 --- a/external/libassuan/ExternalPackage_libassuan.mk +++ b/external/libassuan/ExternalPackage_libassuan.mk @@ -15,7 +15,7 @@ ifneq ($(DISABLE_DYNLOADING),TRUE) ifeq ($(OS),LINUX) -$(eval $(call gb_ExternalPackage_add_file,libassuan,$(LIBO_LIB_FOLDER)/libassuan.so.0,src/.libs/libassuan.so.0.8.3)) +$(eval $(call gb_ExternalPackage_add_file,libassuan,$(LIBO_LIB_FOLDER)/libassuan.so.0,src/.libs/libassuan.so.0.8.5)) else ifeq ($(OS),MACOSX) diff --git a/external/libassuan/w32-build-fixes.patch.1 b/external/libassuan/w32-build-fixes.patch.1 index cac6ea1045bc..ebf98c5f5093 100644 --- a/external/libassuan/w32-build-fixes.patch.1 +++ b/external/libassuan/w32-build-fixes.patch.1 @@ -33,13 +33,14 @@ diff -ru libassuan.orig/src/Makefile.am libassuan/src/Makefile.am `echo $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) | \ sed -e 's/-I/--include-dir /g;s/-D/--define /g'` -@@ -148,9 +148,9 @@ +@@ -148,10 +148,10 @@ $(DESTDIR)$(bindir)/gpgcedev.dll endif +mkheader$(EXEEXT): mkheader.c Makefile -mkheader: mkheader.c Makefile - $(CC_FOR_BUILD) -I. -I$(srcdir) -o $@ $(srcdir)/mkheader.c + $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(CPPFLAGS_FOR_BUILD) \ + $(LDFLAGS_FOR_BUILD) -I. -I$(srcdir) -o $@ $(srcdir)/mkheader.c +assuan.h: assuan.h.in mkheader$(EXEEXT) $(parts_of_assuan_h) + ./mkheader$(EXEEXT) $(host_os) $(srcdir)/assuan.h.in \
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #3 from PJF --- Created attachment 177400 --> https://bugs.documentfoundation.org/attachment.cgi?id=177400=edit Anchor alignment Is this correct? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125201] Scrolling down on Touchpad erratic (6.2.3.2 on Ubuntu 18.04)
https://bugs.documentfoundation.org/show_bug.cgi?id=125201 --- Comment #14 from nicolhill --- With regards to CSGO wagers, specialized help turns into a significant component in the foundation of each site. Some CSGO wagers administrations offer specialized help as a deferred ticket framework – this in itself isn't a disadvantage. Be that as it may, the best execution of a specialized emotionally supportive network is viewed as a web-based visit with a worker. It http://csgo-bets.org/csgo-spray-patterns/ is with the assistance of it that you can get exhortation as fast and effectively as conceivable in regards to any issue that has emerged connected with both the activity of the help and straightforwardly with your CSGO wagers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #2 from PJF --- Thank you so much for the feedback. Will do that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130431] Horrible drawinglayer dashed line performance
https://bugs.documentfoundation.org/show_bug.cgi?id=130431 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Resolution|--- |FIXED CC||79045_79...@mail.ru Status|NEW |RESOLVED --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- I do not see the problem in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1be170d0629cf761f0ee4173007a3c021966546e CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Let's close it as FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #1 from Leslie --- This is caused by the anchor property of the text box. The text box is be aligned to the anchor point ergo the bottom of the text box is aligned to the bottom of the anchor point (in this case it looks to be paragraph). Change the text box anchor property to page and then the align to bottom will work as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81430] libreoffice-mysql-connector cannot create/edit tables without primary key
https://bugs.documentfoundation.org/show_bug.cgi?id=81430 --- Comment #12 from Julien Nabet --- At last, I finally succeeded at making the fields of table not readonly (pk or not pk case) There's still some work (at least really implementing alterColumnByName) but I had already to add a lot of things. So I'd like first to split it in several patches but I must find the right way to avoid breaking something. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 --- Comment #2 from R. Green --- We seem to be at cross purposes. I'm referring only to the position of the F dialogue in relation to the program window, i.e. how far to the left or right or up or down it is. Currently it always appears in the same position on the screen. If you move it to the side (to prevent it obscuring the document and other informational features) and close the dialogue, on reopening it reappears in the default position. It would be useful if I could move it to the optimum position and keep it there no matter how many times I open and close it – at least for the duration of the session. (I have no complaints about the search behaviour, i.e. how terms appear in the FIND field etc.) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 --- Comment #2 from R. Green --- We seem to be at cross purposes. I'm referring only to the position of the F dialogue in relation to the program window, i.e. how far to the left or right or up or down it is. Currently it always appears in the same position on the screen. If you move it to the side (to prevent it obscuring the document and other informational features) and close the dialogue, on reopening it reappears in the default position. It would be useful if I could move it to the optimum position and keep it there no matter how many times I open and close it – at least for the duration of the session. (I have no complaints about the search behaviour, i.e. how terms appear in the FIND field etc.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142493] FILEOPEN DOCX: Settings of character position and size changes in character style "Footnote Anchor"
https://bugs.documentfoundation.org/show_bug.cgi?id=142493 --- Comment #12 from Antonio --- I did the tests as required. Endnote anchor. Before the test, file ott. 1) Superscript 2) Rise / lower by: 45% 3) relative font size: 70% After testing, file docx 4) Superscript 5) Rise / lower by: automatic relative font size: 58% Best regards. Antonio -- You are receiving this mail because: You are the assignee for the bug.
MacUpdate - your app listing has been updated
Title: Untitled Document App Listing Updated Hi The Document Foundation, We have updated your application listing for LibreOffice 7.2.5.2 on MacUpdate.com. Please take a moment to review your application's information to make sure that everything is correct. View your updated app listing You can login to your Developer Account to reply to comments and view stats, or submit new updates and changes to your app listing. Desktop Install Compatibility MacUpdate Desktop 6 is helping developers make it easier for users to fully install and use their apps. Download Desktop 6 and to ensure your app works with the “Install” link on our download pages. Advertise With MacUpdate The best Mac devs advertise their apps on MacUpdate.com because it’s the most targeted, highly performing Mac app advertising you can find on the web. Contact a...@macupdate.com to guarantee your annual ad campaigns get booked and expand your app’s audience. Learn more Questions? Contact our Content Update Team upda...@macupdate.com. You are receiving this offer because you have an app listed on MacUpdate.com. Add us to your address book or white list to ensure reliable delivery. © 2018 MacUpdate - All Rights Reserved 526 W. 14th St. #100 • Traverse City, MI 49684
Re: Open source
On 8.1.2022 13.32, Gunesh wrote: Hello Sir/Ma'am, I am a computer science student and i am new to open source and i liked your projects and want to contribute. I am well aware of C++ only. Hoping to hear from you soon. I have invited you to an interview. Ilmari
[Libreoffice-commits] core.git: toolkit/source
toolkit/source/awt/vclxmenu.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit e44b54a847672836253f56feab9d9ed2c11c0bc7
Author: Mike Kaganski
AuthorDate: Sat Jan 8 19:31:51 2022 +0300
Commit: Mike Kaganski
CommitDate: Sat Jan 8 18:52:16 2022 +0100
Fix build
Commit 326351e2b342eae5ca0154b2ba303b937a696577 crossed with
commit b37f9fbf05e16eb58eae40c6d900a4b9da2972db.
Change-Id: I1a10641aa0324e6af25698bb52d82157898c45d1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128142
Tested-by: Julien Nabet
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/toolkit/source/awt/vclxmenu.cxx b/toolkit/source/awt/vclxmenu.cxx
index 2e7e80636bf6..cbeb1ef7f810 100644
--- a/toolkit/source/awt/vclxmenu.cxx
+++ b/toolkit/source/awt/vclxmenu.cxx
@@ -822,7 +822,7 @@ VCLXMenu::getItemImage(
void VCLXMenu::setUserValue(sal_uInt16 nItemId, void* nUserValue,
MenuUserDataReleaseFunction aFunc)
{
SolarMutexGuard aSolarGuard;
-::osl::Guard< ::osl::Mutex > aGuard( GetMutex() );
+std::unique_lock aGuard(maMutex);
mpMenu->SetUserValue(nItemId, nUserValue, aFunc);
}
@@ -830,7 +830,7 @@ void VCLXMenu::setUserValue(sal_uInt16 nItemId, void*
nUserValue, MenuUserDataRe
void* VCLXMenu::getUserValue(sal_uInt16 nItemId)
{
SolarMutexGuard aSolarGuard;
-::osl::Guard< ::osl::Mutex > aGuard( GetMutex() );
+std::unique_lock aGuard(maMutex);
return mpMenu->GetUserValue(nItemId);
}
[Libreoffice-bugs] [Bug 146655] New: FORMATTING transfer format is applied to a wrong cell: below the cell, that was clicked
https://bugs.documentfoundation.org/show_bug.cgi?id=146655 Bug ID: 146655 Summary: FORMATTING transfer format is applied to a wrong cell: below the cell, that was clicked Product: LibreOffice Version: 7.2.3.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stef...@michalek.de I choose a colored cell, click at the broom (left mouse click), click (left mouse click) at another cell (empty or filled), and then the cell _below_ the targeted cell is formatted (like the original cell was, e.g. colored). Expected behaviour would be: The cell, that was clicked, should get the format. I tested many times: the mouse click is correct when choosing cells, not when transferring the format. A further detail: It seems to happen, that the correct cell is affected, if (by zooming the cells big enough or by fine adjusting) the _whole_ mouse pointer is within the boundaries of the cell. The latter is not the case during normal work and especially when choosing cells. Normally, only the head of the mouse pointer arrow is relevant. While applying format transfer, however, the end of the arrow seems to be relevant. I even manage to get the cell below-and-right formatted, when clicking near the lower right corner (whith the pointer head still left and above the corner). Thanks, Steffen Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+wayland) Locale: de-DE (de_DE.UTF-8); UI: de-DE Ubuntu package version: 1:7.2.3-0ubuntu0.21.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 --- Comment #5 from Noel Grandin --- fix here https://gerrit.libreoffice.org/c/core/+/128143 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146654] Imported tsv file saved as csv is saved as tsv.
https://bugs.documentfoundation.org/show_bug.cgi?id=146654 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from Mike Kaganski --- There's no "TSV" file type in LibreOffice. CSV is a common name for any plain-text structured data imported into Calc, where import and export filter may use different separator characters and other settings. When you imported the tab-separated file, the import filter has saved the settings used for its import, to keep on export. That is reasonable, since *most of the time* users open files, make edits, and save, expecting the file structure to be kept, just the data be changed according to the edits. The use case that you describe is different, and it needs the export filter settings to be changed. For that, Save As dialog, where you define the file type, has "Edit filter settings" checkbox, checking which will open the filter settings after you click Save. There you may define comma as separator, to override the values stored from import. https://help.libreoffice.org/latest/en-US/text/scalc/guide/csv_files.html?DbPAR=CALC Closing NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146643] reload method applied to a subform with subforms fails to reload all when called from a macro
https://bugs.documentfoundation.org/show_bug.cgi?id=146643 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #2 from Robert Großkopf --- Look at table "selector". Value for "SearchString" will be set to '0' the whole time. oAusgabeAuswahl.Commit will say to the form: "I have a new value." oAusgabe.updateRow will write the form to the existing row. Won't work on new rows, but will woirk for your example. oAusgabeAuswahl.Parent.updateRow() is just the same, only seen from the position of the listbox up to the form, which contains the listbox. If this will solve your problem please set this bug to RESOLVED and NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: drawinglayer/source
drawinglayer/source/primitive2d/markerarrayprimitive2d.cxx |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
New commits:
commit 4e5bbcdc3d1fc4dd94ec896480ab049f3a4926fa
Author: Ramreiso Kashung
AuthorDate: Sat Jan 8 08:47:31 2022 +0530
Commit: Mike Kaganski
CommitDate: Sat Jan 8 16:28:36 2022 +0100
Optimise a range-based for loop
This patch is an extension of
https://gerrit.libreoffice.org/c/core/+/127734 related to comment made by Mike
Kaganski
Change-Id: Ia7a6480dba2a0752a52ae4f9655c345af9f3ba64
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128134
Reviewed-by: Julien Nabet
Reviewed-by: Mike Kaganski
Tested-by: Jenkins
diff --git a/drawinglayer/source/primitive2d/markerarrayprimitive2d.cxx
b/drawinglayer/source/primitive2d/markerarrayprimitive2d.cxx
index eb5711307bea..cdaa15e53322 100644
--- a/drawinglayer/source/primitive2d/markerarrayprimitive2d.cxx
+++ b/drawinglayer/source/primitive2d/markerarrayprimitive2d.cxx
@@ -51,9 +51,8 @@ namespace drawinglayer::primitive2d
// use half size for expand
aLogicHalfSize *= 0.5;
-for(const auto& a : rPositions)
+for(const auto& rPosition : rPositions)
{
-const basegfx::B2DPoint& rPosition(a);
const basegfx::B2DRange aRange(rPosition - aLogicHalfSize,
rPosition + aLogicHalfSize);
basegfx::B2DHomMatrix aTransform;
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146648 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146648 [Bug 146648] Find and Replace doesn't restore last user position when opened -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval Blocks||102847 --- Comment #1 from V Stuart Foote --- Positioning sense of Find & Replace (and I'd assume the Find Bar) is to follow the edit cursor. You can prove that with subsequent launch of the dialog using either the 'Find Next' or 'Find Previous'. Meaning the edit cursor is "the last set user position" and the anchor for Find & Replace "position" within the current document. Believe even the 'Find All' or 'Replace All' is relative to the current edit cursor. Not clear any other behavior would make sense. Could you please restate your use case and STR, thanks. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval Blocks||102847 --- Comment #1 from V Stuart Foote --- Positioning sense of Find & Replace (and I'd assume the Find Bar) is to follow the edit cursor. You can prove that with subsequent launch of the dialog using either the 'Find Next' or 'Find Previous'. Meaning the edit cursor is "the last set user position" and the anchor for Find & Replace "position" within the current document. Believe even the 'Find All' or 'Replace All' is relative to the current edit cursor. Not clear any other behavior would make sense. Could you please restate your use case and STR, thanks. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 145114] TEMPLATES: Improve confirmation dialog "Update styles / Keep Old Styles" dialog + If the template has been detached, it is still specified in "File > Properties > Gener
https://bugs.documentfoundation.org/show_bug.cgi?id=145114 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||easyHack, skillCpp, skillUI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146535] Mouse line goes missing when changing paragraph stile
https://bugs.documentfoundation.org/show_bug.cgi?id=146535 --- Comment #1 from ceki...@gmx.net --- can confirm this behaviour, here on KDE Neon (user profile reset) - additional information: mouse reappears after clicking with the right mouse button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108747] [META] File properties/settings (meta data) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108747 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||145047 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145047 [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103314] [META] Templates bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103314 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||145047 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145047 [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||103314, 108747 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103314 [Bug 103314] [META] Templates bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108747 [Bug 108747] [META] File properties/settings (meta data) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 sdc.bla...@youmail.dk changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #6 from sdc.bla...@youmail.dk --- Reproduced effect using STR in comment 3, plus additional steps 8. Open saved template and enable "Apply user data" (in File > Properties) 9. Save template 10. Open test file created in step 5 Result: Get expected warning about changed template. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: e63fe68fb1d0915b64fdf63f7fa6eed866fa3a0d CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146647] [UI] Reword for Match in the Find and Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=146647 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- The 'Match case' is a specific search filter-the entire line of check boxes is already labled/identified as applicable for the 'Find:' Don't believe we gain anything by adjusting the labels, and keep in mind the translation l10n requirement of the UI. -1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146647 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146647 [Bug 146647] [UI] Reword for Match in the Find and Replace dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146647] [UI] Reword for Match in the Find and Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=146647 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- The 'Match case' is a specific search filter-the entire line of check boxes is already labled/identified as applicable for the 'Find:' Don't believe we gain anything by adjusting the labels, and keep in mind the translation l10n requirement of the UI. -1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-3' - config_host/config_gpgme.h.in configure.ac download.lst external/gpgmepp xmlsecurity/source
config_host/config_gpgme.h.in |
3
configure.ac|
3
download.lst|
4
external/gpgmepp/ExternalPackage_gpgmepp.mk |
4
external/gpgmepp/UnpackedTarball_gpgmepp.mk |
2
external/gpgmepp/add-minimal-keyexport.patch|
68 --
external/gpgmepp/find-libgpg-error-libassuan.patch |
29
external/gpgmepp/gpgme.git-fe2892618c20cd40c342cce26ffb6ac4644fd3c3.patch.1 |
30
external/gpgmepp/w32-build-fixes.patch.1|
9 +
external/gpgmepp/w32-fix-win32-macro.patch.1|
3
xmlsecurity/source/gpg/CertificateImpl.cxx |
7 -
11 files changed, 17 insertions(+), 145 deletions(-)
New commits:
commit e0721a655ca69d699024fd91da7071da0485b218
Author: Thorsten Behrens
AuthorDate: Tue Dec 28 22:15:51 2021 +0100
Commit: Caolán McNamara
CommitDate: Sat Jan 8 15:52:25 2022 +0100
Update gpgme to 1.16.0
* remove GPGME_CAN_EXPORT_MINIMAL_KEY, upstream now has support for
key export flags in c++ wrapper (gpgmepp >= 1.14)
* therefore, external/gpgmepp/add-minimal-keyexport.patch now fully
obsolete, tweaked xmlsecurity code to use upstream function
* bits of external/gpgmepp/find-libgpg-error-libassuan.patch are
upstream now (configure and makefile pieces, though we keep
configure.ac changes for the while - to not pick up system versions
too easily)
*
external/gpgmepp/gpgme.git-fe2892618c20cd40c342cce26ffb6ac4644fd3c3.patch.1
was from upstream anyway, removed
Change-Id: I991c20c0eeff0f9135e97c991afcb905be55a959
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127665
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
(cherry picked from commit 78dae8b20b85686d1a642415195d2e10fbb2dc1f)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128085
Reviewed-by: Caolán McNamara
diff --git a/config_host/config_gpgme.h.in b/config_host/config_gpgme.h.in
index 3c483d08f564..ead3ca7bc2b9 100644
--- a/config_host/config_gpgme.h.in
+++ b/config_host/config_gpgme.h.in
@@ -26,9 +26,6 @@
# include "config_lgpl.h"
#endif
-// Defined if gpgme supports exporting minimal key.
-#define GPGME_CAN_EXPORT_MINIMAL_KEY 0
-
#undef GPGME_GPGCONF
#endif
diff --git a/configure.ac b/configure.ac
index aca958768d0a..ce82177fa691 100644
--- a/configure.ac
+++ b/configure.ac
@@ -12443,7 +12443,7 @@ elif test "$_os" = "Linux" -o "$_os" = "Darwin" -o
"$_os" = "WINNT" ; then
# C++ library doesn't come with fancy gpgmepp-config, check for
headers the old-fashioned way
AC_CHECK_HEADER(gpgme++/gpgmepp_version.h, [
GPGMEPP_CFLAGS=-I/usr/include/gpgme++ ],
-[AC_MSG_ERROR([gpgmepp headers not found, install gpgmepp
development package])], [])
+[AC_MSG_ERROR([gpgmepp headers not found, install gpgmepp >= 1.14
development package])], [])
# progress_callback is the only func with plain C linkage
# checking for it also filters out older, KDE-dependent libgpgmepp
versions
AC_CHECK_LIB(gpgmepp, progress_callback, [ GPGMEPP_LIBS=-lgpgmepp ],
@@ -12453,7 +12453,6 @@ elif test "$_os" = "Linux" -o "$_os" = "Darwin" -o
"$_os" = "WINNT" ; then
else
AC_MSG_RESULT([internal])
BUILD_TYPE="$BUILD_TYPE LIBGPGERROR LIBASSUAN GPGMEPP"
-AC_DEFINE([GPGME_CAN_EXPORT_MINIMAL_KEY])
GPG_ERROR_CFLAGS="-I${WORKDIR}/UnpackedTarball/libgpg-error/src"
LIBASSUAN_CFLAGS="-I${WORKDIR}/UnpackedTarball/libassuan/src"
diff --git a/download.lst b/download.lst
index d7e47f661dda..e7aed759c8ee 100644
--- a/download.lst
+++ b/download.lst
@@ -100,8 +100,8 @@ export FREETYPE_SHA256SUM :=
8bee39bd3968c4804b70614a0a3ad597299ad0e824bc8aad5ce
export FREETYPE_TARBALL := freetype-2.11.0.tar.xz
export GLM_SHA256SUM :=
6bba5f032bed47c73ad9397f2313b9acbfb56253d0d0576b5873d3dcb25e99ad
export GLM_TARBALL := glm-0.9.9.8.zip
-export GPGME_SHA256SUM :=
c4e30b227682374c23cddc7fdb9324a99694d907e79242a25a4deeedb393be46
-export GPGME_TARBALL := gpgme-1.13.1.tar.bz2
+export GPGME_SHA256SUM :=
6c8cc4aedb10d5d4c905894ba1d850544619ee765606ac43df7405865de29ed0
+export GPGME_TARBALL := gpgme-1.16.0.tar.bz2
export GRAPHITE_SHA256SUM :=
b8e892d8627c41888ff121e921455b9e2d26836978f2359173d19825da62b8fc
export GRAPHITE_TARBALL := graphite2-minimal-1.3.14.tgz
export HARFBUZZ_SHA256SUM :=
d58461395ce28b9dc03903254374dd70c38c8c28c5046db123c08f7ab9417be7
diff --git a/external/gpgmepp/ExternalPackage_gpgmepp.mk
b/external/gpgmepp/ExternalPackage_gpgmepp.mk
index 6bab3e5e293f..a2b207597cdd 100644
--- a/external/gpgmepp/ExternalPackage_gpgmepp.mk
+++
[Libreoffice-commits] core.git: Branch 'libreoffice-7-3' - download.lst external/libgpg-error
download.lst |4 -
external/libgpg-error/ExternalPackage_libgpg-error.mk |2
external/libgpg-error/w32-build-fixes-5.patch | 64 +-
3 files changed, 35 insertions(+), 35 deletions(-)
New commits:
commit fdfd132dc2f596472f0dfd99f7acd2a3d6509527
Author: Thorsten Behrens
AuthorDate: Tue Dec 28 21:45:45 2021 +0100
Commit: Caolán McNamara
CommitDate: Sat Jan 8 15:51:44 2022 +0100
Update libgpg-error to 1.43
Change-Id: Iecd4a131f9c5b43bb03c5f9c4b6c7efe36e443aa
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127663
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
(cherry picked from commit 7d50d74d0a10b4811b82f66dc5ac5a696c2974c7)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128083
Reviewed-by: Caolán McNamara
diff --git a/download.lst b/download.lst
index 9c1a2b216b01..d7e47f661dda 100644
--- a/download.lst
+++ b/download.lst
@@ -156,8 +156,8 @@ export LIBEXTTEXTCAT_SHA256SUM :=
6d77eace20e9ea106c1330e268ede70c9a4a89744ddc25
export LIBEXTTEXTCAT_TARBALL := libexttextcat-3.4.6.tar.xz
export LIBFFI_SHA256SUM :=
72fba7922703ddfa7a028d513ac15a85c8d54c8d67f55fa5a4802885dc652056
export LIBFFI_TARBALL := libffi-3.3.tar.gz
-export LIBGPGERROR_SHA256SUM :=
b32d6ff72a73cf79797f7f2d039e95e9c6f92f0c1450215410840ab62aea9763
-export LIBGPGERROR_TARBALL := libgpg-error-1.37.tar.bz2
+export LIBGPGERROR_SHA256SUM :=
a9ab83ca7acc442a5bd846a75b920285ff79bdb4e3d34aa382be88ed2c3aebaf
+export LIBGPGERROR_TARBALL := libgpg-error-1.43.tar.bz2
export LIBLANGTAG_SHA256SUM :=
1f12a20a02ec3a8d22e54dedb8b683a43c9c160bda1ba337bf1060607ae733bd
export LIBLANGTAG_TARBALL := liblangtag-0.6.3.tar.bz2
export LIBNUMBERTEXT_SHA256SUM :=
db9060d208501bd7bc06300a55d8489d29dd560ee0fbbd0f41b78af56816680c
diff --git a/external/libgpg-error/ExternalPackage_libgpg-error.mk
b/external/libgpg-error/ExternalPackage_libgpg-error.mk
index 1d9c016e09df..7ee849d2369c 100644
--- a/external/libgpg-error/ExternalPackage_libgpg-error.mk
+++ b/external/libgpg-error/ExternalPackage_libgpg-error.mk
@@ -15,7 +15,7 @@ ifneq ($(DISABLE_DYNLOADING),TRUE)
ifeq ($(OS),LINUX)
-$(eval $(call
gb_ExternalPackage_add_file,libgpg-error,$(LIBO_LIB_FOLDER)/libgpg-error-lo.so.0,src/.libs/libgpg-error-lo.so.0.28.0))
+$(eval $(call
gb_ExternalPackage_add_file,libgpg-error,$(LIBO_LIB_FOLDER)/libgpg-error-lo.so.0,src/.libs/libgpg-error-lo.so.0.32.1))
else ifeq ($(OS),MACOSX)
diff --git a/external/libgpg-error/w32-build-fixes-5.patch
b/external/libgpg-error/w32-build-fixes-5.patch
index 2633df9ee6c9..8a65cedea2da 100644
--- a/external/libgpg-error/w32-build-fixes-5.patch
+++ b/external/libgpg-error/w32-build-fixes-5.patch
@@ -1,3 +1,19 @@
+--- src/argparse.c 2021-11-03 13:44:56.0 +0100
src/argparse.c~2022-01-03 17:05:23.418077200 +0100
+@@ -33,8 +33,12 @@
+ #include
+ #include
+ #include
+-#include
+ #include
++#ifdef _WIN32
++# define R_OK 04
++# define strncasecmp _strnicmp
++# define strcasecmp _stricmp
++#endif
+
+ #include "gpgrt-int.h"
+
--- src/gpg-error.c2020-06-06 00:18:40.199791000 +0200
+++ src/gpg-error.c~ 2020-06-05 18:44:14.223182300 +0200
@@ -61,6 +61,11 @@
@@ -12,6 +28,19 @@
static void
i18n_init (void)
{
+
+--- src/spawn-w32.c~ 2022-01-03 16:33:24.0 +0100
src/spawn-w32.c 2022-01-03 16:46:57.173841200 +0100
+@@ -56,7 +56,7 @@
+ * Previous versions interpreted X_OK as F_OK anyway, so we'll just
+ * use F_OK directly. */
+ #undef X_OK
++#define X_OK 0
+-#define X_OK F_OK
+
+ /* For HANDLE and the internal file descriptor (fd) of this module:
+ * HANDLE can be represented by an intptr_t which should be true for
+
--- src/logging.c 2020-06-05 18:58:59.254413200 +0200
+++ src/logging.c~ 2019-12-12 15:23:37.0 +0100
@@ -44,7 +44,11 @@
@@ -65,20 +94,6 @@
gpg_error_SOURCES = strsource-sym.c strerror-sym.c gpg-error.c
gpg_error_CPPFLAGS = -DPKGDATADIR=\"$(pkgdatadir)\" \
-DLOCALEDIR=\"$(localedir)\" $(extra_cppflags)
src/spawn-w32.c2020-06-05 18:47:05.807099200 +0200
-+++ src/spawn-w32.c~ 2020-06-05 18:44:14.114035900 +0200
-@@ -834,7 +834,11 @@
- /* We don't use ENVP. */
- (void)envp;
-
-+#ifdef _WIN32
-+ if (_access (pgmname, 04))
-+#else
- if (access (pgmname, X_OK))
-+#endif
- return _gpg_err_code_from_syserror ();
-
- /* Prepare security attributes. */
--- src/sysutils.c 2020-06-06 00:23:52.457265500 +0200
+++ src/sysutils.c~2019-12-12 15:23:37.0 +0100
@@ -22,7 +22,11 @@
@@ -94,21 +109,6 @@
#include
#ifdef HAVE_W32_SYSTEM
# include
-@@ -274,11 +270,12 @@
- gpg_err_code_t
- _gpgrt_mkdir (const char *name, const char *modestr)
- {
-+#ifdef _WIN32
--#ifdef HAVE_W32CE_SYSTEM
- wchar_t *wname;
- (void)modestr;
-
-+ size_t size;
-+ wname = utf8_to_wchar (name, -1, );
-- wname = utf8_to_wchar (name);
- if (!wname)
- return
[Libreoffice-bugs] [Bug 145932] Lists: The formatting of the last word affect formatting of the number
https://bugs.documentfoundation.org/show_bug.cgi?id=145932 --- Comment #5 from John --- The workaround (for both "flavors" of this bug) is to finish a problematic list item with a space, and don't apply to this space any formatting. That is, if the text to left of this space is bold, the space should be regular, not bold; and if the text to the left side of the space is red, the space should be black, assuming that black is your primary text color. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77419] Cannot align text to bottom of cell in row of table split over pages
https://bugs.documentfoundation.org/show_bug.cgi?id=77419 --- Comment #13 from R. Green --- Created attachment 177399 --> https://bugs.documentfoundation.org/attachment.cgi?id=177399=edit Writer file showing problem with bottom alignment in tables spanning pages Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded This issue has still not been resolved after over 6 years! Open the attached writer file. Place the cursor in the blank cell and press "Align Bottom" (Table toolbar at botom of window). EXPECTED RESULT: Cursor should move to the bottom of the cell on the next page. ACTUAL RESULT: Cursor only moves to the bottom of the first page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146651 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146651 [Bug 146651] FIND AND REPLACE: difficult to recognize certain search/replace terms, enlarge the UI font (optionally) for clarity -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 146651] FIND AND REPLACE: difficult to recognize certain search/replace terms, enlarge the UI font (optionally) for clarity
https://bugs.documentfoundation.org/show_bug.cgi?id=146651 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Summary|FIND AND REPLACE: difficult |FIND AND REPLACE: difficult |to recognize certain|to recognize certain |search/replace terms|search/replace terms, ||enlarge the UI font ||(optionally) for clarity Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- +1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 146651] FIND AND REPLACE: difficult to recognize certain search/replace terms, enlarge the UI font (optionally) for clarity
https://bugs.documentfoundation.org/show_bug.cgi?id=146651 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Summary|FIND AND REPLACE: difficult |FIND AND REPLACE: difficult |to recognize certain|to recognize certain |search/replace terms|search/replace terms, ||enlarge the UI font ||(optionally) for clarity Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- +1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145932] Lists: The formatting of the last word affect formatting of the number
https://bugs.documentfoundation.org/show_bug.cgi?id=145932 --- Comment #4 from John --- I remember that I have had the same issue last week, but I cannot reproduce it right now. However, I can reproduce something very similar, and I'm sure that this is actually the same bug, just different "flavors": 1. Crete a new document based on the default Writer template. 2. Open the Styles pane (View > Styles) 3. Apply the "Numbering 123" to the first line and then type "This is foo". 4. Repeat the previous step for "This is bar" and "This is baz". So now you have the following list: ``` 1. This is foo 2. This is bar 3. This is baz ``` Put the cursor to the left side of the uppercase letter T in the "bar" line and then press Shift+End to select to its end. Then press Ctrl+B to make this selection bold. You will see that the number "2" is now also bold, even though it is outside the selection. I think this is wrong and "2" should stay "regular", not "bold". Version: 7.2.4.1 (x86) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; 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 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 --- Comment #5 from Dieter --- (In reply to John from comment #3) > I can reproduce it with 7.2.4.1 => status NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88121] EDITING: When "Apply user data" unchecked, "Total editing time" And "Revision number" go blank
https://bugs.documentfoundation.org/show_bug.cgi?id=88121 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5047 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=88 ||121 Status|NEEDINFO|NEW --- Comment #4 from Dieter --- (In reply to John from comment #3) > I can reproduce it with 7.2.4.1 => status NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cpputools/Module_cpputools.mk cpputools/Package_uno_sh.mk cpputools/scripts Repository.mk ure/Module_ure.mk ure/Package_install.mk ure/Package_ure_install.mk ure/source
Repository.mk |1 +
cpputools/Module_cpputools.mk |5 -
cpputools/Package_uno_sh.mk | 16
ure/Module_ure.mk |2 +-
ure/Package_ure_install.mk|4
5 files changed, 22 insertions(+), 6 deletions(-)
New commits:
commit c906ac8e8a06dc5df980e56d7d6776dfcb08aa2a
Author: Jan-Marek Glogowski
AuthorDate: Sat Jan 8 13:29:00 2022 +0100
Commit: Jan-Marek Glogowski
CommitDate: Sat Jan 8 15:33:30 2022 +0100
Don't install the uno script when uno is not build
... move it into cpputools and rename ure/Package_install.mk to
ure/Package_ure_install.mk, to match the module name.
Follow up from commit 92a90cf5ccb998d2fcc77a62bb971534e410cdec
("Don't build the static uno binary"). I missed that hunk in a
larger patch, because the script was in a different module, then
the binary.
Change-Id: If7f3152be9567cf84be176d3fedefbcd5ad8d387
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128138
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski
diff --git a/Repository.mk b/Repository.mk
index c6210625338a..23dbc470dbcc 100644
--- a/Repository.mk
+++ b/Repository.mk
@@ -849,6 +849,7 @@ $(eval $(call
gb_Helper_register_packages_for_install,libreofficekit,\
$(eval $(call gb_Helper_register_packages_for_install,ure,\
instsetoo_native_setup_ure \
+$(call gb_CondExeUno,uno_sh) \
ure_install \
$(if $(ENABLE_JAVA),\
jvmfwk_jvmfwk3_ini \
diff --git a/cpputools/Module_cpputools.mk b/cpputools/Module_cpputools.mk
index 9e41264daee4..c71b68e446d7 100644
--- a/cpputools/Module_cpputools.mk
+++ b/cpputools/Module_cpputools.mk
@@ -11,7 +11,10 @@ $(eval $(call gb_Module_Module,cpputools))
$(eval $(call gb_Module_add_targets,cpputools,\
$(call gb_CondExeSp2bv,Executable_sp2bv) \
-$(call gb_CondExeUno,Executable_uno) \
+$(call gb_CondExeUno, \
+Executable_uno \
+Package_uno_sh \
+) \
))
# vim:set noet sw=4 ts=4:
diff --git a/cpputools/Package_uno_sh.mk b/cpputools/Package_uno_sh.mk
new file mode 100644
index ..4df4d75f5c09
--- /dev/null
+++ b/cpputools/Package_uno_sh.mk
@@ -0,0 +1,16 @@
+# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*-
+#
+# This file is part of the LibreOffice project.
+#
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+#
+
+$(eval $(call gb_Package_Package,uno_sh,$(SRCDIR)/cpputools/scripts))
+
+ifneq (,$(filter-out MACOSX WNT,$(OS)))
+$(eval $(call gb_Package_add_file,uno_sh,$(LIBO_URE_BIN_FOLDER)/uno,uno.sh))
+endif
+
+# vim:set noet sw=4 ts=4:
diff --git a/ure/source/uno b/cpputools/scripts/uno.sh
similarity index 100%
rename from ure/source/uno
rename to cpputools/scripts/uno.sh
diff --git a/ure/Module_ure.mk b/ure/Module_ure.mk
index 88cbc71b31f2..d7f436883c44 100644
--- a/ure/Module_ure.mk
+++ b/ure/Module_ure.mk
@@ -10,7 +10,7 @@
$(eval $(call gb_Module_Module,ure))
$(eval $(call gb_Module_add_targets,ure,\
- Package_install \
+ Package_ure_install \
Rdb_ure \
))
diff --git a/ure/Package_install.mk b/ure/Package_ure_install.mk
similarity index 81%
rename from ure/Package_install.mk
rename to ure/Package_ure_install.mk
index e8b6515fdf10..e73c3c3618d6 100644
--- a/ure/Package_install.mk
+++ b/ure/Package_ure_install.mk
@@ -9,10 +9,6 @@
$(eval $(call gb_Package_Package,ure_install,$(SRCDIR)/ure/source))
-ifneq (,$(filter-out MACOSX WNT,$(OS)))
-$(eval $(call gb_Package_add_file,ure_install,$(LIBO_URE_BIN_FOLDER)/uno,uno))
-endif
-
ifeq (MACOSX,$(OS))
ifneq ($(ENABLE_MACOSX_SANDBOX),TRUE)
$(eval $(call
gb_Package_add_symbolic_link,ure_install,MacOS/urelibs,../Frameworks))
[Libreoffice-bugs] [Bug 107484] Non-english font names claim to be substituted in font name toolbar control
https://bugs.documentfoundation.org/show_bug.cgi?id=107484 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=61 ||134 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61134] Font substitute name should appear in the font name combobox and in its tooltip
https://bugs.documentfoundation.org/show_bug.cgi?id=61134 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||7484 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: framework/source include/toolkit toolkit/source
framework/source/uielement/newmenucontroller.cxx |7 +++
framework/source/uielement/popuptoolbarcontroller.cxx |8
include/toolkit/awt/vclxmenu.hxx |5 +++--
toolkit/source/awt/vclxmenu.cxx | 16
4 files changed, 26 insertions(+), 10 deletions(-)
New commits:
commit 326351e2b342eae5ca0154b2ba303b937a696577
Author: Caolán McNamara
AuthorDate: Tue Dec 14 10:22:00 2021 +
Commit: Caolán McNamara
CommitDate: Sat Jan 8 15:32:56 2022 +0100
move UserData bodge into VCLXMenu
Change-Id: I20c303788e576a29574a696cb20c9e8a235233b1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126804
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/framework/source/uielement/newmenucontroller.cxx
b/framework/source/uielement/newmenucontroller.cxx
index 9b70d5821682..d282509d93f5 100644
--- a/framework/source/uielement/newmenucontroller.cxx
+++ b/framework/source/uielement/newmenucontroller.cxx
@@ -346,7 +346,7 @@ void NewMenuController::fillPopupMenu( Reference<
css::awt::XPopupMenu > const &
rPopupMenu->setCommand(nItemId, aDynamicMenuEntry.sURL);
void* nAttributePtr = MenuAttributes::CreateAttribute(
aDynamicMenuEntry.sTargetName, aDynamicMenuEntry.sImageIdentifier );
-pVCLPopupMenu->SetUserValue( nItemId, nAttributePtr,
MenuAttributes::ReleaseAttribute );
+pPopupMenu->setUserValue(nItemId, nAttributePtr,
MenuAttributes::ReleaseAttribute);
nItemId++;
}
@@ -400,9 +400,8 @@ void SAL_CALL NewMenuController::itemSelected( const
css::awt::MenuEvent& rEvent
{
SolarMutexGuard aSolarMutexGuard;
-PopupMenu* pVCLPopupMenu = static_cast(pPopupMenu->GetMenu());
-aURL = pVCLPopupMenu->GetItemCommand(rEvent.MenuId);
-void* nAttributePtr = pVCLPopupMenu->GetUserValue(rEvent.MenuId);
+aURL = pPopupMenu->getCommand(rEvent.MenuId);
+void* nAttributePtr = pPopupMenu->getUserValue(rEvent.MenuId);
MenuAttributes* pAttributes = static_cast(nAttributePtr);
if (pAttributes)
aTargetFrame = pAttributes->aTargetFrame;
diff --git a/framework/source/uielement/popuptoolbarcontroller.cxx
b/framework/source/uielement/popuptoolbarcontroller.cxx
index 0e1811f8bcd7..62ac260f6c77 100644
--- a/framework/source/uielement/popuptoolbarcontroller.cxx
+++ b/framework/source/uielement/popuptoolbarcontroller.cxx
@@ -696,8 +696,8 @@ void SAL_CALL NewToolbarController::execute( sal_Int16
/*KeyModifier*/ )
aURL = m_xPopupMenu->getCommand(m_nMenuId);
// TODO investigate how to wrap Get/SetUserValue in css::awt::XMenu
-Menu* pVclMenu = comphelper::getFromUnoTunnel( m_xPopupMenu
)->GetMenu();
-MenuAttributes* pMenuAttributes( static_cast(
pVclMenu->GetUserValue( m_nMenuId ) ) );
+VCLXMenu* pMenu = comphelper::getFromUnoTunnel(m_xPopupMenu);
+MenuAttributes*
pMenuAttributes(static_cast(pMenu->getUserValue(m_nMenuId)));
if ( pMenuAttributes )
aTarget = pMenuAttributes->aTargetFrame;
else
@@ -749,8 +749,8 @@ void SAL_CALL NewToolbarController::updateImage()
if ( m_xPopupMenu.is() && m_nMenuId )
{
aURL = m_xPopupMenu->getCommand(m_nMenuId);
-Menu* pVclMenu = comphelper::getFromUnoTunnel( m_xPopupMenu
)->GetMenu();
-MenuAttributes* pMenuAttributes( static_cast(
pVclMenu->GetUserValue( m_nMenuId ) ) );
+VCLXMenu* pMenu = comphelper::getFromUnoTunnel(m_xPopupMenu);
+MenuAttributes*
pMenuAttributes(static_cast(pMenu->getUserValue(m_nMenuId)));
if ( pMenuAttributes )
aImageId = pMenuAttributes->aImageId;
}
diff --git a/include/toolkit/awt/vclxmenu.hxx b/include/toolkit/awt/vclxmenu.hxx
index 5c848975d837..096c370bce82 100644
--- a/include/toolkit/awt/vclxmenu.hxx
+++ b/include/toolkit/awt/vclxmenu.hxx
@@ -48,8 +48,7 @@ typedef ::std::vector<
css::uno::Reference< css::awt::XPopupMenu >
> PopupMenuRefList;
-
-
+typedef void (*MenuUserDataReleaseFunction)(void*);
class TOOLKIT_DLLPUBLIC VCLXMenu : public css::awt::XMenuBar,
public css::awt::XPopupMenu,
@@ -80,6 +79,8 @@ public:
Menu*GetMenu() const { return mpMenu; }
bool IsPopupMenu() const;
+void setUserValue(sal_uInt16 nItemId, void* nUserValue,
MenuUserDataReleaseFunction aFunc);
+void* getUserValue(sal_uInt16 nItemId);
// css::uno::XInterface
css::uno::Any SAL_CALL queryInterface( const css::uno::Type & rType )
override;
diff --git a/toolkit/source/awt/vclxmenu.cxx b/toolkit/source/awt/vclxmenu.cxx
index eca9de23fa12..2e7e80636bf6 100644
--- a/toolkit/source/awt/vclxmenu.cxx
+++ b/toolkit/source/awt/vclxmenu.cxx
@@ -819,6 +819,22 @@ VCLXMenu::getItemImage(
return rxGraphic;
}
+void VCLXMenu::setUserValue(sal_uInt16 nItemId, void* nUserValue,
