chenbo007 / svg-edit

Automatically exported from code.google.com/p/svg-edit
0 stars 0 forks source link

Move to decimal point coordinates and measurements #74

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
due to the scalable nature of the svg documents, a designer would want to
be able to fine-set the value of the stroke width and possibly corner radii
using non-integer units.

an example with corner radius value: just try to make the stroke 40 for an
rectangle and change corner radius from 0 to 1. the difference is huge! the
designer would need to have access to values between 0 and 1.

Original issue reported on code.google.com by Christia...@gmail.com on 12 Jul 2009 at 2:53

GoogleCodeExporter commented 9 years ago

Original comment by codedr...@gmail.com on 12 Jul 2009 at 9:30

GoogleCodeExporter commented 9 years ago

Original comment by codedr...@gmail.com on 7 Aug 2009 at 3:03

GoogleCodeExporter commented 9 years ago
with the addition of viewport, make that 4-6 decimal places and a minus sign 
(usable 
for google maps coordinates and other coordinate systems)

Original comment by Christia...@gmail.com on 13 Sep 2009 at 10:03

GoogleCodeExporter commented 9 years ago
Issue 211 has been merged into this issue.

Original comment by codedr...@gmail.com on 17 Sep 2009 at 2:45

GoogleCodeExporter commented 9 years ago
Issue 195 has been merged into this issue.

Original comment by codedr...@gmail.com on 17 Sep 2009 at 2:46

GoogleCodeExporter commented 9 years ago
Now that zoom is in place, we need to move away from integral coordinates.  We 
need
to ensure that measurements and coordinates can be specified at sufficient 
number of
decimal places.

This means an update to some of the controls as well (rect radius, stroke-width,
font-size, x, y, width, height, cx, cy, rx, ry, r, etc).

Original comment by codedr...@gmail.com on 17 Sep 2009 at 2:49

GoogleCodeExporter commented 9 years ago
r661 has a start on this - properly sizing the selector box and allowing 
floating
point coordinates when dragging/resizing.

There are still problems with poly editing at high zoom levels though.

Original comment by codedr...@gmail.com on 17 Sep 2009 at 3:09

GoogleCodeExporter commented 9 years ago
Issue 214 has been merged into this issue.

Original comment by codedr...@gmail.com on 17 Sep 2009 at 4:55

GoogleCodeExporter commented 9 years ago
I think what's left to be done for this Issue is only the following:

  * update all controls to allow decimal places (including font-size)

Original comment by codedr...@gmail.com on 23 Sep 2009 at 6:13

GoogleCodeExporter commented 9 years ago

Original comment by adeve...@gmail.com on 20 Oct 2009 at 4:07

GoogleCodeExporter commented 9 years ago
With font-size and opacity changed, is anything left? If not, I guess this 
issue can 
be closed.

Original comment by adeve...@gmail.com on 20 Oct 2009 at 8:30

GoogleCodeExporter commented 9 years ago
Sorry.. I have Linux, Firefox 3.5 and i checked out the latest version (because 
of
the firefox cache issue) it does not allow me to type a period "." in any of the
fields that have the roller controls (it shows the dot, then it deletes it)

am i missing something?

Original comment by Christia...@gmail.com on 20 Oct 2009 at 9:27

GoogleCodeExporter commented 9 years ago
I agree that it is extremely difficult to enter a value with a decimal point in 
the
fields.
In the Opacity field, you have to go down to 0, then type for example .3, you 
will
see "3", then put the cursor on the left of the field, then type "." again. 
Then you
get a decimal 0.3.

In the rotation angle field, it's a bit easier, but not really casual. It's a 
general
problem with entering values in all the fields, really, but those two are 
confusing.

The Font size and Zoom spinners are also extremely difficult to "stop", and 
these two
can hog the CPU and freeze the browser, this is not a good thing.

Original comment by worms_...@yahoo.com on 21 Oct 2009 at 6:31

GoogleCodeExporter commented 9 years ago
Sorry I forgot about the keyboard input issue, I believe it has now been fixed 
in 
r855. Basically it will only update now when:
- You press the enter/return key
- You press the tab key
- You press the up/down/PageUp/PageDown keys 
- You click somewhere on the toolbar, or another field

I believe I also fixed the Font size/zoom spinner issue mentioned in c#13 in 
r856. 
Please verify, and feel free to close the issue if you're satisfied. :)

Original comment by adeve...@gmail.com on 21 Oct 2009 at 12:33

GoogleCodeExporter commented 9 years ago
satisfied here :) thank you!

Original comment by Christia...@gmail.com on 21 Oct 2009 at 12:47

GoogleCodeExporter commented 9 years ago
Yes, it's all good for me now, thank you!

Original comment by worms_...@yahoo.com on 21 Oct 2009 at 1:00

GoogleCodeExporter commented 9 years ago
Two satisfied customers = closing this issue. :)

Original comment by adeve...@gmail.com on 21 Oct 2009 at 1:01