Mantis Issue Tracking for Scribus
· Hosting provided by Anduin.net / Øverby Consulting ·

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010171ScribusUsabilitypublic11-Aug-10 15:1814-Jul-02 03:56
ReporterVladimir Savic 
Assigned ToChelen 
PrioritynormalSeveritytweakReproducibilityalways
StatusassignedResolutionopen 
PlatformLinuxOSUbuntuOS Version11.04
Product Version1.5.0svn 
Target Version1.6 milestoneFixed in Version 
Summary0010171: Default zoom stepping to big
DescriptionIt would be much easier on user if ctrl+mouse wheel zooming goes by 25% (bigger or smaller then current)
TagsNo tags attached.
Attached Files

- Relationships
related to 0012195new more progressive unzoom when < 100% 
related to 0010978closedChelen [PATCH] Snap to Item functionnality and other features 

-  Notes
(0026699)
ale (manager)
11-Aug-10 17:38

while discussing with vlada about this, we thought that it would be better to have absolute instead of relative zoom increments.

by 125% now we have:
100 125 156.25 195.31 244.14 305.18 ...

i think it would be better to have:
100 125 150 175 200 225 250 275 300 ...

while zooming in, there are no problems...

when zooming out, i wonder if 100 75 50 25 is ok...

maybe, we should keep the relative zooming when the factor goes under the minimum step (so after 25% you would have 75%(25) and so on...
(this should also be done when scaling up from a factor which is smaller than the step, until the value of the step is reached).


ah, and 125% would be a better default than 200%... if we can't get absolute ratios :-)
(0028582)
greyscale (reporter)
12-Jul-23 22:51

Indeed, the 200% default is way too massive, 125% is much more useful. I am sure that many users don't know they can change this in the preferences. I only noticed it after a search here in the bugtracker. So it's certainly important to have the most usable default setting!

Just for reference, in another popular layout app, the default steps for zooming in are 100 125 150 200 300 400, and for zooming out 100 75 50 25 12,5 5 ... It's pretty usable, but I think what Ale proposes (with more increments) is even better!

Generally when creating layouts, I think that the extreme values are not often used, it's the area between 50 - 250% where the action mostly occurs. So that's where we need a sufficient number of increments, so that we can navigate the interface quickly and smoothly.

PS: in Scribus 1.4.1 (Mac and Linux), changing the value doesn't take effect immediately in the currently opened document - only after closing/reopening.
(0028603)
greyscale (reporter)
12-Jul-25 11:34
edited on: 12-Jul-25 11:47

Actually the behavior when changing the zoom preferences in Scribus 1.4.1 is a bit confusing:

Changed prefences will apply only to *newly* created documents, but all existing files will stick to the zoom preference they were created with (i.e. mostly 200%).

If we want to change the setting for an existing document, we need to go into Document Setup, and change it there.

I think this is not the optimal way: generally, I expect that changes I make in the preferences pane will apply to the *currently opened file*. Specially if it's a setting that affects the general Scribus interface, rather than the file.

Or to put it differently: it doesn't seem very logical that each document has it's own private zoom preference that is unaffected by the application preferences. My impression is that by default, every document should apply the zoom setting that is defined in the application preferences.

If I decide to switch to 125%, I don't want to update this value manually in every Scribus file I ever created ...

(0028617)
Chelen (developer)
12-Jul-25 14:42

In fact, this is a file modification. If you change the value for one file, when you reopen this one, you will have the saved value.
However, I fix the issue : if no preference are set on the file, you will have a default 125% value.
(0028657)
ale (manager)
12-Jul-26 22:43

i think that greyscale is right, it does not make sense to store the settings for the zoom steps in the document setting.

all the three settings in the zoom tab of the preferences should only be defined in the preferences and not in the document settings.

and future versions of scribus should simply ignore the values that are written in .sla (if any)
(0028732)
ale (manager)
12-Aug-02 14:01
edited on: 12-Aug-02 14:05

what about having a list of values?
and when you get out of the defined values you get the step between the last and the one before?
so a simple list would be:
40,50,100,200,400
which gives
1 (rounded up?), 10, 20, 30, 40, 50, 100, 200, 400, 600, 800, 1000, 1200, ...

also i wonder what should happen when scrolling up/down from 23%. personally, i'd like to see 30 (in the case of the list above) when scrolling up and 20% when scrolling down. not 33% or 13%...

p.s.: avox suggests the list that would support the values 50, 75, 80, 90 100, 110, 125, 150

(0028733)
ale (manager)
12-Aug-02 14:05

imo, one further important question is if we want the user to be able to define how the zoom behaves or if it's defined by the program.
(0031641)
JLuc (updater)
14-Apr-07 17:19

see also 0012195

- Issue History
Date Modified Username Field Change
11-Aug-10 15:18 Vladimir Savic New Issue
11-Aug-10 17:38 ale Note Added: 0026699
12-Jul-23 22:51 greyscale Note Added: 0028582
12-Jul-25 11:34 greyscale Note Added: 0028603
12-Jul-25 11:44 greyscale Note Edited: 0028603 View Revisions
12-Jul-25 11:47 greyscale Note Edited: 0028603 View Revisions
12-Jul-25 14:39 Chelen Assigned To => Chelen
12-Jul-25 14:39 Chelen Status new => assigned
12-Jul-25 14:42 Chelen Note Added: 0028617
12-Jul-26 22:43 ale Note Added: 0028657
12-Jul-31 21:31 cbradney Relationship added related to 0010978
12-Aug-02 14:01 ale Note Added: 0028732
12-Aug-02 14:05 ale Note Added: 0028733
12-Aug-02 14:05 ale Note Edited: 0028732 View Revisions
14-Apr-07 17:19 JLuc Note Added: 0031641
14-Jul-02 03:54 Kunda Relationship added related to 0012195
14-Jul-02 03:56 Kunda Target Version => 1.6 milestone



Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker