Re: [Inkscape-devel] remove/apply transformations?
by Robert Crosbie
---8<---Snip--->8---
>>Lets say I want to draw a regular hexagon. I will draw 3
>>identical lines, rotate one 60, another -60, then apply the
>>transformations. The endpoints of these paths will give me the
>>control points to draw the hexagon.
>
>From this example, however, I don't see why you need preserving
>transformations - if you apply them at once! This means you just
>want the rotate command (in the Transformation dialog, I suppose) to
>work in the "optimize" mode, i.e. apply the transformations for
>you. Or am I missing something?
In this particular case, optimize mode would work well, but I am actually
constantly switching between the two.
Suppose I'm drawing a snowflake:
http://members.rogers.com/rcrosbie/images/woodworking/snowflake_2c.jpg
I only need to work on one branch of that snowflake, group the paths and the
others are copies of that branch that are rotated. In this case I want to
work in preserve mode because If I make a change to one of the branches, I
can copy that change to the transformed groups. But suppose I want the
side-branches to meet. I will then use my hexagon example above to find the
point where side-branches intersect and use that as my endpoint.
I usually want to optimize the transformations in jig objects that are used
to find points for my preserved object. Does that make sense?
I wouldn't have to do things like this if inkscape had some CAD-like path
features such as: Connect path A to the midpoint of Path B; Clip path A at
it's intersection with path B; etc. I'm constantly making objects to
precisely find these points that I need.
Check out this celtic knot:
http://members.rogers.com/rcrosbie/images/woodworking/plate5of3a.jpg
It consists of 5 copies of the same path that are rotated, but I had to draw
a lot of intermediary objects and paths to ensure that that one path would
be seamless when it was rotated and combined into the larger object. It's
the intermediary objects that I need to apply the transformations to.
Cheers,
Rob.
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
19 years, 2 months
RE: [Inkscape-devel] RE: couple of functionality tweaks
by bulia byak
>Hey, wait a minute, actually I programmed this long ago - and it works for
>me! Could you please describe in detail how it's not working? With a sample
>file and step-by-step instructions?
Perhaps this is a misunderstanding: It should deselect any selected nodes
(they must become all gray), but not deselect the shape itself (why would
you need that in node edit?) If you need to edit nodes of another shape,
however, you can click on it, and it will be selected instead (i.e. the old
shape's nodes will disappear, and the new shape will show its nodes,
initially deselected (gray)).
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjo...
19 years, 2 months
RE: couple of functionality tweaks
by bulia byak
>While I was editing a shape using the node-select tool, I tried to
>deselect the shape by clicking on the canvas, which is kinda standard
>practice, and the shape was still selected (ie, the nodes were active).
>When one is using the node edit tool and they click on open space, all
>nodes should be deselected.
>
>I'm putting an RFE in on this one, but I figured it might be a simple
>change.
>https://sourceforge.net/tracker/index.php?func=detail&aid=884979&group_id...
Hey, wait a minute, actually I programmed this long ago - and it works for
me! Could you please describe in detail how it's not working? With a sample
file and step-by-step instructions?
Anyone else having problems with this?
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
19 years, 2 months
RE: [Inkscape-devel] remove/apply transformations?
by Robert Crosbie
I actually have a need for both "transform = " and "apply transform" (I see
no need for "remove transform"). I would prefer that when I transform an
object, I get a "transform = " and then have the ability to apply that
transform.
Lets say I want to draw a regular hexagon. I will draw 3 identical lines,
rotate one 60, another -60, then apply the transformations. The endpoints
of these paths will give me the control points to draw the hexagon. This is
a simplified example, but I do things like this a lot to get accurate
points.
In inkscape, currently, I combine paths to apply a transformation. I'd
really like to see an apply transform button.
Rob.
http://members.rogers.com/rcrosbie
>From: "bulia byak" <archiver_1@...19...>
>To: inkscape-devel(a)lists.sourceforge.net
>Subject: [Inkscape-devel] remove/apply transformations?
>Date: Mon, 26 Jan 2004 16:08:38 +0000
>
>Another confusing concept. SVG allows to store transformations (moves,
>rotates, etc) both "natively" (in the object's own coordinates) and as a
>transform= attribute that is applied "after the fact". Of the many commands
>that move/rotate objects, some (most) write the new coordinates directly
>into the object, but some just add a transform= attribute without changing
>anything else in the object. I see no apparent logic behind this difference
>in behavior.
>
>Now, the "remove transformations" command simply erases the transform=
>attribute if it is present. Recent Sodipodi adds "apply transformations"
>which writes the transform= into the object and then removes it (i.e. no
>visible change). I think this mess is very confusing and serves no useful
>purpose. To an artist, "remove transformations" works as a weird sort of
>undo whose results are generally unpredictable, and "apply transformations"
>does nothing at all. So I propose:
>
>- remove the "remove transformations" command.
>
>- fix the remaining commands that add transform= so that they always
>"apply" their transformations to the objects at once. (In particular,
>scaling a text object must affect its font size; transforming a group must
>write transformations into the group's members instead of adding transform=
>to the entire group.)
>
>I may have missed something, so please argue.
>
>_________________________________________________________________
>The new MSN 8: advanced junk mail protection and 2 months FREE*
>http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin....
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>Inkscape-devel mailing list
>Inkscape-devel(a)lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/inkscape-devel
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin....
19 years, 2 months
Re: [Inkscape-devel] new preview?
by bulia byak
>If this functionality is in fact "Preview in Browser" then it is certainly
>confusing which makes it useless in its current state but I think with
>minor changes it could be made genuinely useful.
Good idea to make this command an "External preview". Just store a command
line with options in prefs, and when a preview is requested, save the
current file and run the command on it.
This seems to be similar to the task of running an external browser for help
files - therefore, Jon, what would you say if I ask you to add this to your
TODO?
Right now, however, the "preview" is done by Inkscape itself, and is
therefore useless. So I'm removing this command for now, until we have an
external preview functionality.
Alan, can you say your word on the most HIG-compliant set of scrollwheel
modifiers? As I wrote some time ago:
We have this item in the roadmap:
* Decide on mouse scrollwheel modifiers [everyone, see mailing list
archives]
So, once you raised the issue, could you please review the current wheel
behaviors:
# Mouse wheel scroll canvas vertically
# Ctrl + Mouse wheel scroll canvas horizontally
# Shift + Mouse wheel zoom in or out
and propose a change to conform to HIG, but without losing any of the three
functions. After you publish your proposal here, if no one objects, I will
code it.
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin....
19 years, 2 months
new preview?
by bulia byak
Anyone would object if I remove this command? What it does is basically runs
an SVG viewer on the current file. The idea behind this is unclear to me. If
you want a parallel view of your file, "New view" would be just fine. So I
think "New preview" is confusing and useless.
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
19 years, 2 months
news + features
by Jonathan Phillips
Does anyone have any news/announcements that they would like on the main
page.
I'm going to add prior to our release:
- inkscape-user mailing list announcement
Are there any more announcements?
Jon
--
Jonathan Phillips <jon@...15...>
19 years, 2 months
remove/apply transformations?
by bulia byak
Another confusing concept. SVG allows to store transformations (moves,
rotates, etc) both "natively" (in the object's own coordinates) and as a
transform= attribute that is applied "after the fact". Of the many commands
that move/rotate objects, some (most) write the new coordinates directly
into the object, but some just add a transform= attribute without changing
anything else in the object. I see no apparent logic behind this difference
in behavior.
Now, the "remove transformations" command simply erases the transform=
attribute if it is present. Recent Sodipodi adds "apply transformations"
which writes the transform= into the object and then removes it (i.e. no
visible change). I think this mess is very confusing and serves no useful
purpose. To an artist, "remove transformations" works as a weird sort of
undo whose results are generally unpredictable, and "apply transformations"
does nothing at all. So I propose:
- remove the "remove transformations" command.
- fix the remaining commands that add transform= so that they always "apply"
their transformations to the objects at once. (In particular, scaling a text
object must affect its font size; transforming a group must write
transformations into the group's members instead of adding transform= to the
entire group.)
I may have missed something, so please argue.
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2fjoin....
19 years, 2 months
