[Libreoffice-ux-advise] [Bug 141625] Calc Chart x-Axis Formatting

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.4.0

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 141625] Calc Chart x-Axis Formatting

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

--- Comment #5 from Commit Notification 
 ---
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/c15fceae5e70483daf8355a9b7d53215b7643c2b

Resolves: tdf#141625 give enough space to see full date+time

It will be available in 7.4.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 141625] Calc Chart x-Axis Formatting

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

Caolán McNamara  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Caolán McNamara  ---
done in trunk, backport to 7-3 in gerrit

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 141625] Calc Chart x-Axis Formatting

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.4.0|target:7.4.0 target:7.3.4

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 141625] Calc Chart x-Axis Formatting

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141625

--- Comment #7 from Commit Notification 
 ---
Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-7-3":

https://git.libreoffice.org/core/commit/5d9ba65897d2ba2998e43e97b25dbb9a560a16a1

Resolves: tdf#141625 give enough space to see full date+time

It will be available in 7.3.4.

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 on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148591] Rename "page text area top" and "page text area bottom" to "Above (or Below) page text area

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148591

sdc.bla...@youmail.dk changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||8485
 Blocks||108741
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108741
[Bug 108741] [META] Shapes bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148513] Poor nomenclature for Manual Break

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148513

--- Comment #15 from Heiko Tietze  ---
(In reply to sdc.blanco from comment #14)
Don't get the difference between "After all objects" and "After all objects *"
from reading the options. Sounds like "superordinate object".

Would go with a shorter "Left/Right after object" and defer to the (online)
help.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147943] MASTER DOCUMENT: Allow to customize numbering formats of subdocuments when creating Master Document with File -> Send

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147943

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||mentoring@documentfoundatio
   ||n.org
   Keywords|needsUXEval |difficultyBeginner,
   ||easyHack, skillCpp, topicUI

--- Comment #8 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input. Let's change the default to have at least two digits at the beginning
followed by an underscore.

Code pointer: sw/source/uibase/app/docsh2.cxx #1030 (SwDocShell::Execute() case
FN_NEW_GLOBAL_DOC)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 141380] FILEOPEN (csv import): Allow resizing of preview columns

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141380

Heiko Tietze  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input. Little benefit (not much to scale) comes with huge effort (complete
interaction needed) and I recommend to keep the current preview simple.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148349] Use attention-attracting cue when pressing Ctrl+F while in the find bar

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148349

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |caol...@redhat.com,
   |.freedesktop.org|heiko.tietze@documentfounda
   ||tion.org
 Blocks||108743
 Status|UNCONFIRMED |NEW
   Keywords|needsUXEval |
 Ever confirmed|0   |1

--- Comment #4 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input. 

Could imagine some default similar to set_message_type(). Caolan, any idea?

If not let's change the border color to the highlight color and fade out within
500 ms.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108743
[Bug 108743] [META] Find toolbar bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 140787] Introduce an option for cell formatting on protected sheets

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140787

Heiko Tietze  changed:

   What|Removed |Added

   Keywords|needsUXEval |
Summary|New features Request:Allows |Introduce an option for
   |to paint color cells while  |cell formatting on
   |protecting the sheet.   |protected sheets
 Status|UNCONFIRMED |NEW
 Blocks||107450
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
 Ever confirmed|0   |1

--- Comment #4 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input.

Let's add the option at the protection dialog to change cell attributes except
number format as other cells may depend on it.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107450
[Bug 107450] [META] Cell and sheet protection bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 139954] Improve labels for [M] and [T] in AutoCorrect Options tab and add labels in Localized Options tab

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139954

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||vstuart.fo...@utsa.edu
   Keywords|needsUXEval |needsDevAdvice
  Component|LibreOffice |Writer

--- Comment #3 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input.

Short labels make sense but having better tooltips would be good. Guess [M]
means to finish editing with a white-space or return. But not sure =>
needsDevAdvice

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148272] Cross-reference to numbering wrongly includes separator character

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148272

Dieter  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

--- Comment #4 from Dieter  ---
So lets ask Design-Team

cc: Design-Team

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 139953] [rfe]: Tools > AutoCorrect > Apply and Edit Changes - drop first dialog go directly to Edit

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139953

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||mentoring@documentfoundatio
   ||n.org
   Keywords|needsUXEval |difficultyBeginner,
   ||easyHack, skillCpp, topicUI
  Component|LibreOffice |Writer
 Status|UNCONFIRMED |NEW

