search

Letractively / svgweb

Automatically exported from code.google.com/p/svgweb
Other
0 stars 0 forks source link

currentTranslate.setXY does translate the svg, but doesn't affect currentTranslate.getX or getY #401

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Save the attached html file in the svgweb/samples directory
2. Open it in a browser, you will see the svg and a message dialog saying 
"Starting translate, 
currentTranslate is: 0, 0". When you click OK, the script will increase 
currentTranslate x and y 
by 20 by calling currentTranslate.setXY.
3. Click OK and a new message dialog will popup giving the currentTranslate 
coordinates after 
translating by 20.

What is the expected output? What do you see instead?
Two things should happen:
1. The svg image should shift 20px. This works.
2. The second message dialog should show "Starting translate, currentTranslate 
is: 20, 20", 
because the script increased currentTranslate x and y by 20. However, it 
displays 
"currentTranslate is: 0, 0" instead.

If I change the script to use currentTranslate.setX() and 
currentTranslate.setY() instead of 
setXY(), it returns the expected result. You can try this by commenting line 18 
and uncommenting 
line 19 and 20.

What version of the product are you using? On what operating system,
browser, and version of Flash?
Tested this in FF 3.5 and Chromium under Ubuntu 9.10 on r972 of svgweb.

Original issue reported on code.google.com by thomaskelder on 6 Nov 2009 at 10:07

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by bradneub...@gmail.com on 6 Nov 2009 at 10:23

GoogleCodeExporter commented 8 years ago

Original comment by bradneub...@gmail.com on 10 Nov 2009 at 10:09

GoogleCodeExporter commented 8 years ago 
This affects the Wikipedia prototype in Issue 291.

Original comment by bradneub...@gmail.com on 10 Nov 2009 at 9:27

GoogleCodeExporter commented 8 years ago

Original comment by bradneub...@gmail.com on 10 Nov 2009 at 9:27

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r982.

Original comment by bradneub...@gmail.com on 13 Nov 2009 at 2:12