Scaling problems with "farthest opposite node"

Bug #165799 reported by Buliabyak-users
2
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Medium
Dvlierop2

Bug Description

I'm assigning high priority to this because it must be
fixed before 0.39:

The new "scale origin" option does not quite work. The
"outermost point" mode works, but the "bounding box"
mode does not.
Turn on box selection cue, zoom in and draw a small
rect with thick
stroke. Now when I drag the right handle, the left edge
of the rect
also moves a bit in the same direction. It must stay
unmoved in that
mode.

Better names for the options are:
- Opposite bounding box edge
- Farthest opposite node [not point]

Additionally the bbox option does not sit well with the
"scale
stroke" option. When I don't want to scale stroke, i.e.
use a
compensation after scaling, that compensation moves the
bbox of the
object even farther away from the original position,
making the bug in
2. above worse. This mode must check the value of the
"scale stroke"
option and take it into account.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Since this also did not work in 0.38, I guess we can lower
priority somewhat.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Not likely to be fixed even for 0.40. Lowering.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

I fixed the bbox option - but now the farthest node option
seems to be broken instead :)

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: YES

Diederik: assigning this to you, hopefully we'll be able to close this
when this option is removed :)

Revision history for this message
Dvlierop2 (dvlierop2) wrote :

Originator: NO

While I was working on the selector tool this weekend, I got a bit too
reckless in shuffling code around. I'll have too undo some stuff to bring
it back to a working state, but after that this bug will be fixed I hope.
The origin option can then finally be removed, together with the "snap to
nodes" / "snap bbox" option. I'll get back to you on this soon.

I saw that you made the snap sensitivity independent of zoom. That makes
much more sense! I was already planning on creating a feature request for
that :-). It's not important at all, but maybe you should add the units for
this measure? It's measured in screen pixels, but that's not stated
anywhere. I guess the yellow pop-up box would be usefull for that.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: YES

> While I was working on the selector tool this weekend, I got a bit too
reckless in shuffling code around. I'll have too undo some stuff to bring
it back to a working state, but after that this bug will be fixed I hope.
The origin option can then finally be removed, together with the "snap to
nodes" / "snap bbox" option. I'll get back to you on this soon.

Great, thanks!

> I saw that you made the snap sensitivity independent of zoom. That
makes
much more sense! I was already planning on creating a feature request for
that :-). It's not important at all, but maybe you should add the units
for
this measure? It's measured in screen pixels, but that's not stated
anywhere. I guess the yellow pop-up box would be usefull for that.

The yellow pop-up box is called a tooltip, and it already tells you about
units: "Snapping distance, in screen pixels, for snapping to grid"

Revision history for this message
Dvlierop2 (dvlierop2) wrote :

Originator: NO

> The yellow pop-up box is called a tooltip, and it already tells you
about
units: "Snapping distance, in screen pixels, for snapping to grid"

While I was writing this comment I did check whether the units were
mentioned in the tooltip, but I forgot that at work (were I'm now) I'm
still using an old build :-(.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: YES

happily closing as no longer relevant

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.