Created attachment 52567 [details]
PrintPreview1 with zoom buttons and scaling factor widget circled
In the attached "PrintPreview1", I claim that the "scaling factor" slider widget (circle (1)) is not visually clear as to it's purpose.
I originally clicked on the buttons expecting the behavior one gets when clicking the +/- buttons in circle (2). When I did not get the desired visual appeal, I thought again that maybe I was messing with the margins. It finally dawned on me what it was doing (see "PrintPreview2", but it took me more than a few seconds to kick myself from my preconceived notions.
I submit that this could/should be made more visually explicit before 3.5. Unfortunately, I'm not a UI guy or I'd offer a suggestion.
This may apply to other LO components as well, but I was using Calc when I noted it.
This screenshots were made with master. Last pulled commit:
$ git log -1 --format=oneline 5ad4d151dac1eb887d92200330e31af269d8d1fd migrate to StringRangeEnumerator in pdfexport
Created attachment 52568 [details]
PrintPreview2 with scaling factor widget utilized
Not a particular Master problem, I also see it with LibO 3.3.3 Portable. Behavior is inherited from OOo, I also see it with OOo 3.1.1
No idea for what that is needed
- we have a zoom slider in the status bar
- no help available (see Bug 42081 - LOCALHELP for CALC
Page Preview Bar incomplete)
I can't find out any purpose for what that slider might be useful.
Please add findings to Help (also see "Bug 42081 - LOCALHELP for CALC Page Preview Bar incomplete").
Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (184.108.40.206 or later): https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
Thank you for your help!
-- The LibreOffice QA Team
This NEW Message was generated on: 2015-02-19
Confirmed it's still the same in Calc. Giving to the design team.
Win 7 Pro 64-bit, LibO Version: 220.127.116.11
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Ubuntu 14.10 64-bit
Build ID: 40m0(Build:2)
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
Zoom (2) works similar to ctrl+wheel or the statusbar slider - it zooms into the document. The slider (1) scales the content, meaning you get more columns on one page with "-" or enlarge the font with "+".
The interaction has a clear feedback but the UI is missing a label "Scale" before the slider. The usability would also benefit from showing the actual scaling factor and when +/- steps become more discrete.
Sounds like an easyhack.
The scale slider is handled in sc/source/ui/cctrl/tbzoomsliderctrl.cxx with a constant nSliderXOffset to both left and right that should be changed into an asymmetric offset to allow the output of 'Scale' before the slider, and perhaps also the current value right of it.
Hi!I would like to work on this bug.
(In reply to Heiko Tietze from comment #7)
> The interaction has a clear feedback but the UI is missing a label "Scale"
> before the slider. The usability would also benefit from showing the actual
> scaling factor and when +/- steps become more discrete.
As I understand,I need to create label before slider and its actual value on right side in previewbar .
(In reply to Kshitij from comment #9)
> As I understand,I need to create label before slider and its actual value on
> right side in previewbar .
Exactly, there should be a translatable caption with the slider. I would also like to have the actual value on the other side. And when you touch the code and find an option to increase the steps when the user clicks on + or - that would be great. Sounds like we ideally go with a standard control, if there is one.
But having just a caption on the left side is fine at the moment.
I have submitted the patch https://gerrit.libreoffice.org/#/c/49204/ with both caption and actual valuein right.@Heiko can you please review that :)
(In reply to Kshitij from comment #11)
> @Heiko can you please review that :)
Done on Gerrit.
A polite ping, still working on this bug?
Yes ,working on it :)
It's been 1,076 days since the assignee has responded. Marking as New.
(In reply to Luke from comment #26)
> It's been 1,076 days since the assignee has responded. Marking as New.
Hi Luke, you have got the assignees mixed up. I am a new assignee with a patch at https://gerrit.libreoffice.org/c/core/+/110960 awaiting review. Marking as Assigned.
Dear George Bateman,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.