Open GoogleCodeExporter opened 9 years ago
I can not reproduce this in 2.5 1572 in either chrome or firefox. Could it be
that
some of the changes you made related to Issue 514 are indirectly causing this?
Original comment by wschleter
on 24 May 2010 at 4:04
I am doing this on the latest trunk builds both on my server and the one hosted
on
google. I can reproduce this problem each and every time on firefox, opera,
and
chrome. Resize text like 3-4 times as much. rotate it. and then try moving
it. The
text object will hop.
Original comment by anas.has...@gmail.com
on 25 May 2010 at 2:40
Yeah, this is basically like Issue 472. I'd "fixed" it for most conditions, but
I
guess this one still remains. Will see if I can "fix" it too.
I put "fix" in quotes as I actually bypassed the original formula when simply
selecting/moving elements. I'd prefer it if a real fix could be found, but
that's a
bit beyond my realm of expertise.
Original comment by adeve...@gmail.com
on 25 May 2010 at 1:19
Oh, and I think it only occurs on angles > 90, which may be why wschleter
couldn't
see it.
Original comment by adeve...@gmail.com
on 25 May 2010 at 1:29
It occurs on all angles. Even if its only 1 degree. And programmatically, it
makes
no exception based on the angle. Only two conditions have to be met: the
object is
resized by a matrix and the object is rotated.
There is a problem with disabling function recalculateDimensions after a move
event.
The purpose of the function is to merge the translate item in a transform
attribute
during a mouseup event to the matrix item (I think its either matrix or x & y).
At
the same time, to recalculate coordinates of the rotate item.
If you cannot solve this puzzle, I will give it another try when I am more
awake. I
know of the solution but it just cannot come to my head right now.
Original comment by anas.has...@gmail.com
on 25 May 2010 at 6:09
Is it a regression?
Original comment by codedr...@gmail.com
on 25 May 2010 at 7:02
I don't think it is a regression. It seems to be that the rotate center is
incorrectly
calculated. This calculation happens during a SELECT of the object and a
TRANSLATE of
the object. Weirdly, the text hops back to its normal position during either a
rotate
command or a bold/italic command.
I am attaching a patch for svgcanvas.js that will fix this. This time I tried
removing
majority of the whitespace changes, but some were still stubbornly left.
Original comment by anas.has...@gmail.com
on 3 Jun 2010 at 2:25
Attachments:
[deleted comment]
Hi,
I submitted the patch you see above. I was not able to submit it using SVN. I
don't think I am admitted as commiter. Can you apply the patch to the trunk of
the project? Thanks.
Original comment by anas.has...@gmail.com
on 10 Jun 2010 at 3:30
I tried applying your patch, but it seems to basically undo the solution I came
up with for Issue 472. Let me see if I can find a way to adjust the code to
solve both problems (though you're welcome to try too).
Original comment by adeve...@gmail.com
on 10 Jun 2010 at 1:46
This problem has been reduced in r1694...it still exists, but requires less
selection/moving depending on how much the object is rotated. The closer to 180
degrees, the sooner it occurs.
Original comment by adeve...@gmail.com
on 31 Aug 2010 at 6:11
Original issue reported on code.google.com by
anas.has...@gmail.com
on 24 May 2010 at 4:15