I finally found time to test the new node tool. Overall it feels
great, but of course I found many small and not so small things to fix
:) #1 is my personal pet peeve, if you can't see it please just give
me pointers to the code which passes events up and I'll have a look
I'll probably have more as I do more testing, but here's the fist batch:
1. Bug: Middle-button dragging and Shift-middle button zoom rubberband
still do not
work. Are you using a mouse with a middle button to test? They work in
Selector but not
2. Lost feature: when rotating/scaling nodes by keys and one node is
mouseovered, it is
used as center of rotation and scaling.
3. Lost feature: when ctrl+alt+dragging a node, it should slide along
the handles _and
4. Lost feature: when ctrl+alt+dragging a node, and it has a linear segment on
one side, it should slide along the continuation of that segment.
5. Lost feature: node sculpting. Will you work on it, or do you want
me to work on porting it?
6. Bug: select a single node and rotate it by  with or without Alt:
it rotates around
some random center far away, instead of around itself.
7. Lost feature: When rotating a handle with Ctrl, it now snaps to the original
position and 15 deg increments from that original position. The
previous behaviour was:
snap to origin, its opposite and perpendicular, to
vertical/horizontal, and to 15 deg
steps from vertical. This is much more useful because more often, I use Ctrl to
snap it to vertical or some simple angle like 60 deg.
8. Lost feature: create a cusp node next to a linear segment; press Shift+S; it
becomes semismooth, aligned with the segment (correct); now press
Shift+S again; old
behavior is to make it fully smooth, extending the second handle, but
your tool does nothing.
9. Lost feature: Rotating a handle with Shift before allowed to rotate
the second handle
by the same angle, thus rotating a cusp node as a whole; now it does nothing.
10. Suggested feature: now that we can edit multiple paths, Ctrl+A when nothing
selected should do the same in Node tool as in Selector, instead of
doing nothing as
11. Performance: Create a path with thousands of nodes (paste text,
convert to path,
combine), select it in Node tool: notice how slow it all becomes,
freezing for many
seconds, as you simply move your mouse over the path. My guess is that
something on each motion event and does not cache the results. The old
tool also wasn't
very snappy in such situation but it was much better, only freezing
for a couple seconds
at most with the same file (test it!) partly because it cached the livarot
representation of the path it used for proximity/over the path calculations.
12. Lost feature: the statusbar used to say how much total nodes are
there ("2 of 5
nodes selected") and, for a single node, its type (smooth, cusp,
auto). For multiple
subpaths it said e.g. "2 of 9 nodes selected in 2 of 3 subpaths". Now
it only says
"Selected 2 nodes" (which is also a wrong word order, suggesting an
action instead of a
state). Could you please just copy this part from the old node tool?
13. Suggested feature: now that we can select multiple objects, the
statusbar hints must
reflect that, in the same way as subpaths, e.g. "2 of 9 nodes selected in 2 of 3
subpaths in 1 of 2 selected paths", or simply "2 of 9 nodes selected
in 1 of 2 selected
paths" if there are no subpaths involved.
14. Bug: when dragging a node handle, statusbar erroneously says "Move
by" instead of
"Node handle:" as did the old tool.
15. When mouseovering a node, it says "click to select" even if it is already
selected. I'd like to copy this from the old tool as well, which
modifiers for dragging instead.
16. On the node deletion discussion, I found the current behavior
satisfactory: if you
Del, you get curved approximation; if you Ctrl+del you get linear segment from
linears. I think this is logical (unless I miss something).
17. UI suggestion: since the show/hide seltrans handles button belongs
it should be moved to the right end of the controls bar, next to node
handles and node
18. Crash: draw a path; draw a path and apply it as mask; draw another
and apply as
clippath; go to node tool; enable both mask and clippath editing; drag
a mask node; drag
a clippath node; drag a node of the path itself; undo 4 times - crash.
19. UI bug: create with Pen a Spiro path; now switch to Node tool -
the green outline of
the source path is visible always, even when "show outline of path"
toggle is off and
"show path parameter" was never pressed. Also, as we discussed in the summer, I
suggested a purple color for LPE parameter paths, so they are not confused with
20. Crash (somewhat hard to reproduce): With Pencil in Spiro mode,
create a path with
just two nodes (click, click). Now create a curved doodle path
(unrelated bug in Pencil:
you need to deselect first path before drawing second, otherwise they
joined!). Now select both paths, go to Node. Select the end node of
the linear path and
start node of the curved path. Mouseover the latter and press Shift+J.
Then press Ctrl+Z
while still mouseovering the joined node. Crash:
Program received signal SIGSEGV, Segmentation fault.
Inkscape::UI::NodeList::closed (this=0xbfffe3dc) at ui/tool/node.cpp:1060
#0 Inkscape::UI::NodeList::closed (this=0xbfffe3dc) at ui/tool/node.cpp:1060
#1 0x085fc574 in Inkscape::UI::CurveDragPoint::_getTip
(this=0xb8d57c8, state=4) at ui/tool/curve-drag-point.cpp:152
#2 0x085fadc1 in Inkscape::UI::ControlPoint::_updateTip
(this=0xb8d5790, state=4) at ui/tool/control-point.cpp:470
#3 0x085fb914 in Inkscape::UI::ControlPoint::_setMouseover
(p=0xb8d5790, state=4) at ui/tool/control-point.cpp:460
#4 0x085fc122 in Inkscape::UI::ControlPoint::_eventHandler
#5 0x085faad8 in Inkscape::UI::ControlPoint::_event_handler
#6 0x0824dd28 in sp_marshal_BOOLEAN__POINTER (closure=0xb5c0270,
marshal_data=0x85faac0) at helper/sp-marshal.cpp:352
#7 0x0056a072 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#8 0x0057f7a8 in ?? () from /usr/lib/libgobject-2.0.so.0
#9 0x005809b8 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#10 0x012b38ee in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x081c66df in emit_event (canvas=<value optimized out>,
event=0xb8d57c8) at display/sp-canvas.cpp:1348
#12 0x081c68e3 in pick_current_item (canvas=0x985c060, event=<value
optimized out>) at display/sp-canvas.cpp:1491
#13 0x081c9431 in sp_canvas_motion (widget=0x985c060, event=0xaf58340)
Inkscape. Draw Freely.
This list contains fixes between 4/14 @ 11:15am PDT - 4/22 @ 2:28pm PDT.
Only fixes to "true bugs" (i.e. no website/translation/docs/etc. bugs).
Pts BugID Fixer Description
6 479964 Johan Engelen "Fit Page to Selection" doesn't take arrow...
3 429776 Johan Engelen Axonometric grid unusable when spacing set...
3 554734 JazzyNico inconvenient default path for extension...
12 165529 jaspervdg border around bitmap object in exported png
3 530790 Jon Cruz Compiler warning: function returns random...
3 439270 ycswyw javafx save with errored call to function path
6 455302 jaspervdg Filter: Ink bleed with bad results
12 208768 Kosiński Bézier tool behaviour changed with 0.46
3 401567 JazzyNico Render>Grid doesn't render the horizontal...
It's regarding this bug:
I recently commited a fix, but now it appears there might be a new
problem with this filter. It doesn't look directly related to the fix to
this particular bug, but it perhaps it has something to do with one my
other fixes (or someone else's). Unfortunately I cannot reproduce the
problem, so I'd like to know who CAN reproduce it (and how).
If you can reproduce the problem any information that might help pin
down the exact revision in which the problem was introduced would help.
(Obviously it's also interesting if you CANNOT reproduce the problem.)
Today, I decided to change my main launchpad email address back to
something that I read. Can someone tell me how to stop receiving
general Inkscape Bug Team mails?
(the mails that say: "You received this bug notification because you are
a member of Inkscape Bug Team, which is subscribed to Inkscape.")
If this is not possible without leaving the Bug Team, I'm forced to set
my mailaddress back to the spam address.
I've started using SVG for some of the graphics on my pages, and
encountered some problems - probably due to ignorance... but not for lack
of trying to find answers:
1) If I 'embed' an SVN image in a page, and want to use it as a link to
somewhere else, I find that the image isn't sensitive. I'm using Firefox
3.6 - I thought embedding was ok for the majority of browsers?
2) If I define the size smaller than the original image, I get scrollbars
in Firefox. I thought SVN was scaleable? Or are the images only scaleable
to larger sizes - never seen that mentioned...
I'd appreciate pointers to documentation for either or both issues.
I've fixed Inkscape to actually respect the filterUnits (and
primitiveUnits) propertie(s), but now I need to be able to access the
viewport dimensions for the filtered object... As far as I have been
able to find this is only available reliably from SPItemCtx. But for a
filter I need to access this not for the filter itself, but rather for
the filtered object... Any help would be appreciated.
Getting this right would fix the following bug btw.:
Disclaimer: *This is no advertisement.* If it doesn't get clear from the
following, I'm in no way associated with the owners of
StackOverflow.com. (I mention this, because after reading the mail
again, it could be interpreted the wrong way.)
The Q&A platform StackOverflow offers open source projects free ad space
to recruit new developers . The method is quite simple: If you want
to have an ad there, place it as answer to the question linked as 
and hope for other people to upvote it. After a certain threshold of
upvotes it gets published for free on stackoverflow.com.
Since Inkscape hasn't got an ad proposal there, yet, I thought I'd
suggest one. It must be 220px x 220px and GIF or PNG, and my suggestion
If noone on the list objects (especially against using the Inkscape
logo) I'd upload the proposal to meta.stackoverflow.com during the
weekend. If there are suggestions for other banners, mine can easily be
exchanged afterwards. I write this mail just because I don't want to do
the ad kind of behind the back of the Inkscape developers.
By the way: What would be your suggestion for the backlink the ad should
point to? The wiki? The Inkscape homepage?
I'm working against a clean debian stable environment now, I think.
The current problem appears to be with an undocumented dependency
on ImageMagick (I think on an old version of ImageMagick). ImageMagick
doesn't show up in this list:
The build finally dies like this:
Making all in src
make: Entering directory `/home/bkerin/tmp/inkscape-0.47/src'
g++ -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual
-Wswitch -Wno-unused-parameter -g -O2 -fopenmp --export-dynamic
-Wl,-z,relro -o inkscape main.o libinkscape.a dom/libdom.a
libcroco/libcroco.a libavoid/libavoid.a libgdl/libgdl.a libcola/libcola.a
libvpsc/libvpsc.a livarot/libvarot.a 2geom/lib2geom.a libinkversion.a
-pthread -L/home/bkerin/opt/gnome_clean/lib -lgtkmm-2.4 -latkmm-1.6
-lgdkmm-2.4 -lgiomm-2.4 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lxslt
-lxml2 -lsigc-2.0 -lgtkspell -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0
-lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0
-lfreetype -lz -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt
-lglib-2.0 -lpng12 -lgsl -lgslcblas -lm -lpng -lz -lgomp -lpopt -laspell
-pthread -L/home/bkerin/opt/gnome_clean/lib -lgnomevfs-2 -lgconf-2
-lgthread-2.0 -lrt -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -lfontconfig
-L/home/bkerin/opt/gnome_clean/lib -lpangoft2-1.0 -lpango-1.0 -lfreetype -lz
-lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0
-L/home/bkerin/local/lib -lfreetype -lz -lMagick++ -lWand -lMagick
-lgc -llcms -lpoppler -lpoppler-glib
/usr/bin/ld: warning: librt.so.1, needed by
/home/bkerin/opt/gnome_clean/lib/libgthread-2.0.so, may conflict with
/usr/bin/ld: warning: librt.so.1, needed by
/home/bkerin/opt/gnome_clean/lib/libgthread-2.0.so, may conflict with
libinkscape.a(addNoise.o): In function
undefined reference to `Magick::Image::addNoise(MagickLib::NoiseType)'
libinkscape.a(channel.o): In function
undefined reference to `Magick::Image::channel(MagickLib::ChannelType)'
libinkscape.a(levelChannel.o): In function
undefined reference to `Magick::Image::levelChannel(MagickLib::ChannelType,
double, double, double)'
collect2: ld returned 1 exit status
make: *** [inkscape] Error 1
make: Leaving directory `/home/bkerin/tmp/inkscape-0.47/src'
make: *** [all-recursive] Error 1
make: Leaving directory `/home/bkerin/tmp/inkscape-0.47'
make: *** [all] Error 2
I know I've seen that librt error before as well, though I don't recall
what the fix was or if it was needed.