Warning: This question might be specefic to Inkscape extension scripts
written in Python.
I've come up with ideas for several little extensions scripts I'd like
to write for Inkscape. Most deal with allowing the type of "precision"
drawing that would make Inkscape more suitable for precision drawing.
I keep running into an obstacle when I think about the design of these
scripts, and I thought I might get some help here.
An example may be the easiest way to ask my question.
I want to write a script that makes one line segment parallel or
perpendicular to another line segment. The problem is that I want to
make the line segment selected last by the user parallel to the line
segment that is selected first, not the other way around.
I'm looking for a way to do this without having the user run two
scripts. The first to select the line that will not be modified, and
the second to select the line that will be modified and that then
performs the operation.
Does Inkscape "deliver" the selected items to an extension script in
the order they were selected? Or is the order random? If the order
isn't random, which items (or nodes) would come first? Those selected
last by the user, or those selected first?
I hope my question makes sense. I might be pushing the envelope of
what is possible with Inkscape's current extensions script system.
On Thu, 11 Oct 2007 17:34:57 +0200, "Maarten van der Velde" <Maarten.van-der-Velde@...1771...> wrote:
> I'm just wondering why it happens? Are the names for the gradients
> assigned based on a incrementing counter? Can't we just assign them
> random numbers?
Random numbers aren't guaranteed to be unique either.
Is there an option so when you tweak the colours of a gradient it modifies
the current gradient rather than makes a copy then modifies it?
I normally reuse gradients on multiple objects to intentially keep them same
for if I decide to change colours. I don't know if others feel the same,
but my preference would be that when I tweak the gradient on one object, all
other objects that also use that gradient should change also. Perhaps a
toggle in the tool control bar?
View this message in context: http://www.nabble.com/Color-Tweak---Option-to-not-create-new-gradient-tf4...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
One minor issue I have with Inkscape is that the tools aren't named in the
This doesn't effect my own use, but when attempting to help someone else I
like to refer to tools by their correct names and I don't know what some
tools are called off the top of my head. Refering to them by their
description in impractical. The only way I know how to find out the correct
name of a tool is to look at the Keys and Mouse reference.
Is it possible to put the tool name in the tooltips? Or are the names of
the tools already revealed within Inkscape in a way that I have overlooked?
View this message in context: http://www.nabble.com/Tool-names-in-tooltips-tf4604916.html#a13148870
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
> Actually it might make sense to make it a preference. Something like
> specifying what happens to the other layers when one is selected
That's a good idea in and of it's self, make the two things distinct
functions and together they make a powerful control.
So one idea is to have a slider bar to change which layer is selected.
And the second idea is to be able to set some how what happens to
other layers and the current layer such that it should be possible to
make the current layer visible, the next and previous layers semi
transparent and all other layers invisible. this would also be very
cool for doing tracing and a bunch of other things.
>> I wrote the barcode plugin, I can't Imagen it'd be too much more difficult.
> Ah, I didn't realize that was you. Yes, this one should be much easier :)
Yes the barcode wasn't that hard to be honest I translated my perl
barcode stuff to python.
> Also, from the SVG perspective there is a good group of people who talk
> about SVG related issues over here:
I'm planning on creating a python based plugin which will look at each
of the objects in each root layer and allow you to combine them into a
support is just the path and transofrm animations and maybe style.
I'll make it so you should be able to select the timing between each
I'm posting this to the inkscape devel list for you guys to shoot down
as many as the silly ideas as possible so we can come up with some
Best Regards, Martin Owens
Just a quick note to let you know that, after changing Inkscape
description text at Apple, the project gained a little visibility (it
was marked as updated) but also changed location (moved from Unix &
Open source to Imaging & 3D) and lost its staff-picked status. As of
today, Inkscape has been staff-picked again and, maybe more
importantly, is back in the top ten most popular applications in its
new category (it is number 6):
There is no indication of how the "popularity" is judged but since
the list features old and new items, staff-picked as well as non-
staff picked items etc. my guess is that a simple metric such as the
number of clicks on the download link or the number of visits to the
product page is used. This is all very good news for Inkscape and
0.46 promises to be a really big hit. Congratulations to everyone.
All those thinking of going to SCALE - it would be great to have a paper
submitted, but if no one is up for that, we should plan on at least a
BOF on all the new cool features that will be in .46 that should be out
by then. At any rate we should coordinate and then let Gareth know.
While working with some text in Inkscape, I found an unpleasant behaviour of the text selection field (the field above the font selection drop down menu): it is case sensitive. When I type "Arial" in it and hit enter, the selected text's font is changed to arial as it should. But if I type "arial" or "ARIAL", then I get a warning that the font is not found/installed.
The expected behaviour is that no matter what case I enter in (like aRiaL) it must find the font I'm looking for (this is the behaviour of Illustrator, Indesign, Corel, Photoshop, Openoffice and many other programs).
Although it is not a real bug, it is IMO a usability issue.
By the way, I'm on Windows XP sp2. Is it the same on Linux? Mac? And should I fill a feature request or a bug report?
What do you think about docking floating extensions dialogs (i.e.
dialogs with "Floating" option enabled)? When you have several of them
around and you need them all the time, docking them would make sense.