View Issue Details

IDProjectCategoryView StatusLast Update
0013197ScribusUsabilitypublic2015-08-29 22:27
Reporterale Assigned Tojghali  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product Version1.5.1svn 
Fixed in Version1.5.1svn 
Summary0013197: in file > new, "chaining" should make all values equal
Descriptionin "file > new" chaining the margins or the bleeds (making them all the same) should modify the other values and set them to the active value.

currently, scribus does only modify the other values on blur.

the chain icon, might also deserve a short tooltip...
TagsNo tags attached.
PatchNo

Relationships

related to 0013321 closedFirasH Add tooltip for chain icon in File > New 
related to 0013320 closedjghali Wrong tooltips in File > Preferences > "Margins & Bleeds" 

Activities

simonaw

2015-07-01 23:18

reporter   ~0035610

In this case it is (imo) desired behaviour as the input widgets are ScrSpinBoxes which inherit from QDoubleSpinBox. In the "New" dialog the signal "valueChanged" is used that gets emitted only when the editing process is finished, i.e. either the spin-buttons (up/down-arrows) are pressed or the widget has lost its focus. AFAIK there is no textEdited or textChanged signal like in QLineEdit.

Sure, we can start handling keyboard key presses in ScrSpinBox. But do we really want that?

ale

2015-07-02 18:34

manager   ~0035633

mmm, simon, not sure i understand your comment.

again, what i would like to see (or, better, what a user was expecting and i agreed that it was a good idea):
- change the top margin to 1cm
- press the chain
- all other values change to 1cm

this is what currently happens:
- change the top margin to 1cm
- press the chain
- all other values do not change
- press tab to get out of the top margin field (or click into another field) and all fields becom 1cm.

i can live with that, but i understand why she was feeling uncomfortable with it!

cbradney

2015-07-02 21:21

administrator   ~0035640

Perfect like it is, resolving. Won't fix.

ale

2015-07-03 08:34

manager   ~0035651

craig, for people who are very comfortable with their computer, this is for sure ok. maybe not perfect, but ok.

but not for people who are a bit more hesitant.

even to me it feels odd. even if i could live with this for years!

and in scribus itself, most if not all of the other chain buttons modify the values when they are clicked.
try it out. you'll feel the difference!

the ones in the file > new dialog are the only ones that i found that don't do it (otherwise i would have made a ticket for generally asking for such a change, not only for the file > new dialog)

at the last workshop i did, several people (who are already using indesign) were puzzling at how to get all the same to be the same.
many people are not used to navigate the fields with the tab key: they are stuck with a value that does not change even if they press the chain button multiple times.

simonaw

2015-07-03 11:12

reporter   ~0035654

@ale Ah, now I see it. If you don't leave the spin box (focus) and press the link button immediately after entering text, valueChanged is not emitted and the other values don't get sync'd.

@cbradney Isn't possible to just emit valueChanged of the spin box that has focus when enabling link?

Kunda

2015-07-09 12:49

updater   ~0035710

Last edited: 2015-07-10 01:18

Jghali committed fix in r20236
Couple of things:

1) It works but only 1 time. If you try to reproduce the effect it reverts to the old behavior where you need 2 clicks.
For example,
change 'Left Margin' from 40pt to 3 pt <click chain>
results: all fields change to 3 pt.
Now change 'Left Margin' back to 40 pt <click chain> result no change
Again <click chain> result: all margins back to 40 pt


2) The <click chain> only responds to edits made in the 'Left Margin'. I can't get the behavior in any of the other margins.

EDIT: 10.10.3 r20240

jghali

2015-07-09 13:00

administrator   ~0035711

1) is invalid as the second click on chain invalidates the value link. This is expected behavior.

Kunda

2015-07-10 00:58

updater   ~0035731

Last edited: 2015-07-10 00:59

2) has been fixed in r20241

New bug:
change 'Left Margin' from 40pt to 3 pt <click chain>
results: all fields change to 3 pt.
Now change 'right Margin' back to 40 pt <click chain> result no change
Again <click chain> result: all margins back to 3 pt instead of 40pt