--- Comment #6 from Heiko Tietze  ---
Topic was on the agenda for the design meeting but didn't receive further
input.

I agree with the idea, let's do it.

Code pointer:
sw/source/uibase/shells/textsh1.cxx: 
* switch (lcl_AskRedlineFlags(GetView().GetFrameWeld()))...
* static short lcl_AskRedlineFlags(weld::Window *pWin)
sw/uiconfig/swriter/ui/queryredlinedialog.ui
sw/UIConfig_swriter.mk

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

sdc.bla...@youmail.dk changed:

   What|Removed |Added

Summary|"Left page border" and  |"Left page border" and
   |"right page border" options |"right page border" options
   |in Position and Size for|for Horizontal "to"
   |shapes are misleading   |position in Position and
   |names, which should be  |Size for shapes are
   |changed |misleading names, which
   ||should be changed
   Keywords||needsUXEval
 Blocks||108741
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108741
[Bug 108741] [META] Shapes bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148513] Poor nomenclature for Manual Break

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148513

--- Comment #16 from sdc.bla...@youmail.dk ---
(In reply to Heiko Tietze from comment #15)
> Don't get the difference between "After all objects" and "After all objects
> *" from reading the options.
Yet another Eve user who expects immediate understanding from words alone. ;-)

Please try the following.  Open the attachment.  Place the cursor on the word
"law" or "nervously" (you will find them between the two trapezoids).

Then make line breaks from that word using:

(Next Full Line)After all objects
 (Right)After all objects to right of cursor
  (Left)After all objects to left of cursor

And maybe also try with the word "pulled" in the upper right corner.

I would strongly encourage you, before hitting OK each time, to predict where
the line break will appear. 

After that experience, it should be easier to discuss the situation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

Heiko Tietze  changed:

   What|Removed |Added

 CC||mikekagan...@hotmail.com,
   ||rb.hensc...@t-online.de

--- Comment #1 from Heiko Tietze  ---
[Left] of [Left page border] sounds good to me and while [Right] of [Left page
border] is a bit weird it works well for [Right] of [Right page border]. This
*region to* is confusing. Perhaps page margin instead of border? But is this
really needed?

Regina, Mike, your take?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148513] Poor nomenclature for Manual Break

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148513

--- Comment #17 from Heiko Tietze  ---
(In reply to sdc.blanco from comment #16)
> (In reply to Heiko Tietze from comment #15)
> > Don't get the difference ... from reading the options.

> Please try the following. ... before hitting OK each time

It's "Save Changes" :-).

My comment was based on the idea to understand a function from reading the
label and the fact that your proposal is quite long. As always, no need to
follow my input. What you do is usually well thought out and I just add ideas
for consideration.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

--- Comment #2 from Mike Kaganski  ---
It is called *margin*, set up in page style; and the preview in the dialog
provides enough context to describe the idea.

I'd just replaced "border" (definitely wrong) with "margin" everywhere, and be
done.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148272] Cross-reference to numbering wrongly includes separator character

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148272

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||2555

--- Comment #5 from Heiko Tietze  ---
Same discussion recently in bug 142555 was decided WONTFIX since you have the
choice of Number or Chapter.

*** This bug has been marked as a duplicate of bug 142555 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148591] Rename "page text area top" and "page text area bottom" to "Above (or Below) page text area

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148591

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||8593
 Ever confirmed|0   |1

--- Comment #2 from Heiko Tietze  ---
If we use Margin as suggested on bug 148593 it would apply here as well. Would
"Top/Bottom page margin" work given we use "Left/right page margin"?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

Heiko Tietze  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||8591

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148417] Change "X" icon in Print Preview to "X Close Preview" (like in Writer)

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148417

Heiko Tietze  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||mentoring@documentfoundatio
   ||n.org
   Keywords|needsUXEval |difficultyBeginner,
   ||easyHack, skillDesign,
   ||topicDesign

