[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - svtools/source
svtools/source/control/tabbar.cxx | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
New commits:
commit f02c2912e50df357125c93eaaadfc96f02a05db0
Author: Caolán McNamara
AuthorDate: Mon Feb 20 15:54:22 2023 +
Commit: Adolfo Jayme Barrientos
CommitDate: Tue Feb 21 07:49:35 2023 +
Resolves: tdf#153763 first/last buttons in tabbar not responding
Change-Id: Id6e70eca7c2d523643d9e38e8c7402879464bf5a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147291
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/svtools/source/control/tabbar.cxx
b/svtools/source/control/tabbar.cxx
index 3e4e2d94cedb..a9579dfb94f8 100644
--- a/svtools/source/control/tabbar.cxx
+++ b/svtools/source/control/tabbar.cxx
@@ -881,13 +881,16 @@ void TabBar::ImplShowPage( sal_uInt16 nPos )
IMPL_LINK( TabBar, ImplClickHdl, weld::Button&, rBtn, void )
{
-if ((GetPointerState().mnState & (MOUSE_LEFT | MOUSE_MIDDLE |
MOUSE_RIGHT)) == 0)
+if ( != mpImpl->mxButtonBox->m_xFirstButton.get() && !=
mpImpl->mxButtonBox->m_xLastButton.get())
{
-// like tdf#149482 if we didn't see a mouse up, but find that the
mouse is no
-// longer pressed at this point, then bail
-mpImpl->mxButtonBox->m_xPrevRepeater->Stop();
-mpImpl->mxButtonBox->m_xNextRepeater->Stop();
-return;
+if ((GetPointerState().mnState & (MOUSE_LEFT | MOUSE_MIDDLE |
MOUSE_RIGHT)) == 0)
+{
+// like tdf#149482 if we didn't see a mouse up, but find that the
mouse is no
+// longer pressed at this point, then bail
+mpImpl->mxButtonBox->m_xPrevRepeater->Stop();
+mpImpl->mxButtonBox->m_xNextRepeater->Stop();
+return;
+}
}
EndEditMode();
[Libreoffice-bugs] [Bug 153485] Tooltip for H icon in Navigator should be "Outline Level"
https://bugs.documentfoundation.org/show_bug.cgi?id=153485 --- Comment #15 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3ae7bd3345e2f356b52ba7b8160dbcbdc4967e89 tdf#153485 align command names to show headings by outline level It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: officecfg/registry sw/inc sw/uiconfig
officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu |2 +-
sw/inc/strings.hrc |2 +-
sw/uiconfig/swriter/ui/navigatorcontextmenu.ui |2 +-
sw/uiconfig/swriter/ui/navigatorpanel.ui|4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
New commits:
commit 3ae7bd3345e2f356b52ba7b8160dbcbdc4967e89
Author: Seth Chaiklin
AuthorDate: Fri Feb 17 20:48:02 2023 +
Commit: Adolfo Jayme Barrientos
CommitDate: Tue Feb 21 07:48:39 2023 +
tdf#153485 align command names to show headings by outline level
There are three different places where a command can be given
to select the maximum allowed outline level for a displayed heading
in Navigator. This patch changes all these command labels to be
identical, so that users can recognize them as identical.
"Outline Level" -> "Show to Outline Level" in Navigator context menu
"Heading Levels Shown" -> "Show to Outline Level" in Navigator panel
"Show Outline Content to Level" -> "Show to Outline Level" in
.uno:OutlineLevelsShown and its popup dialog box.
Change-Id: I7b1eac8067251a0e2faf38f2747dcfcf1993cebb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147247
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git
a/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
b/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
index 33755db9f601..ed1d92c685c9 100644
--- a/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
+++ b/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
@@ -419,7 +419,7 @@
- Show Outline Content up to Level...
+ Show Up to Outline Level...
1
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index 476df842a9f1..454df50b1284 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -682,7 +682,7 @@
#define STR_OUTLINE_CONTENT_VISIBILITY_TOGGLE
NC_("STR_OUTLINE_CONTENT_VISIBILITY_TOGGLE", "Toggle")
#define STR_OUTLINE_CONTENT_VISIBILITY_SHOW_ALL
NC_("STR_OUTLINE_CONTENT_VISIBILITY_SHOW_ALL", "Unfold All")
#define STR_OUTLINE_CONTENT_VISIBILITY_HIDE_ALL
NC_("STR_OUTLINE_CONTENT_VISIBILITY_HIDE_ALL", "Fold All")
-#define STR_OUTLINE_LEVELS_SHOWN_TITLE
NC_("STR_OUTLINE_LEVELS_SHOWN_TITLE", "Show Outline Content to Level")
+#define STR_OUTLINE_LEVELS_SHOWN_TITLE
NC_("STR_OUTLINE_LEVELS_SHOWN_TITLE", "Show Up to Outline Level")
#define STR_OUTLINE_LEVELS_SHOWN_SPIN_LABEL
NC_("STR_OUTLINE_LEVELS_SHOWN_SPIN_LABEL", "Level (1–10):")
#define STR_OUTLINE_LEVELS_SHOWN_HELP_LABEL
NC_("STR_OUTLINE_LEVELS_SHOWN_HELP_LABEL", "Enter maximum outline level allowed
for a displayed heading.")
diff --git a/sw/uiconfig/swriter/ui/navigatorcontextmenu.ui
b/sw/uiconfig/swriter/ui/navigatorcontextmenu.ui
index 519104ba5fdb..9ef3a5bbc6d3 100644
--- a/sw/uiconfig/swriter/ui/navigatorcontextmenu.ui
+++ b/sw/uiconfig/swriter/ui/navigatorcontextmenu.ui
@@ -438,7 +438,7 @@
True
False
-Outline Level
+Show Up to Outline
Level
True
diff --git a/sw/uiconfig/swriter/ui/navigatorpanel.ui
b/sw/uiconfig/swriter/ui/navigatorpanel.ui
index f38518649c9a..7c3fd820e2d3 100644
--- a/sw/uiconfig/swriter/ui/navigatorpanel.ui
+++ b/sw/uiconfig/swriter/ui/navigatorpanel.ui
@@ -513,11 +513,11 @@
True
-Heading Levels Shown
+Show Up to Outline
Level
sw/res/sc20236.png
-Click this
icon, and then choose the number of heading outline levels that you want to
view in the Navigator window.
+Use this
option to control what headings in the document structure are displayed in the
Navigator window. Click the icon, and choose an outline level number. Any
heading with an outline number less than or equal to the selected number will
be displayed.
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/captionoptions.ui |9 + sw/uiconfig/swriter/ui/optcaptionpage.ui |8 2 files changed, 9 insertions(+), 8 deletions(-) New commits: commit 0fa6932e26ca197cb1134c1edf8e026536f87ec8 Author: Seth Chaiklin AuthorDate: Sun Feb 19 23:09:47 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Tue Feb 21 07:48:15 2023 + tdf#153243 change "Numbering by Chapter" and "Outline Level" labels Changes are made both for Insert - Caption - Caption Options and AutoCaption. "Chapter" was incorrect, because the option uses the number of the immediately prior heading. Now the label is "Heading Number Prefix" (because the number is always prepended to the caption number). Also, the label "Outline Level" is renamed "Up to level" because its function is to specify how many levels in the heading number are displayed. There is a tooltip and extended tip for "Up to level" that makes it clear that outline levels are involved. Change-Id: I1ca8c881c8ce07870efc226b075fc8ba7f27b7e5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147280 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/sw/uiconfig/swriter/ui/captionoptions.ui b/sw/uiconfig/swriter/ui/captionoptions.ui index fbe32fede7b7..83c3e8689066 100644 --- a/sw/uiconfig/swriter/ui/captionoptions.ui +++ b/sw/uiconfig/swriter/ui/captionoptions.ui @@ -102,10 +102,11 @@ True False True -Specify the maximum outline level of the immediately prior heading number to include in the caption number. +Select the number of outline levels of the immediately prior heading number to prepend to the caption number. -Specify the maximum outline level of the immediately prior heading number to include in the caption number. For numbers to appear, the selected heading must have numbering applied. +Specify the number of outline levels of the immediately prior heading number to prepend to the caption number. For example, select “2” to use the first two numbers in the heading. If [None] is selected, then no heading number is prepended. +. @@ -136,7 +137,7 @@ True False -_Outline level: +_Up to level: True level 1 @@ -166,7 +167,7 @@ True False -Numbering by Chapter +Heading Number Prefix diff --git a/sw/uiconfig/swriter/ui/optcaptionpage.ui b/sw/uiconfig/swriter/ui/optcaptionpage.ui index 0ad93bc4d888..b285d850b573 100644 --- a/sw/uiconfig/swriter/ui/optcaptionpage.ui +++ b/sw/uiconfig/swriter/ui/optcaptionpage.ui @@ -256,7 +256,7 @@ True False -Outline level: +Up to level: True level 0 @@ -306,13 +306,13 @@ False center True -Specify the maximum outline level of the immediately prior heading to prepend to the caption number. +Specify the number of outline levels of the immediately prior heading number to prepend to the caption number. If [None] is selected, then no heading number is prepended. None -Use this option to specify the outline level of the heading number that should be prepended to the caption number. The first immediately prior heading with an outline level no greater than the specified number here is used to supply the numbering that is prepended. +Specify the number of outline levels of the immediately prior heading number to prepend to the caption number. For example, select “2” to use the first two numbers in the heading. If [None] is selected, then no heading numbered is prepended. @@ -327,7 +327,7 @@ True False -Numbering by Chapter +Heading Number Prefix
[Libreoffice-bugs] [Bug 153333] Plasma Wayland: Invisible or wrong cursor when inserting geometric shapes etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=15 Michael Weghorn changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 15, which changed state. Bug 15 Summary: Plasma Wayland: Invisible or wrong cursor when inserting geometric shapes etc. https://bugs.documentfoundation.org/show_bug.cgi?id=15 What|Removed |Added Status|RESOLVED|NEW Resolution|NOTOURBUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 15, which changed state. Bug 15 Summary: Plasma Wayland: Invisible or wrong cursor when inserting geometric shapes etc. https://bugs.documentfoundation.org/show_bug.cgi?id=15 What|Removed |Added Status|RESOLVED|NEW Resolution|NOTOURBUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153333] Plasma Wayland: Invisible or wrong cursor when inserting geometric shapes etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=15 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|NEW Resolution|NOTOURBUG |--- Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4302, ||https://bugreports.qt.io/br ||owse/QTBUG-95434 --- Comment #4 from Michael Weghorn --- (In reply to Michael Weghorn from comment #2) > This is a Qt bug: > https://bugreports.qt.io/browse/QTBUG-95434 > > I've suggested a change that makes this work for me with the qt6 VCL plugin: > https://codereview.qt-project.org/c/qt/qtwayland/+/461361 However, thinking about it again, we can still avoid triggering the buggy Qt code path by implementing tdf#144302: https://gerrit.libreoffice.org/c/core/+/147379 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144302] Load cursor from PNG on kf5
https://bugs.documentfoundation.org/show_bug.cgi?id=144302 Michael Weghorn changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Status|NEW |ASSIGNED --- Comment #4 from Michael Weghorn --- Implementing this also helps avoid running into a Qt bug that makes custom cursors not show at all on Wayland, s. tdf#15/QTBUG-95434. Pending Gerrit change: https://gerrit.libreoffice.org/c/core/+/147379 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #22 from Buovjaga --- (In reply to Lee from comment #21) > That email address I used in comment 20 failed. I'm not sure how to get a > hold of the documentation team. They can now be reached here: https://community.documentfoundation.org/c/documentation/12 Can you mention where you saw the mention of that mailing list? The change to the forum happened relatively recently and there might be some references that need to be updated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #22 from Buovjaga --- (In reply to Lee from comment #21) > That email address I used in comment 20 failed. I'm not sure how to get a > hold of the documentation team. They can now be reached here: https://community.documentfoundation.org/c/documentation/12 Can you mention where you saw the mention of that mailing list? The change to the forum happened relatively recently and there might be some references that need to be updated. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #8 from Heiko Tietze --- (In reply to sdc.blanco from comment #7) > [ ] Index by outline level of immediately prior heading Keep the localization in mind. I'm in favor of (In reply to Heiko Tietze from comment #6) > [ ] Use level from source heading -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Buovjaga changed: What|Removed |Added Depends on||148047 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148047 [Bug 148047] Area fill split button does not trigger, if it is behind a chevron due to narrow window width (GTK3) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #7 from Heiko Tietze --- (In reply to sdc.blanco from comment #5) > Will highlight again the last two lines of OP. Not a fan of just Up/Down, with Move it sounds a bit more usual; but the thing is that this action colon specification indicates that we provide similar action like "Up: Table" or "Down: Section". And don't we talk about tooltips? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/core/text/porglue.hxx |3 +++
1 file changed, 3 insertions(+)
New commits:
commit 0bcce236059ae68c6dcc7bce8ceaec5d39c28f1c
Author: Miklos Vajna
AuthorDate: Mon Feb 20 20:40:19 2023 +0100
Commit: Miklos Vajna
CommitDate: Tue Feb 21 07:03:35 2023 +
sw: document SwGluePortion
This is typically subclassed, but there is a single case for footnotes
where created as-is.
Change-Id: I36649d6fa25761a76469dd0c328b54c156be4f64
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147348
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
diff --git a/sw/source/core/text/porglue.hxx b/sw/source/core/text/porglue.hxx
index d46962d454bb..aaaeec339f31 100644
--- a/sw/source/core/text/porglue.hxx
+++ b/sw/source/core/text/porglue.hxx
@@ -24,6 +24,9 @@
class SwRect;
class SwLineLayout;
+/// A glue portion is either a base class for other portions that want to have
a certain width to
+/// push text out (e.g. tab portions) or used to align SwQuoVadisPortion
instances on the right for
+/// footnotes.
class SwGluePortion : public SwLinePortion
{
private:
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Michael Weghorn changed: What|Removed |Added Depends on||144993 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144993 [Bug 144993] unable to use menus with kf5+wayland -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144993] unable to use menus with kf5+wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144993 Michael Weghorn changed: What|Removed |Added Version|7.5.0.3 release |7.2.1.2 release Hardware|x86-64 (AMD64) |All Blocks||102495 --- Comment #8 from Michael Weghorn --- (In reply to Dmitry from comment #6) > Created attachment 185498 [details] > GTK3 bug of color chooser popup > > Bug 144585 does not resolve the problem with VCL gtk3 (x11). Popups hide > right after they appear if they are hidden with drawer in classic interface > mode That's a different issue, please create a separate bug report for this as needed. This bug report here is about the qt5/kf5-specific bug that was fixed in the context of tdf#144585. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #6 from Jim Raykowski --- (In reply to sdc.blanco from comment #5) > About Tooltip. First quick thought: Press Ctrl to move heading without > subheadings. +1 I had my thinking cap on too tight with the tooltip changes when ctrl is pressed idea <:-). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: basic/source include/basic
basic/source/sbx/sbxexec.cxx | 16 +---
include/basic/sbmod.hxx |3 ++-
include/basic/sbxobj.hxx |5 ++---
3 files changed, 9 insertions(+), 15 deletions(-)
New commits:
commit 527741d528ef347b28917976efffd366c62341b1
Author: Mike Kaganski
AuthorDate: Tue Feb 21 08:00:26 2023 +0300
Commit: Mike Kaganski
CommitDate: Tue Feb 21 05:52:59 2023 +
Related: tdf#153752 Use virtual method to avoid dynamic casts
Change-Id: I97c09d82699621d5a43a525b5f2cf75ff5d131c0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147353
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/basic/source/sbx/sbxexec.cxx b/basic/source/sbx/sbxexec.cxx
index de711944d36c..af7d12c00651 100644
--- a/basic/source/sbx/sbxexec.cxx
+++ b/basic/source/sbx/sbxexec.cxx
@@ -19,7 +19,6 @@
#include
-#include
#include
#include
#include
@@ -350,7 +349,7 @@ SbxVariable* SbxObject::Execute( const OUString& rTxt )
{
SetError( ERRCODE_BASIC_SYNTAX ); break;
}
-pVar = Assign( this, this, , IsModuleCompatible() );
+pVar = Assign( this, this, , IsOptionCompatible() );
if( !pVar.is() )
{
break;
@@ -373,7 +372,7 @@ SbxVariable* SbxObject::FindQualified( const OUString&
rName, SbxClassType t )
{
return nullptr;
}
-pVar = QualifiedName( this, this, , t, IsModuleCompatible() );
+pVar = QualifiedName( this, this, , t, IsOptionCompatible() );
p = SkipWhitespace( p );
if( *p )
{
@@ -382,15 +381,10 @@ SbxVariable* SbxObject::FindQualified( const OUString&
rName, SbxClassType t )
return pVar.get();
}
-bool SbxObject::IsModuleCompatible() const
+bool SbxObject::IsOptionCompatible() const
{
-const SbxObject* pObj = this;
-while (pObj)
-{
-if (auto pMod = dynamic_cast(pObj))
-return pMod->IsCompatible();
-pObj = pObj->GetParent();
-}
+if (const SbxObject* pObj = GetParent())
+return pObj->IsOptionCompatible();
return false;
}
diff --git a/include/basic/sbmod.hxx b/include/basic/sbmod.hxx
index fac7f9e50121..7ca52276d012 100644
--- a/include/basic/sbmod.hxx
+++ b/include/basic/sbmod.hxx
@@ -94,6 +94,8 @@ protected:
SAL_DLLPRIVATE virtual void Notify( SfxBroadcaster& rBC, const SfxHint&
rHint ) override;
SAL_DLLPRIVATE void handleProcedureProperties( SfxBroadcaster& rBC, const
SfxHint& rHint );
virtual ~SbModule() override;
+bool IsOptionCompatible() const override { return mbCompat; }
+
public:
SBX_DECL_PERSIST_NODATA(SBXID_BASICMOD,2);
SbModule( const OUString&, bool bVBASupport = false );
@@ -123,7 +125,6 @@ public:
SAL_DLLPRIVATE bool HasExeCode();
bool IsVBASupport() const { return mbVBASupport; }
SAL_DLLPRIVATE void SetVBASupport( bool bSupport );
-bool IsCompatible() const { return mbCompat; }
sal_Int32 GetModuleType() const { return mnType; }
void SetModuleType( sal_Int32 nType ) { mnType = nType; }
bool isProxyModule() const { return bIsProxyModule; }
diff --git a/include/basic/sbxobj.hxx b/include/basic/sbxobj.hxx
index 34c117d33853..33ffc98c77d9 100644
--- a/include/basic/sbxobj.hxx
+++ b/include/basic/sbxobj.hxx
@@ -41,6 +41,8 @@ protected:
virtual bool StoreData( SvStream& ) const override;
virtual ~SbxObject() override;
virtual void Notify( SfxBroadcaster& rBC, const SfxHint& rHint ) override;
+virtual bool IsOptionCompatible() const; // Module's Option Compatible
+
public:
SBX_DECL_PERSIST_NODATA(SBXID_OBJECT,1);
SbxObject( const OUString& rClassname );
@@ -78,9 +80,6 @@ public:
SbxArray* GetObjects() { return pObjs.get(); }
// Debugging
void Dump( SvStream&, bool bDumpAll );
-
-private:
-bool IsModuleCompatible() const; // Module's Option Compatible
};
#endif // INCLUDED_BASIC_SBXOBJ_HXX
[Libreoffice-bugs] [Bug 153766] Conditional formatting needs autocalculate to be enabled to work
https://bugs.documentfoundation.org/show_bug.cgi?id=153766 --- Comment #2 from ady --- > This is happening in current master and back to 3.5, so my guess is this > could be an old performance workaround. There is one thing to consider. IIUC, CF works "somewhat" like volatile functions, so it may demand more calculation resources in some sense. There was a time when users would make changes to a workbook, and only then would activate calculation (whether automatic or manual). Nowadays, most "normal" size worksheets (if there is such a thing) are used with AutoCalculate set on, whereas "big" workbooks are calculated manually in order not to waste time waiting for some meaningless calculation, until the results are really needed. Setting conditional format to disregard the Calculate setting could be detrimental for such "big" size workbook users that intentionally set AutoCalculate to off. IDK whether CF deserves its own "AutoCalculate" setting, but that seems a possible way to allow users control their resources according to their needs and priorities, instead of imposing one way or the other. The additional factor to consider would be the potential discrepancy between the way a cell "looks" (CF) and the (not-yet-calculated) results somewhere in the worksheet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: basic/source include/basic include/unotest sc/qa sc/source unotest/source
basic/source/classes/sb.cxx |2
basic/source/classes/sbxmod.cxx | 28 +
basic/source/comp/parser.cxx |6 +-
basic/source/runtime/runtime.cxx |2
basic/source/runtime/stdobj.cxx |2
basic/source/sbx/sbxexec.cxx | 66 +-
include/basic/sbmod.hxx | 10 ++-
include/basic/sbxobj.hxx |3 +
include/unotest/macros_test.hxx |3 -
sc/qa/extras/testdocuments/ForEachInSelection.ods |binary
sc/qa/extras/vba-macro-test.cxx | 31 ++
sc/source/core/tool/interpr4.cxx |2
unotest/source/cpp/macros_test.cxx|9 +--
13 files changed, 110 insertions(+), 54 deletions(-)
New commits:
commit ccd0ef98f76011f108f8ea1d282b96386dba0a6a
Author: Mike Kaganski
AuthorDate: Mon Feb 20 16:16:40 2023 +0300
Commit: Mike Kaganski
CommitDate: Tue Feb 21 04:30:34 2023 +
tdf#153752: SbxObject::Execute: extra characters in Option Compatible mode
Change-Id: Ib3e4bd9eb9a249123a686f2434ded7b529fb050f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147345
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/basic/source/classes/sb.cxx b/basic/source/classes/sb.cxx
index f1ab6dd1da0c..0296e2238ca1 100644
--- a/basic/source/classes/sb.cxx
+++ b/basic/source/classes/sb.cxx
@@ -744,7 +744,7 @@ SbClassModuleObject::SbClassModuleObject( SbModule*
pClassModule )
}
}
SetModuleType( ModuleType::CLASS );
-mbVBACompat = pClassModule->mbVBACompat;
+mbVBASupport = pClassModule->mbVBASupport;
}
SbClassModuleObject::~SbClassModuleObject()
diff --git a/basic/source/classes/sbxmod.cxx b/basic/source/classes/sbxmod.cxx
index f38e729185db..aaad6cd9bb41 100644
--- a/basic/source/classes/sbxmod.cxx
+++ b/basic/source/classes/sbxmod.cxx
@@ -416,9 +416,9 @@ static bool getDefaultVBAMode( StarBASIC* pb )
// A Basic module has set EXTSEARCH, so that the elements, that the module
contains,
// could be found from other module.
-SbModule::SbModule( const OUString& rName, bool bVBACompat )
+SbModule::SbModule( const OUString& rName, bool bVBASupport )
: SbxObject( "StarBASICModule" ),
- pBreaks(nullptr), mbVBACompat( bVBACompat ), bIsProxyModule( false )
+ pBreaks(nullptr), mbVBASupport(bVBASupport), mbCompat(bVBASupport),
bIsProxyModule(false)
{
SetName( rName );
SetFlag( SbxFlagBits::ExtSearch | SbxFlagBits::GlobalSearch );
@@ -802,11 +802,11 @@ void SbModule::Notify( SfxBroadcaster& rBC, const
SfxHint& rHint )
void SbModule::SetSource32( const OUString& r )
{
// Default basic mode to library container mode, but... allow Option
VBASupport 0/1 override
-SetVBACompat( getDefaultVBAMode( static_cast< StarBASIC*>( GetParent() ) )
);
+SetVBASupport( getDefaultVBAMode( static_cast< StarBASIC*>( GetParent() )
) );
aOUSource = r;
StartDefinitions();
SbiTokenizer aTok( r );
-aTok.SetCompatible( IsVBACompat() );
+aTok.SetCompatible( IsVBASupport() );
while( !aTok.IsEof() )
{
@@ -837,12 +837,13 @@ void SbModule::SetSource32( const OUString& r )
eCurTok = aTok.Next();
if( eCurTok == COMPATIBLE )
{
+mbCompat = true;
aTok.SetCompatible( true );
}
else if ( ( eCurTok == VBASUPPORT ) && ( aTok.Next() ==
NUMBER ) )
{
bool bIsVBA = ( aTok.GetDbl()== 1 );
-SetVBACompat( bIsVBA );
+SetVBASupport( bIsVBA );
aTok.SetCompatible( bIsVBA );
}
}
@@ -974,15 +975,16 @@ static void ClearUnoObjectsInRTL_Impl( StarBASIC* pBasic )
}
-void SbModule::SetVBACompat( bool bCompat )
+void SbModule::SetVBASupport( bool bSupport )
{
-if( mbVBACompat == bCompat )
+if( mbVBASupport == bSupport )
return;
-mbVBACompat = bCompat;
+mbVBASupport = bSupport;
// initialize VBA document API
-if( mbVBACompat ) try
+if( mbVBASupport ) try
{
+mbCompat = true;
StarBASIC* pBasic = static_cast< StarBASIC* >( GetParent() );
uno::Reference< lang::XMultiServiceFactory > xFactory(
getDocumentModel( pBasic ), uno::UNO_QUERY_THROW );
xFactory->createInstance( "ooo.vba.VBAGlobals" );
@@ -1067,7 +1069,7 @@ namespace
// Run a Basic-subprogram
void SbModule::Run( SbMethod* pMeth )
{
-SAL_INFO("basic","About to run " << pMeth->GetName() << ", vba compatmode
is " << mbVBACompat );
+SAL_INFO("basic","About to run " << pMeth->GetName() << ", vba compatmode
is " << mbVBASupport );
static sal_uInt16 nMaxCallLevel = 0;
@@ -1088,7 +1090,7 @@
[Libreoffice-bugs] [Bug 153728] Can't assign macro to autotext
https://bugs.documentfoundation.org/show_bug.cgi?id=153728 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153713] Feldbefehl - Verweis einfügen
https://bugs.documentfoundation.org/show_bug.cgi?id=153713 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153424] Autocorrect for "Replace Custom Styles" does not work when a custom style is applied to an empty paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=153424 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 153749] Calc Text Box cursor bug
https://bugs.documentfoundation.org/show_bug.cgi?id=153749 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150583] Have an option - better, default - of no auto-formatting.
https://bugs.documentfoundation.org/show_bug.cgi?id=150583 --- Comment #3 from QA Administrators --- Dear loathgoogel, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153713] Feldbefehl - Verweis einfügen
https://bugs.documentfoundation.org/show_bug.cgi?id=153713 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147075] Window goes to 1x2 pixel size when moving
https://bugs.documentfoundation.org/show_bug.cgi?id=147075 --- Comment #7 from QA Administrators --- Dear michael.vanderford, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134791] UI: Options dialog window is too small in width and height
https://bugs.documentfoundation.org/show_bug.cgi?id=134791 --- Comment #23 from QA Administrators --- Dear Thomas Lendo, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140163] "Clear direct formatting" deletes column breaks, but the effect is not shown until saved and reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=140163 --- Comment #2 from QA Administrators --- Dear Ming Hua, 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 85644] Some bullet lists don't have their bullets displayed in Read-Only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=85644 --- Comment #9 from QA Administrators --- Dear Daniel Grigoras, 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 69487] EDITING: Extraneous New Line When Pasting FROM Calc into Other Programs
https://bugs.documentfoundation.org/show_bug.cgi?id=69487 --- Comment #10 from QA Administrators --- Dear Zoffix Znet, 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 114010] Interfering shortcuts for underline / double underline
https://bugs.documentfoundation.org/show_bug.cgi?id=114010 --- Comment #3 from QA Administrators --- Dear Heiko Tietze, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #21 from Lee <92ma...@gmail.com> --- That email address I used in comment 20 failed. I'm not sure how to get a hold of the documentation team. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #21 from Lee <92ma...@gmail.com> --- That email address I used in comment 20 failed. I'm not sure how to get a hold of the documentation team. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #20 from Lee <92ma...@gmail.com> --- Rather than some comments in the WIKI, perhaps the need for setting "evaluate up to level" should be in the User's Guide discussion of the e# element for customizing the TOC? I just sent that suggestion to the documentation area (LibreOffice Documentation ). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #20 from Lee <92ma...@gmail.com> --- Rather than some comments in the WIKI, perhaps the need for setting "evaluate up to level" should be in the User's Guide discussion of the e# element for customizing the TOC? I just sent that suggestion to the documentation area (LibreOffice Documentation ). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 116625] [META] Bugs where document modification status is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=116625 Aron Budea changed: What|Removed |Added Depends on||146532 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146532 [Bug 146532] Updating DDE links should dirty the document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112581 Aron Budea changed: What|Removed |Added Depends on||146532 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146532 [Bug 146532] Updating DDE links should dirty the document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146532] Updating DDE links should dirty the document
https://bugs.documentfoundation.org/show_bug.cgi?id=146532 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com Blocks||112581, 116625 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112581 [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=116625 [Bug 116625] [META] Bugs where document modification status is wrong -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151413] Unable to create a DDE link to a file with special characters in name on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=151413 Aron Budea changed: What|Removed |Added Blocks||112581 CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112581 [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112581 Aron Budea changed: What|Removed |Added Depends on||151413 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151413 [Bug 151413] Unable to create a DDE link to a file with special characters in name on Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112581 Aron Budea changed: What|Removed |Added Depends on||151429 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151429 [Bug 151429] DDE link drops Unicode characters not representable in Windows system encoding -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112581] [META] Linked (non-embedded) external files bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112581 Aron Budea changed: What|Removed |Added Depends on||152717 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152717 [Bug 152717] DDE linking in calc is broken since 7.4.3 RC1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153766] Conditional formatting needs autocalculate to be enabled to work
https://bugs.documentfoundation.org/show_bug.cgi?id=153766 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Some related bugs: tdf#56896 tdf#57028 +1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153768] Conditional formatting does not have "Stop if true" option
https://bugs.documentfoundation.org/show_bug.cgi?id=153768 --- Comment #2 from m.a.riosv --- https://help.libreoffice.org/7.6/en-US/text/scalc/01/0512.html?System=WIN=CALC=modules/scalc/ui/conditionalformatdialog/dialog-action_area1#bm_id3152518 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153768] Conditional formatting does not have "Stop if true" option
https://bugs.documentfoundation.org/show_bug.cgi?id=153768 m.a.riosv changed: What|Removed |Added Severity|enhancement |normal -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153741] calc 7.4.5 EDITING keeps protected a sheet created by excel with password
https://bugs.documentfoundation.org/show_bug.cgi?id=153741 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from m.a.riosv --- Hi, I reply to this email because I don't know how to add comments to the bug reporting. I can't send the spreadsheet not working for security reasons because it is a list of sites with id and password. I was not able to get the same effect with another file. After different tests, the problem disappeared when changing the password. Then I consider my problem solved even if the case is weird. Sorry for the inconvenience. If it happens again with a less sensitive file, I will come back to you. Thanks Le 19/02/2023 à 23:04, bugzilla-dae...@bugs.documentfoundation.org a écrit : > m.a.riosv changed bug 153741 > What Removed Added > Ever confirmed1 > CCmiguelange...@libreoffice.org > StatusUNCONFIRMED NEEDINFO > > Comment # 1 on bug 153741 from m.a.riosv > Please provide a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 1a022fcbc8bf256eb04319aa3ecfc4a3c1b5 Author: Seth Chaiklin AuthorDate: Tue Feb 21 01:10:07 2023 + Commit: Gerrit Code Review CommitDate: Tue Feb 21 01:10:07 2023 + Update git submodules * Update helpcontent2 from branch 'master' to e75f5c367876eb7c983ea5e94eda777c4e0f247b - tdf#152605 update "chapter heading" to "numbered heading" Change-Id: I9afe6af9e039e2e40f9d19558fffd5caa1eeb645 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147281 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/helpcontent2 b/helpcontent2 index 336d8e277daa..e75f5c367876 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 336d8e277daa429fe5c271d7e5169e179dd4aaf9 +Subproject commit e75f5c367876eb7c983ea5e94eda777c4e0f247b
[Libreoffice-commits] help.git: source/text
source/text/shared/02/0605.xhp | 11 +-- source/text/shared/02/0606.xhp | 11 +-- source/text/swriter/02/0607.xhp |5 - source/text/swriter/02/0608.xhp |5 - source/text/swriter/02/0612.xhp |5 - source/text/swriter/02/0613.xhp |5 - 6 files changed, 34 insertions(+), 8 deletions(-) New commits: commit e75f5c367876eb7c983ea5e94eda777c4e0f247b Author: Seth Chaiklin AuthorDate: Sun Feb 19 23:13:05 2023 + Commit: Seth Chaiklin CommitDate: Tue Feb 21 01:10:07 2023 + tdf#152605 update "chapter heading" to "numbered heading" Change-Id: I9afe6af9e039e2e40f9d19558fffd5caa1eeb645 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147281 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/source/text/shared/02/0605.xhp b/source/text/shared/02/0605.xhp index 51089004b3..07b9085d47 100644 --- a/source/text/shared/02/0605.xhp +++ b/source/text/shared/02/0605.xhp @@ -32,9 +32,9 @@ Demote Outline Level -Moves a chapter heading where the cursor is located, or selected chapter headings, down one outline level. Moves a list paragraph where the cursor is located, or selected list paragraphs, down one list level.UFI: need two files for numbering and outline, also for 0606.xhp +Moves a numbered heading where the cursor is located, or selected headings, down one outline level. Moves a list paragraph where the cursor is located, or selected list paragraphs, down one list level.UFI: need two files for numbering and outline, also for 0606.xhp -The Demote Outline Level icon is on the Bullets and Numbering bar, which appears when the cursor is positioned on a numbered chapter heading or a list paragraph. +The Demote Outline Level icon is on the Bullets and Numbering bar, which appears when the cursor is positioned on a numbered heading or a list paragraph. The Demote icon is on the Outline bar, which appears when working in the outline view. This function can also be called by pressing Alt+Shift+Right Arrow. @@ -48,5 +48,12 @@ + + + + + + + diff --git a/source/text/shared/02/0606.xhp b/source/text/shared/02/0606.xhp index 9977ec7956..f4803fd293 100644 --- a/source/text/shared/02/0606.xhp +++ b/source/text/shared/02/0606.xhp @@ -32,9 +32,9 @@ Promote Outline Level -Moves a chapter heading where the cursor is located, or selected chapter headings, up one outline level. Moves a list paragraph where the cursor is located, or selected list paragraphs, up one list level. +Moves a numbered heading where the cursor is located, or selected headings, up one outline level. Moves a list paragraph where the cursor is located, or selected list paragraphs, up one list level. -The Promote Outline Level icon is on the Bullets and Numbering bar, which appears when the cursor is positioned on a numbered chapter heading or a list paragraph.The Promote icon is on the Outline bar, which appears when working in the outline view. This function can also be called by pressing Alt+Shift+Left Arrow. +The Promote Outline Level icon is on the Bullets and Numbering bar, which appears when the cursor is positioned on a numbered heading or a list paragraph.The Promote icon is on the Outline bar, which appears when working in the outline view. This function can also be called by pressing Alt+Shift+Left Arrow. @@ -47,5 +47,12 @@ + + + + + + + diff --git a/source/text/swriter/02/0607.xhp b/source/text/swriter/02/0607.xhp index 58123dbd09..0df1d9f9b3 100644 --- a/source/text/swriter/02/0607.xhp +++ b/source/text/swriter/02/0607.xhp @@ -32,7 +32,7 @@ i66535, was Shift down with Subpoints Demote Outline Level with Subpoints -Demotes the list of a list paragraph where the cursor is located and its subpoints to the next list level. Multiple list paragraphs can be selected. Demotes the outline level of a chapter heading where the cursor is located and all its subheadings to the next outline level. This command is active only when the cursor is positioned in a list paragraph or a chapter heading. +Demotes the list of a list paragraph where the cursor is located and its subpoints to the next list level. Multiple list paragraphs can be selected. Demotes the outline level of a numbered heading where the cursor is located and all its subheadings to the next outline level. This command is active only when the cursor is positioned in a list paragraph or a numbered heading. @@ -47,5 +47,8 @@ + + + diff --git a/source/text/swriter/02/0608.xhp b/source/text/swriter/02/0608.xhp index 01f174dd37..549cfaab4a 100644 --- a/source/text/swriter/02/0608.xhp +++ b/source/text/swriter/02/0608.xhp @@ -32,7 +32,7 @@ i66535, was Shift up with Subpoints Promote Outline Level With Subpoints -Promotes the list level of a list paragraph where the cursor is located
[Libreoffice-bugs] [Bug 153737] After upgrading from LO 7.3.7.2 to 7.4.5.1 vLookup with DDE file descriptor does not work right
https://bugs.documentfoundation.org/show_bug.cgi?id=153737 m.a.riosv changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from m.a.riosv --- Fixed for 7.4.6 *** This bug has been marked as a duplicate of bug 152717 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109329] [META] VLookup function bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109329 Bug 109329 depends on bug 153737, which changed state. Bug 153737 Summary: After upgrading from LO 7.3.7.2 to 7.4.5.1 vLookup with DDE file descriptor does not work right https://bugs.documentfoundation.org/show_bug.cgi?id=153737 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #4 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #3) > Don't see why we have to change the E# into H#. Heading # Would seem more confusing to me to click on "Heading No." and have E# show up in the Structure, than H# > it seems the E# has been chosen randomly. Probably to make link to E, with E# being the Entry number. In effect: "Heading number" and "Heading content" (but not suggesting that user PoV must correspond to underlying implementation logic). > Side note: funny, And more supporting evidence... -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #4 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #3) > Don't see why we have to change the E# into H#. Heading # Would seem more confusing to me to click on "Heading No." and have E# show up in the Structure, than H# > it seems the E# has been chosen randomly. Probably to make link to E, with E# being the Entry number. In effect: "Heading number" and "Heading content" (but not suggesting that user PoV must correspond to underlying implementation logic). > Side note: funny, And more supporting evidence... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153712] "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=153712 --- Comment #3 from sdc.bla...@youmail.dk --- (In reply to sdc.blanco from comment #2) > 2. will wait for discussion Select "E#" in ToC Entries tab. The dropdown box for "Format" offers "Number" and "Number without separator". This is consistent with point that this control is like Document Field (where Heading Number, Heading Contents, etc. are listed in the "Format" field). Not recommending to use "Format" with "Heading Info" in the Index Entries tab - just highlighting the underlying concept of what is going on. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #5 from sdc.bla...@youmail.dk --- Resisting "outline" as too ambiguous (for general user) And what about the "Delete"? (comment 1) Delete Outline? Will highlight again the last two lines of OP. Up: Heading and Text Down: Heading and Text Delete: Heading and Text 1. No need to mention "Move" -- it is implicit in Up and Down. 2. "Heading" in command name links to section title "Headings" About Tooltip. First quick thought: Press Ctrl to move heading without subheadings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153771] New: Automatic sync of settings of multiple LibreOffice installations
https://bugs.documentfoundation.org/show_bug.cgi?id=153771 Bug ID: 153771 Summary: Automatic sync of settings of multiple LibreOffice installations Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: go...@iki.fi Description: If you are using LibreOffice with multiple computers regularly, tweaking UI/Settings can be overwhelmingly laborous as you have to do it to each installation separately. E.g. if you change something under Customize... (e.g. Toolbar tools or Context menus) you have to do it separately for each installation. One solution would be that you can select/define a custom location for the settings folder that is typically (in Windows) located under USER/AppData/Roaming/Libreoffice and put this folder to Dropbox, Onedrive or any other cloud syncing service that you are using. Of course there could come issues if all instances are open simultaneously in different computers and this folder has settings related to the state of the program. So in long term in might make sense to separate content of the folder to 2 parts. A. those that can be synced via 3rd party cloud service, B. those that cannot. Actual Results: no sync Expected Results: should be sync option Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153712] "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=153712 --- Comment #2 from sdc.bla...@youmail.dk --- 1. Ok. "Heading Info" 2. will wait for discussion 3. Could label this control: "Heading Info" -- which would keep the link to the button. See next point. 4-5. This control is similar to Document Field "Heading" (see bug 153560), which now uses "heading number" and "heading contents" and "heading number and contents" (these three labels correspond to, and seem like better labels, for the current dropdown box labels). If "heading" was always in the dropdown box, then the link to "Heading Info" (points 1 and 3) should be apparent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153749] Calc Text Box cursor bug
https://bugs.documentfoundation.org/show_bug.cgi?id=153749 --- Comment #3 from golemus --- >To me, the current behaviour does make sense: >- A single click selects the object, and allow drag-and-dropping from anywhere >on >the from, and moving it with the arrows. If once decides to starts adding >text in >selection mode, it is naturally added at the end of existing text, a >good >default. An extra click can place the cursor wherever we want in the >text. >- Double-clicking it will place the cursor where the pointer is, and text can >be >entered there. First of all lets acknowledge that this issue is not only with Calc vs. Excel but also extends to Impress vs. Powerpoint text boxes. In Excel/Powerpoint a single click puts cursor directly where clicked. If you want to move textbox with arrow keys you have to click handle in the edge or corner. IMO the more common need should be behind single click which at least for me (and I'd imagine majority of users) is to edit the text inside the box instead of moving the box. Also majority of users probably come from MS Office and are already more used to that sort of behavior. How to implement this then? IMO there could be (at least for the next 3-5 years) a "single click textbox editing" setting somewhere under Options... menu in LibreOffice. Its default value would be "disabled" in beginning but changed to "enabled" after 2 years or so. This setting would change behavior of textboxes in Calc and Impress as described above so that single click starts to directly edit from where cursor was pressed. >We need the two modes, selection and editing, otherwise moving the text box >>with keyboard arrows would not work (important from an accessibility point of >>view). As selection is probably lesser used mode it could be enabled by clicking edges/corners or clicking inside the textbox and pressing ESC to get from editing to selection mode. >Not sure about default text box background. If one wants to have a text box >>with a solid fill, inserting a shape (e.g. rectangle) is easy enough, >although >the default format is centered. I tried it and it is not really a solution. I am using textbox as a notepad so centering text in the middle is not an option. Although when using Impress centering probably makes more sense. As you know internals of Libreoffice better could you maybe make the above suggestions "Single Click Textbox Editing" and "solid white or graywhite background as default Area... values/fills for Calc textbox" to the right discussion thread where they would get more attention? >Do you think that is sufficient and could be closed as "not a bug" ? I could sware that in addition to everything discussed until now I also witnessed a bug where there is no blinking cursor at all while I am writing text inside the text box. That would definitely be a bug as there should always be a blinking cursor (except for first letter in some exceptions) when you are writing text to an app. But I am unable to reproduce it anymore. I am 95% sure that I experienced this behavior in textbox in Libreoffice 7.3.7. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153768] Conditional formatting does not have "Stop if true" option
https://bugs.documentfoundation.org/show_bug.cgi?id=153768 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153768] Conditional formatting does not have "Stop if true" option
https://bugs.documentfoundation.org/show_bug.cgi?id=153768 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Created attachment 185507 --> https://bugs.documentfoundation.org/attachment.cgi?id=185507=edit Modified sample file. Looks like a bug, seems to me, mixing the icon set with other condition. Works fine with a different type of condition (sample file). And splitting the icon set condition to a different CF also works as expected (sample file). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 16a35542aa07ed69c6c699d1c17f076d87708958 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/inc sw/qa sw/uiconfig
sw/inc/strings.hrc| 10 +-
sw/qa/uitest/fieldDialog/tdf143483.py | 16
sw/uiconfig/swriter/ui/flddocumentpage.ui |6 +++---
3 files changed, 16 insertions(+), 16 deletions(-)
New commits:
commit 842ed5e6b02939ca57db90f08ce5877836ae45ed
Author: Seth Chaiklin
AuthorDate: Sun Feb 19 10:47:57 2023 +
Commit: Seth Chaiklin
CommitDate: Tue Feb 21 00:22:24 2023 +
tdf#153560 "chapter" -> "heading" for Type and Format and adjust "level"
label
* also change "name" to "contents" for Format
* change "Outline Level" to "Up to level" and add colon, because it
is a buddy control. The new label gives a better indication of the
function of the control.
* update tooltip and extended tip for the "Up to level" option.
Needed to modify unit test: sw/qa/uitest/fieldDialog/tdf143483.py
Change-Id: Idafd693fe4ce161d4fa069da59a78a6111be8e8a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147276
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin
diff --git a/sw/inc/strings.hrc b/sw/inc/strings.hrc
index 7e41e6b08cae..476df842a9f1 100644
--- a/sw/inc/strings.hrc
+++ b/sw/inc/strings.hrc
@@ -908,7 +908,7 @@
#define STR_TIMEFLD NC_("STR_TIMEFLD", "Time")
#define STR_FILENAMEFLD NC_("STR_FILENAMEFLD", "File
name")
#define STR_DBNAMEFLD NC_("STR_DBNAMEFLD", "Database
Name")
-#define STR_CHAPTERFLD NC_("STR_CHAPTERFLD",
"Chapter")
+#define STR_CHAPTERFLD NC_("STR_CHAPTERFLD",
"~Heading")
#define STR_PAGENUMBERFLD NC_("STR_PAGENUMBERFLD", "Page
number")
#define STR_DOCSTATFLD NC_("STR_DOCSTATFLD",
"Statistics")
#define STR_AUTHORFLD NC_("STR_AUTHORFLD", "Author")
@@ -1003,10 +1003,10 @@
/*
Description: format chapter
*/
-#define FMT_CHAPTER_NAMENC_("FMT_CHAPTER_NAME",
"Chapter name")
-#define FMT_CHAPTER_NO NC_("FMT_CHAPTER_NO", "Chapter
number")
-#define FMT_CHAPTER_NO_NOSEPARATOR
NC_("FMT_CHAPTER_NO_NOSEPARATOR", "Chapter number without separator")
-#define FMT_CHAPTER_NAMENO NC_("FMT_CHAPTER_NAMENO",
"Chapter number and name")
+#define FMT_CHAPTER_NAMENC_("FMT_CHAPTER_NAME",
"Heading contents")
+#define FMT_CHAPTER_NO NC_("FMT_CHAPTER_NO", "Heading
number")
+#define FMT_CHAPTER_NO_NOSEPARATOR
NC_("FMT_CHAPTER_NO_NOSEPARATOR", "Heading number without separator")
+#define FMT_CHAPTER_NAMENO NC_("FMT_CHAPTER_NAMENO",
"Heading number and contents")
/*
Description: formats
*/
diff --git a/sw/qa/uitest/fieldDialog/tdf143483.py
b/sw/qa/uitest/fieldDialog/tdf143483.py
index 357c283badbf..03eeceb7954a 100644
--- a/sw/qa/uitest/fieldDialog/tdf143483.py
+++ b/sw/qa/uitest/fieldDialog/tdf143483.py
@@ -21,26 +21,26 @@ class Tdf143483(UITestCase):
with
self.ui_test.execute_dialog_through_command(".uno:FieldDialog") as xDialog:
xDoc = xDialog.getChild("type-doc")
-self.assertEqual("Chapter",
get_state_as_dict(xDoc)['SelectEntryText'])
+self.assertEqual("Heading",
get_state_as_dict(xDoc)['SelectEntryText'])
xFormat = xDialog.getChild("format-doc")
-self.assertEqual("Chapter name",
get_state_as_dict(xFormat)['SelectEntryText'])
+self.assertEqual("Heading contents",
get_state_as_dict(xFormat)['SelectEntryText'])
xNext = xDialog.getChild("next")
xNext.executeAction("CLICK", tuple())
-self.assertEqual("Chapter",
get_state_as_dict(xDoc)['SelectEntryText'])
-self.assertEqual("Chapter number",
get_state_as_dict(xFormat)['SelectEntryText'])
+self.assertEqual("Heading",
get_state_as_dict(xDoc)['SelectEntryText'])
+self.assertEqual("Heading number",
get_state_as_dict(xFormat)['SelectEntryText'])
xNext.executeAction("CLICK", tuple())
-self.assertEqual("Chapter",
get_state_as_dict(xDoc)['SelectEntryText'])
-self.assertEqual("Chapter number and name",
get_state_as_dict(xFormat)['SelectEntryText'])
+self.assertEqual("Heading",
get_state_as_dict(xDoc)['SelectEntryText'])
+self.assertEqual("Heading number and contents",
get_state_as_dict(xFormat)['SelectEntryText'])
xNext.executeAction("CLICK", tuple())
-
[Libreoffice-bugs] [Bug 153637] Rename "Use level from source chapter" to "Use outline level from document headings" in Type tab of Insert Table of Contents, Index, or Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153637 --- Comment #7 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #6) > By picking "Tables", for example, you insert a ToC with all table captions > (excluding the actual caption text) Not "table captions". Your index is composed of the Table Name(s). To confirm, use Table Properties to change a table name and update the index. > but how naive users would read it. As a naive user, I would expect the label to refer to the relevant aspects that I need to understand, and then look to the help page to find out what the words mean. Seems too optimistic (in this case) for the label to be "transparent" without some experience creating some indices in this context, along with some reading (even if just plus tooltip/extended tip). Also relevant to consider the context in which this checkbox appears. In the "Create From" section, with the checkbox under the Tables, etc. Even as a naive user, I would expect the index to use the objects that I check. Then, if I made an index (without checking the "Use level..." box), I would see everything flush left, and then look at the label on the checkbox, and try to guess from the words what it is doing (and then see if the help page could give an idea of how to interpret those words). For now ... even after considering and working with your three suggestions, I keep coming back, for a variety of reasons, to: [ ] Index by outline level of immediately prior heading (immediately is needed because there can be multiple prior headings). Primary reason is that it points to the relevant features that will affect the output. Note that "Index" is also a verb. Meanwhile -- thinking about how the dialog would appear from a naive user PoV has motivated another trial balloonbug 153770. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153770 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153770 [Bug 153770] Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153770] Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index
https://bugs.documentfoundation.org/show_bug.cgi?id=153770 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153770] Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index
https://bugs.documentfoundation.org/show_bug.cgi?id=153770 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153770] New: Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index
https://bugs.documentfoundation.org/show_bug.cgi?id=153770 Bug ID: 153770 Summary: Proposal to modify "Create Index or Table of Contents" and Type-dependent "Create From" sections in Type tab of ToC/Index Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Discussion in bug 153637, comment 6, raised the question of "how does the naive user read [one of the labels] - which gave a useful perspective for looking at the dialog. Here is an attempt to simplify/streamline, make meanings of sections more explicit. The focus is on the two lower sections, with the titles: Create Index or Table of Contents Create From - Scope (of ToC or Index) ( ) Entire Document ( ) Chapter [depending on selected Type] Create ToC From Evaluate up to level [] (underneath the 3 checkboxes) Create Table (of Figures) From Create Index (of Tables) From Create Index From (User-defined) Create Table (of Objects) From no change for Alphabetical Index and Bibliography -- Some explanations. 1. Instead of "Create" appearing twice, "Scope" should be meaningful, and why have a dropdown with 2 items? (optional whether "Index and TOC" should be mentioned.) 2. The current "Create From" section changes, depending on the selected Type. a. It should be possible to identify the specific kind of Index or TOC that is being created, as illustrated above (i.e., much more specific than "Create From") b. The "Evaluate up to level" in Type TOC is always index level (but as discussed in bug 153596, can be left unspecified for now), so it can be moved meaningful down. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 --- Comment #11 from ady --- (In reply to V Stuart Foote from comment #10) > (In reply to ady from comment #9) > The Win10/Win11 Settings -> Display -> 'Make text bigger' control in the > os/DE provides exactly the adjustment needed for this issue. As I already mentioned, I already have adjustments to that OS's control, among others, and I still have the need to use the OS's zoom feature when I need to read the formula bar. So, please, I am asking you to be more flexible in the terminology. It _can_ help, but it is not the ultimate solution; it might not be enough. That OS's setting affects other areas of the OS's UI, and other programs too. Claiming that users can freely keep making that setting higher and higher (or lower and lower for this particular ticket) is not realistic; yes, some users could, but there are other reasons not to modify it (more than it has been). The formula bar in Calc is not the only factor to be considered when modifying that setting. This is the reason for the recurring requests in several tickets, either for accessibility reasons, for convenience, or for reduction of UI glitches. > > Similar UI controls in macOS and the various Linux os/DEs. > > Not every adjustment must be in the LibreOffice UI, but there is room tweak > the UI to use "other than os/DE system UI font" and also to extablish a > different fontsize for the inputwin.hxx/.cxx of the 'Formula Bar' widget. > > Again this is => WFM, and the other BZ issues are already open for the > "tweaks". The WFM definition would need, IMHO, more input/feedback from the OP (iaganicshe). According to the report, the CTL font that is being shown in the formula bar is not adequate ATM in/for that system. You seem to suggest, IIUC, that the System/OS font should be modified for this, and that the current defaults in LO are ideal for every_and_all configurations/systems (i.e. "just change the system's configurations"). I assume some users won't like/agree with that idea, just for Calc's formula bar, or they might have a different default language (not CTL) for the system/OS. It might be helpful to have the OP's feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 --- Comment #11 from ady --- (In reply to V Stuart Foote from comment #10) > (In reply to ady from comment #9) > The Win10/Win11 Settings -> Display -> 'Make text bigger' control in the > os/DE provides exactly the adjustment needed for this issue. As I already mentioned, I already have adjustments to that OS's control, among others, and I still have the need to use the OS's zoom feature when I need to read the formula bar. So, please, I am asking you to be more flexible in the terminology. It _can_ help, but it is not the ultimate solution; it might not be enough. That OS's setting affects other areas of the OS's UI, and other programs too. Claiming that users can freely keep making that setting higher and higher (or lower and lower for this particular ticket) is not realistic; yes, some users could, but there are other reasons not to modify it (more than it has been). The formula bar in Calc is not the only factor to be considered when modifying that setting. This is the reason for the recurring requests in several tickets, either for accessibility reasons, for convenience, or for reduction of UI glitches. > > Similar UI controls in macOS and the various Linux os/DEs. > > Not every adjustment must be in the LibreOffice UI, but there is room tweak > the UI to use "other than os/DE system UI font" and also to extablish a > different fontsize for the inputwin.hxx/.cxx of the 'Formula Bar' widget. > > Again this is => WFM, and the other BZ issues are already open for the > "tweaks". The WFM definition would need, IMHO, more input/feedback from the OP (iaganicshe). According to the report, the CTL font that is being shown in the formula bar is not adequate ATM in/for that system. You seem to suggest, IIUC, that the System/OS font should be modified for this, and that the current defaults in LO are ideal for every_and_all configurations/systems (i.e. "just change the system's configurations"). I assume some users won't like/agree with that idea, just for Calc's formula bar, or they might have a different default language (not CTL) for the system/OS. It might be helpful to have the OP's feedback. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153485] Tooltip for H icon in Navigator should be "Outline Level"
https://bugs.documentfoundation.org/show_bug.cgi?id=153485 --- Comment #14 from Rizal Muttaqin --- (In reply to sdc.blanco from comment #13) > Happy to see that I have reinvented the wheel. More importantly: perhaps you > have a useful direction in which to go, and I will get out of your way. I would rather to see different bug report for this request -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151745] Resizing window with Meta+left/right arrow puts Sidebar into glitchy state in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=151745 Samuel Mehrbrodt (allotropia) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |samuel.mehrbrodt@allotropia |desktop.org |.de CC||samuel.mehrbrodt@allotropia ||.de Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153416] Some buttons are white-on-white on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153416 --- Comment #10 from Ken Shirriff --- Stéphane, I'm using light mode in macOS. I haven't done any customization of toolbars beyond maybe enabling some of them. The problem happens in Safe Mode too, which I think bypasses customization? Version information: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153402] English (en-us) Spellcheck overactive (acceptable spelling "briar" flagged as incorrect)
https://bugs.documentfoundation.org/show_bug.cgi?id=153402 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #2 from Aron Budea --- The right place for this report would probably be in the upstream issue tracker for the word list: https://github.com/en-wl/wordlist/issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153720] Bar chart: data stacks are showed in reverse order.
https://bugs.documentfoundation.org/show_bug.cgi?id=153720 --- Comment #5 from Stéphane Guillou (stragu) --- No worries, thanks for the quick follow-up :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39969] Applying formatting doesnt work correctly if cell contains multiple direct formatting sequences
https://bugs.documentfoundation.org/show_bug.cgi?id=39969 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3392 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108391] Editing: The text color of multiple cells can't be changed under specific conditions
https://bugs.documentfoundation.org/show_bug.cgi?id=108391 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3392 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108662] [META] Cells with multiple or partly direct formatted texts
https://bugs.documentfoundation.org/show_bug.cgi?id=108662 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153392 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153392 [Bug 153392] Font Name, Font Size and Font "Style" (Bold, Italic, Underline) changes applied to a column do not change all the content of selected cells. Ukrainian language/Cyrillic font -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153392] Font Name, Font Size and Font "Style" (Bold, Italic, Underline) changes applied to a column do not change all the content of selected cells. Ukrainian language/Cyrillic
https://bugs.documentfoundation.org/show_bug.cgi?id=153392 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Version|7.4.4.2 release |6.0.0.3 release CC||stephane.guillou@libreoffic ||e.org Blocks||108662 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=39 ||969, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||8391 Status|UNCONFIRMED |NEW --- Comment #4 from Stéphane Guillou (stragu) --- Reproduced in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b52117c0be97c45824d2897657084f8ac7e9bf42 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group I need to clear direct formatting before being able to change the formatting of whole selections. Otherwise, applying changes in formatting of multi-cell selection is very erratic and unpredictable in this file (no change to formatting, or change only in certain cells, or even applying a different change than the one clicked...) Saving as ODS and reloading does not fix the issue. This is very similar to what is described in bug 39969 and bug 108391. I also tested OOo 3.3, in which I can't format any cell or selection. At least the behaviour back then was consistent and not completely unpredictable. OpenOffice.org 3.3.0 OOO330m20 (Build:9567) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108662 [Bug 108662] [META] Cells with multiple or partly direct formatted texts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108391] Editing: The text color of multiple cells can't be changed under specific conditions
https://bugs.documentfoundation.org/show_bug.cgi?id=108391 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #5 from Stéphane Guillou (stragu) --- Reproducible in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b52117c0be97c45824d2897657084f8ac7e9bf42 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153485] Tooltip for H icon in Navigator should be "Outline Level"
https://bugs.documentfoundation.org/show_bug.cgi?id=153485 --- Comment #13 from sdc.bla...@youmail.dk --- (In reply to Rizal Muttaqin from comment #12)> > Look at how Karasa Jaga (this design was stolen from Galaxy) has better > representation here. Happy to see that I have reinvented the wheel. More importantly: perhaps you have a useful direction in which to go, and I will get out of your way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153769] New: error playing animations and transitions in libreoffice impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153769 Bug ID: 153769 Summary: error playing animations and transitions in libreoffice impress Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: maicoleduardofigue...@gmail.com Description: error playing animations and transitions in libreoffice impress. when launching the presentation in full or normal screen, there is an error that does not allow to play most of the animations or transitions 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 153401] Remove "COLUMN" from the Sort Key dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=153401 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- This has been implemented for LO 7.4, as a fix for bug 140290. You can use it straight away in our currently supported versions, 7.4 and 7.5. Thanks! *** This bug has been marked as a duplicate of bug 140290 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128795] FILEOPEN DOCX Rectangular gradient fill Center XY position imported/exported incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=128795 Gabor Kelemen (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3762 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153762] FILESAVE DOCX gradient direction and type is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=153762 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8795 --- Comment #3 from Gabor Kelemen (allotropia) --- Different fill rendering is likely bug 128795 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153402 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153402 [Bug 153402] English (en-us) Spellcheck overactive (acceptable spelling "briar" flagged as incorrect) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153402] English (en-us) Spellcheck overactive (acceptable spelling "briar" flagged as incorrect)
https://bugs.documentfoundation.org/show_bug.cgi?id=153402 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Blocks||108728 Component|UI |Linguistic Summary|English (en-us) Spellcheck |English (en-us) Spellcheck |overactive (acceptable |overactive (acceptable |spelling flagged as |spelling "briar" flagged as |incorrect) |incorrect) CC||k...@kevina.org, ||so...@libreoffice.org, ||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW --- Comment #1 from Stéphane Guillou (stragu) --- Thank you Tina! (and thanks for the kind words!) Confirming that it is not in the en_US dictionary: https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/en_US.dic It is however included in the en_GB dictionary: https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/en_GB.dic#n11133 I agree that it should probably be included: https://en.wiktionary.org/wiki/briar https://www.merriam-webster.com/dictionary/briar Kevin, what are you thoughts? I'm not familiar yet with how the dictionaries are compiled and augmented. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108728 [Bug 108728] [META] Dictionaries bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/outlinenumbering.ui | 50 ++--- 1 file changed, 45 insertions(+), 5 deletions(-) New commits: commit 74dc2ac66f0130bcd77cf1bbe417b22865beb067 Author: Seth Chaiklin AuthorDate: Sun Feb 19 03:17:45 2023 + Commit: Seth Chaiklin CommitDate: Mon Feb 20 21:44:44 2023 + tdf#153549 update extended tips for load/save numbering formats There was only an extended tip for the first item in the dropdown list, so extended tips were added to the 8 other items in the list. Change-Id: I29188637068ca683da0272b798d665cf5f8f22aa Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147275 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/sw/uiconfig/swriter/ui/outlinenumbering.ui b/sw/uiconfig/swriter/ui/outlinenumbering.ui index 99df7dcaaeef..228c762b32a1 100644 --- a/sw/uiconfig/swriter/ui/outlinenumbering.ui +++ b/sw/uiconfig/swriter/ui/outlinenumbering.ui @@ -13,7 +13,7 @@ True -Select the predefined numbering scheme that you want to assign to the selected outline level. +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. @@ -24,6 +24,11 @@ False Untitled 2 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -32,6 +37,11 @@ False Untitled 3 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -40,6 +50,11 @@ False Untitled 4 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -48,6 +63,11 @@ False Untitled 5 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -56,6 +76,11 @@ False Untitled 6 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -64,6 +89,11 @@ False Untitled 7 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -72,6 +102,11 @@ False Untitled 8 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -80,6 +115,11 @@ False Untitled 9 True + + +Select this predefined numbering format to be the numbering format for this document. It will overwrite the current settings. + + @@ -96,21 +136,21 @@ True -Opens a dialog where you can save the current settings for the selected chapter and outline level. You can then load these settings from another document. +Opens a dialog box where you enter a name to identify the current settings. The name you enter will appear in the dropdown list when the Load/Save button is clicked, both in the current and in other documents. Click on the name to load the saved settings into a document. -Click a numbering scheme in the list, and then enter a name for the scheme. The numbers correspond to the outline level that the styles are assigned to. +Click a numbering scheme in the list, and then enter a name for the scheme. The numbers correspond to the outline level of the styles. False 6 -Chapter Numbering +Heading Numbering False True 0 @@ -331,7 +371,7 @@ -Use this dialog to specify the numbering scheme for headings in the current document. For each outline level, you can assign a paragraph style and a numbering scheme. Use “1-10” to apply the same setting for all outline levels. +Use this dialog to specify the numbering format for headings in the current document. For each outline level, you can assign a paragraph style and a numbering scheme. Use “1-10” to apply the same setting for all
[Libreoffice-bugs] [Bug 153720] Bar chart: data stacks are showed in reverse order.
https://bugs.documentfoundation.org/show_bug.cgi?id=153720 --- Comment #4 from m.a.riosv --- Created attachment 185506 --> https://bugs.documentfoundation.org/attachment.cgi?id=185506=edit Sample file with bar chart Sorry, I have uploaded a wrong file, first time. Thanks, @Stéphane the option to reverse order on Y axes, solve the issue. I did not find it, when searching for a solution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153722] Review needed of style groups "Chapter Styles" and "Text Styles"
https://bugs.documentfoundation.org/show_bug.cgi?id=153722 --- Comment #3 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #2) > "Outline Styles" sounds reasonable considering the latest activities. "Outline" is ambiguous. I only use "outline level". > Alternatively "Document Structure" for all headings plus the current > "chapter style" "Document Structure" is good. The current grouping in Text Styles looks like an implementation error. Once the Headings are removed from Text Styles, the "logic" of what remains is clear enough. In sum, the request looks like: 1. Rename "Chapter Styles" to "Document Structure" 2. Move "Heading" and "Heading [1-10]" PS from "Text Styles" to "Document Structure" Maybe an EasyHack? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153722] Review needed of style groups "Chapter Styles" and "Text Styles"
https://bugs.documentfoundation.org/show_bug.cgi?id=153722 --- Comment #3 from sdc.bla...@youmail.dk --- (In reply to Heiko Tietze from comment #2) > "Outline Styles" sounds reasonable considering the latest activities. "Outline" is ambiguous. I only use "outline level". > Alternatively "Document Structure" for all headings plus the current > "chapter style" "Document Structure" is good. The current grouping in Text Styles looks like an implementation error. Once the Headings are removed from Text Styles, the "logic" of what remains is clear enough. In sum, the request looks like: 1. Rename "Chapter Styles" to "Document Structure" 2. Move "Heading" and "Heading [1-10]" PS from "Text Styles" to "Document Structure" Maybe an EasyHack? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87351] [META] Conditional formatting bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87351 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||153768 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153768 [Bug 153768] Conditional formatting does not have "Stop if true" option -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153768] New: Conditional formatting does not have "Stop if true" option
https://bugs.documentfoundation.org/show_bug.cgi?id=153768 Bug ID: 153768 Summary: Conditional formatting does not have "Stop if true" option Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 87351 Created attachment 185505 --> https://bugs.documentfoundation.org/attachment.cgi?id=185505=edit The Regional Sales sheet in Excel and Calc attachment 185496 from bug 153763 demonstrates the Excel Conditional formatting feature "Stop if true" on the "Regional sales" sheet. Calc does not have this feature, so it formats the cells differently. 1. Open attachment 185496 2. Go to the "Regional sales" sheet. -> Observe the green traffic lights applied to the B4:B11 range in Calc. In Excel the first rule has the "Stop if true" box checked so the second rule is not evaluated for the B4, B6, B8:B10 cells, since the first rule matched and this stops further CF rule evaluation. Calc evaluates the second rule as well and puts the appropriate icon set icons into the cells. Calc should implement this feature for better interoperability. Also it's a nice feature to have on its own :). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87351 [Bug 87351] [META] Conditional formatting bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 --- Comment #10 from V Stuart Foote --- (In reply to ady from comment #9) > I already have that setting modified in the OS. As a user, I set it in some > "balance" point, where I can read clearly _every_ aspect of the OS > interface. If I have to set it even bigger, just for the formula bar, it > would make some other places in my OS "too big" and it won't fit in the > place where it allows me to see the complete text (i.e. part of it will be > hidden by other artifacts). > Again, OP looks to have os/DE system at 100% -- too small. The Win10/Win11 Settings -> Display -> 'Make text bigger' control in the os/DE provides exactly the adjustment needed for this issue. Similar UI controls in macOS and the various Linux os/DEs. Not every adjustment must be in the LibreOffice UI, but there is room tweak the UI to use "other than os/DE system UI font" and also to extablish a different fontsize for the inputwin.hxx/.cxx of the 'Formula Bar' widget. Again this is => WFM, and the other BZ issues are already open for the "tweaks". -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 --- Comment #10 from V Stuart Foote --- (In reply to ady from comment #9) > I already have that setting modified in the OS. As a user, I set it in some > "balance" point, where I can read clearly _every_ aspect of the OS > interface. If I have to set it even bigger, just for the formula bar, it > would make some other places in my OS "too big" and it won't fit in the > place where it allows me to see the complete text (i.e. part of it will be > hidden by other artifacts). > Again, OP looks to have os/DE system at 100% -- too small. The Win10/Win11 Settings -> Display -> 'Make text bigger' control in the os/DE provides exactly the adjustment needed for this issue. Similar UI controls in macOS and the various Linux os/DEs. Not every adjustment must be in the LibreOffice UI, but there is room tweak the UI to use "other than os/DE system UI font" and also to extablish a different fontsize for the inputwin.hxx/.cxx of the 'Formula Bar' widget. Again this is => WFM, and the other BZ issues are already open for the "tweaks". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153744] Words found during a search in LibreOffice Writer hardly visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153744 arthur jackson changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153744] Words found during a search in LibreOffice Writer hardly visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153744 --- Comment #2 from arthur jackson --- Version information: Libre Office Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.6 Linux Mint 20.3 However, ... I've just checked the search function again for a screenshot, and the highlights are now quite clear - similar to the screenshot someone uploaded after saying they had the same problem as me. I have no idea what is going on but it seems solved. Sorry for the irrelevant bug request, I hope the problem doesn't reoccur. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108897] [META] XLSX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108897 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||153767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153767 [Bug 153767] FILEOPEN XLSX Boolean formula results not loaded, needs recalculation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153767] New: FILEOPEN XLSX Boolean formula results not loaded, needs recalculation
https://bugs.documentfoundation.org/show_bug.cgi?id=153767 Bug ID: 153767 Summary: FILEOPEN XLSX Boolean formula results not loaded, needs recalculation Product: LibreOffice Version: 6.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com CC: er...@redhat.com Blocks: 108897 Created attachment 185504 --> https://bugs.documentfoundation.org/attachment.cgi?id=185504=edit The Customers2 tab in Excel and Calc attachment 185496 from bug 153763 has the following formula on the Customers2 sheet in the H3:H20 range: =NOT(IF(G3>1;TRUE;FALSE)) When the file is loaded, all cells in the above range open with the value 0 instead of a series of TRUE/FALSE. 1. Open attachment 185496 2. Go to the Customers2 sheet 3. Observe that the H3:H20 range has the 0 values 4. Press F9 -> the values change to TRUE/FALSE according to the formula result. These match what Excel shows. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 16a35542aa07ed69c6c699d1c17f076d87708958 CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Started in 6.2 with: https://git.libreoffice.org/core/+/bd3baf8dab6c5b8865a33136cc28a016e6ee6afb author Eike Rathke Tue Jul 17 12:58:30 2018 +0200 committer Eike Rathke Tue Jul 17 17:19:13 2018 +0200 OOXML import: CalcFormulaTree() is unnecessary, tdf#94925 follow-up Adding CC to: Eike Rathke Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108897 [Bug 108897] [META] XLSX (OOXML) bug tracker -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104524] [META] DOCX (OOXML) Table of Contents (ToC) and Index related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104524 Bug 104524 depends on bug 153090, which changed state. Bug 153090 Summary: FILEOPEN DOCX TOF incorrect when based on para style instead of category https://bugs.documentfoundation.org/show_bug.cgi?id=153090 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