jghali

2015-07-10 06:56

administrator   ~0035732

Last edited: 2015-07-10 07:02

Not a bug. Second click on chain, *cancel* the link. As the spinbox widgets have lost the focus, there is no way to tell from which widget the value should come from. So the value is taken by default from "Left" spinbox.

Kunda

2015-07-10 12:06

updater   ~0035736

Interesting. Ok. Then all that is left is a tooltip for the chain icon.
Not sure how to word that

Kunda

2015-08-28 01:26

updater   ~0036111

Reminder sent to: FirasH

Can you make a tooltip for the chain icon ?

FirasH

2015-08-29 22:07

developer   ~0036118

Patch for tooltips uploaded.

jghali

2015-08-29 22:16

administrator   ~0036119

Last edited: 2015-08-29 22:17

This patch is out of subject in regards of this issue. Please create proper issue.

Kunda

2015-08-29 22:27

updater   ~0036120

Firash created new issue in 0013321.
Closing this issue. Thanks for all the work fellas!

Issue History

Date Modified Username Field Change
2015-07-01 19:58 ale New Issue
2015-07-01 23:18 simonaw Note Added: 0035610
2015-07-02 18:34 ale Note Added: 0035633
2015-07-02 21:21 cbradney Note Added: 0035640
2015-07-02 21:21 cbradney Status new => resolved
2015-07-02 21:21 cbradney Resolution open => won't fix
2015-07-02 21:21 cbradney Assigned To => cbradney
2015-07-03 08:34 ale Assigned To cbradney =>
2015-07-03 08:34 ale Note Added: 0035651
2015-07-03 08:34 ale Status resolved => feedback
2015-07-03 08:34 ale Resolution won't fix => reopened
2015-07-03 08:34 ale Status feedback => new
2015-07-03 11:12 simonaw Note Added: 0035654
2015-07-07 23:16 jghali Status new => resolved
2015-07-07 23:16 jghali Fixed in Version => 1.5.1svn
2015-07-07 23:16 jghali Resolution reopened => fixed
2015-07-07 23:16 jghali Assigned To => jghali
2015-07-09 12:49 Kunda Note Added: 0035710
2015-07-09 12:49 Kunda Status resolved => feedback
2015-07-09 12:49 Kunda Resolution fixed => reopened
2015-07-09 12:50 Kunda Note Edited: 0035710
2015-07-09 12:50 Kunda Note Edited: 0035710
2015-07-09 13:00 jghali Note Added: 0035711
2015-07-09 20:20 jghali Status feedback => resolved
2015-07-09 20:20 jghali Resolution reopened => fixed
2015-07-10 00:58 Kunda Note Added: 0035731
2015-07-10 00:59 Kunda Status resolved => feedback
2015-07-10 00:59 Kunda Resolution fixed => reopened
2015-07-10 00:59 Kunda Note Edited: 0035731
2015-07-10 01:18 Kunda Note Edited: 0035710
2015-07-10 06:56 jghali Note Added: 0035732
2015-07-10 06:56 jghali Status feedback => resolved
2015-07-10 06:56 jghali Resolution reopened => fixed
2015-07-10 07:02 jghali Note Edited: 0035732
2015-07-10 12:06 Kunda Note Added: 0035736
2015-08-28 01:26 Kunda Note Added: 0036111
2015-08-29 21:55 Kunda Relationship added related to 0013320
2015-08-29 22:07 FirasH File Added: 13197-Patch.diff
2015-08-29 22:07 FirasH Note Added: 0036118
2015-08-29 22:09 Kunda Status resolved => assigned
2015-08-29 22:16 jghali Note Added: 0036119
2015-08-29 22:16 jghali Status assigned => resolved
2015-08-29 22:17 jghali Note Edited: 0036119
2015-08-29 22:24 FirasH Issue cloned: 0013321
2015-08-29 22:26 Kunda Relationship added related to 0013321
2015-08-29 22:27 Kunda Note Added: 0036120
2015-08-29 22:27 Kunda Status resolved => closed
2015-08-29 22:27 Kunda File Deleted: 13197-Patch.diff