--- Comment #3 from Heiko Tietze  ---
(In reply to sdc.blanco from comment #2)
> Polite ping to check if this ticket should be registered as an EasyHack.

Sure, it qualifies as easyhack. Code pointer in c0.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

--- Comment #3 from sdc.bla...@youmail.dk ---
(In reply to Mike Kaganski from comment #2)
> I'd just replaced "border" (definitely wrong) with "margin" everywhere, and
> be done.
It would be wrong.  Your statement is true only if there is no padding in the
page style.  See page 2 of attachment for illustration of what happens when
there is padding.

These controls seem to function (for the left and right sides of page text
area) as "page text area top" and "page text area bottom" function for the
regions above and below the page text area.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148591] Rename "page text area top" and "page text area bottom" to "Above (or Below) page text area

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148591

--- Comment #3 from sdc.bla...@youmail.dk ---
(In reply to Heiko Tietze from comment #2)
> If we use Margin as suggested on bug 148593 
As explained in bug 148593 comment 3, that suggestion is wrong. 

But, as implied in comment 3, definitely a good idea to try to get fairly
consistent, common terminology for all four of these options.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

--- Comment #4 from Mike Kaganski  ---
(In reply to sdc.blanco from comment #3)
> It would be wrong.  Your statement is true only if there is no padding in
> the page style.  See page 2 of attachment for illustration of what happens
> when there is padding.

Oh! You are absolutely correct. Thanks - I missed the second page completely!

No suggestion from me - the bulky suggestion in comment 0 looks technically
correct.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148463] Need ability to search only comments

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148463

stragu  changed:

   What|Removed |Added

 Blocks||106179


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106179
[Bug 106179] [META] Writer comment bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148513] Poor nomenclature for Manual Break

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148513

--- Comment #18 from sdc.bla...@youmail.dk ---
(In reply to Heiko Tietze from comment #17)
> It's "Save Changes" :-).
I take this to mean that you have come to appreciate that the behavior of the
line breaks is complex. 

It might be an advantage to have accurate descriptions, even if a bit long and
not fully obvious from reading alone, because once you understand the "logic"
of the breaks, then I believe my proposal gives the right "memory cue" to be
able to predict/remember accurately what will happen. (should also make it
easier to write accurate help pages)

Will wait to hear from others, especially from OP...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148591] Rename "page text area top" and "page text area bottom" to "Above (or Below) page text area

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148591

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Blocks||148485


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148485
[Bug 148485] four options missing in "Position > Vertical > to" section for
Position and Size tab for Shape
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 148593] "Left page border" and "right page border" options for Horizontal "to" position in Position and Size for shapes are misleading names, which should be changed

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=148593

--- Comment #5 from Regina Henschel  ---
(In reply to Heiko Tietze from comment #1)
> [Left] of [Left page border] sounds good to me and while [Right] of [Left
> page border] is a bit weird it works well for [Right] of [Right page
> border]. This *region to* is confusing. Perhaps page margin instead of
> border? But is this really needed?
> 
> Regina, Mike, your take?

The wording should neither contain "Margin" nor "Border". The region in
question is "page margin area" plus "page border area" plus "page padding
area". Thereby "margin", "border" and "padding" are used as defined in CSS, see
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Box_Model/Introduction_to_the_CSS_box_model
or https://drafts.csswg.org/css-box/#box-model.

It could be named
page region left of page content area

But that is too long for the drop-down list.

You need "page" in the item, because you have regions related to paragraphs in
the same list.

Perhaps a total different concept is needed, for example a large preview, which
has place enough to show the regions in question and has for each region an
identifier that can be used in the list.

The paragraph related items have the same wording problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147948] Visual improvements in LibreOffice - Mockups - "revolutionary, good, simple" ideas

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147948

--- Comment #22 from Yeron 50201  ---
1. Here it shows a minimal menu in textedit in mac-os - you can see in the
youtube video: "Using TextEdit For Casual Word Processing (MacMost Now 379)" -
https://www.youtube.com/watch?v=UNCo4Jvs5Ys
2. this video references the idea I mentioned here of having a minimal menu

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147948] Visual improvements in LibreOffice - Mockups - "revolutionary, good, simple" ideas

2022-04-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147948

--- Comment #23 from Yeron 50201  ---
Created attachment 179570
  --> https://bugs.documentfoundation.org/attachment.cgi?id=179570&action=edit
minimal_menu

new image minimal menu

-- 
You are receiving this mail because:
You are on the CC list for the bug.