I just tried to embed images in a new Inkscape document, created with
a recent SVN build of Inkscape, and it did not work. Here is the
problem (it's quite tricky):
The SVG document comes from a computer with a different directory
organization. It has images linked in it, that are in the same
directory that the document. I open it on my machine and copy parts
of it (some paths + some bitmaps) to a new, untilted document.
Inkscape copies the images with xlink:href containing a relative link
to the image (just the name in this case) and sodipodi:absref which
is not valid anymore (it contains the directory structure of the
other machine). In the new document, images initially appear as
broken links since the absref is not valid and the document has not
been saved, hence the root is unknown.
I save this new document next to the orignal one, so that the
relative links are respected. Once saved, the xlink:href become valid
but the images are still show as broken. I have to reopen the
document to see the images (which is probably a problem in itself).
In the XML editor, just to be sure, I deleted the sodipodi:absref
elements which were not valid anyway.
Then I tried to embbed the images and Inkscape complained saying
"No xlink:href or sodipodi:absref attributes found, or they do not
point to an existing file! Unable to embed image.
Sorry we could not locate /Applications/Inkscape.app/
The absref attributes are not there so that's fine but the xlinks are
valid. However Inkscape looks for images in /Applications/
Inkscape.app which is the default location where documents are saved
on OS X. If I remember well there was a document root attribute that
was removed some time ago. I suspect that embbed bitmaps was looking
for the images as document root+xlink and since document root is
inexistant the default is used.
This means that embbed images only works when sodipodi:absref is
present, now that document root does not exists. This seems like a
bug to me but the problem was complicated so I would prefer having
your advice. Did I explained it clearly?
Well currently I'll have to rewrite the sodipodi:abserf by hand and
it will solve the problem but the solution may be quite hard to find
for somebody who does not want to dive in the XML editor.
What was the decision on the live update of extensions?
The original justification was that it would happen in a separate thread so
you wouldn't notice, but it is *very* noticeable. At least on Windows with
the snapshot builds.
The worst part of it theres a DOS console that pops up every time the
command gets rerun, and often that steals the focus away from the text field
you're trying to type some number into. It's very annoying.
> Kent Tenney wrote:
> > I would like Inkscape to show only contents
> > of the active (selected?) layer, other layers
> > would not be visible.
Someone just needs to implement Alt+click on a layer in Layer dialog
to hide all other layers. That's how it's done in Photoshop so it will
be a familiar shortcut for most users.
Inkscape. Draw Freely.
As I mentioned earlier, I updated Inkscape description at Apple
downloads. The description was taken from the text on the main page
of the site and now that I played a bit with it and compared it to
other software, I tend to find it quite verbose and technical. This
text is what people will copy paste to describe Inkscape (as I did)
and does not look to appealing to me. For example I don't think there
is enough emphasis on the UI which is one of Inkscape greatest
strengths while some very basic things (shapes, paths, etc) are
mentioned while they can be considered self evident. Would a rework
of this text be acceptable or has it already been reworked many times
and this is considered final? How do you want Inkscape to be
perceived: as a UI on top of SVG or as a vector editor that happens
to use SVG as its format?
More specifically about Apple Downloads, I just thought I would let
you know that their staff updated Inkscape description. Now Inkscape
has a nicer screenshot, a more detailed description and is classified
as Imaging and 3D rather than under the more abstract "unix & open
However, since I submitted it, it is listed under my name (but links
to www.inkscape.org). This is obviously wrong (I don't want people
thinking that Inkscape is my project, by any means!) and I tried to
correct it by adding "Inkscape Community" as my company name. I hope
they will update the description soon. For 0.46, the best thing will
probably be to open an Apple account under the name "Inkscape
Community" and then I'll delete Inkscape from mine.
Has anyone noticed that the type=string variables passed to python
extensions have literal quotes in them?
For instance the number nodes (dots.py) example doesn't really work in the
latest snapshot I downloaded because the sizes are getting set to things
like '"20"' instead of just '20'
Some time ago we reported that executing extensions on Windows crashes Inkscape. Today I read the Bill Baxter was actually able to run some extension, so I tried again.
The LaTeX extension still crashes, Path-along-path too. But the grid extension does not crash.
Details: I am building Inkscape with a slightly modified build.xml so Inkscape always starts with a console window, to easily see debug info. I am going to try without console window now, to see whether that matters. In any case, execution of the grid extension did not spawn a new console window, nor did it pass focus to the already existing console.
The CMYK color input behaves strangely: in the Fill and Stroke panel, when I try to change the color percentages in the CMYK tab by entering numbers on the right of the color mixers, these numbers are somehow recalculated on the fly and already entered amounts change. Here's an example:
C 0 I change it into 44
M 27 jumps to 0
Y 61 jumps to 47
B 60 jumps to 71
And so on... It is almost impossible to input a CMYK color. Even entering CMYK color amounts with the help of the color sliders (for example MAGENTA) leads to subit changes in other colors (CYAN, YELLOW and BLACK).
I've done some draft yesterday and was using guidelines, something I
don't do very often...
Well, first of all, I would like guidelines to be selectable and then
placeble via the tool bar (everything but the x or y position should be
However, if this seems to hard to do, quickly, I think it would make
sense to at least allow the same number of digest after the point in
both, the guideline dialogue (currently 2) and the tool bar coordinates
(currently 3, which I of course prefer).
Greetings from Spain!
I was finally able to get the initial cut of supporting icc-color()
in. It should support most color spaces including CMYK.
At the moment it will only be active for colors with an icc profile
already set. There are some problems with the Lab and YCbCr color
spaces. So far I've tested RGB, CMYK and Grayscale successfully.
To test just build the latest, have a <color-profile> in your SVG and
set the color in the SVG.
So if you have a <color-profile> element with a name attribute of
"cmyk", then you would just need to set
fill:#ff00ff icc-color(cmyk, 0, 0, 0, 0, 0)