In my current project i try to get close to photorealism (don't want to actually achieve it). The scene contains a pool and i need to draw waves. Just drawing them will not give me good results. I don't want sharp edges. Bluring helps, but it can't work like a smudge brush in programs like GIMP. My ...

In Inkscape 0.48 you can control the snapping with the snapping toolbar. As i moved it around (grab n drag) it somehow disappeared. Now i tried to get it back. But it won't show up again. The Menu-Entry shows that it should be visible, but it isn't. It is somewhere, but not on my screen. Not hiding ...

Some time back i tried a new approach to draw. It basically came down to use Inkscape for the fine contours and Gimp for the gradients and other stuff. In my previous works i tried to use Inkscape alone. It also worked, but the filters have a heavy price, turning your new PC to look as if you tried ...

1. How exactly, when and on what does bitmap oversampling work? Any image aside from vector graphics uses pixels which are at best seen as a grid of "squares" with different colors. If you have 100% zoom then every pixel of the image is mapped to a single pixel and anything works fine. Bu...

@brynn: It is realy simple if you did some programming yourself. Think of the same path with two different descriptions. One with extended commands and one with the very basics. The basic paths Inkscape uses are described by lines and bezier curves. The SVG-Specification allows additionally to defin...

I haven't looked at your file yet, but the incorrect number of nodes is not related to the node type, but to the path commands used to describe the outline: since 0.47, the path uses 'a' ( elliptical arc ) commands to describe round caps and round joins of strokes converted to paths. While Inkscape...

I cannot confirm niabot's info, that smooth (square) nodes aren't counted. Mine reports 19 nodes, actually there are 25, smooth 21, corner/cusp 4. Unless I misunderstand or counted wrong? The difference might be that my original path contained smooth nodes (bezier curves), while niabot's appear to ...

I have verified that paths created with 'stroke to path' have a wrong node count in the select tool - a regression introduced in 0.47, possible with the new optimized path data (but I need to do some more tests). This one I will report myself. Maybe i should add: It does not count square nodes inse...

A case where this happens nearly every time: Create a closed path with four nodes. Set the nodes to auto-smooth. Now you have something like a potato. Select 2 neighboring nodes and move them. One not selected node will be replaced with at least 1 doubled node.

More detailed description. I experimented with the settings inside the node options. If i deactivate the the option i marked inside the screenshot with the mouse cursor (don't know how it is called inside the English translation), then it does not happen anymore. In effect the drawing is changed whi...

I appended an SVG-Example. I tried to reload the SVG and the error was still there. The more tests i made, the more sure i'm that "square" nodes aren't counted. A Modification to the path/contour will update the number correctly.

I can reproduce this problem. But it seams just to be related to a missing update of the node count for the "info display" after you applied "path to outline". As soon you change a single node it is right again. Seams not to be related to the double point issue. At least its not ...

Here is a simple example to illustrate that Spiro Curves get no closed (double node). Given that it only occurs at the end of the curve might indicate that this could be the result of another issue, that might be not directly related to the doubled nodes. In fact i think that all this double nodes m...

This applies to many more things than just the bucket. I also get such results from boolean operations, stroke to path conversions, and so on.

As my drawing starts to get more complex i found something ugly. While i drag a node and release the mousebutton to stop the movement it does not stop immediately. Instead Inkscape grabs the mouse location again as it redraws/refits the selection box, moving the node further as excepted (where the m...

You can avoid this error (a typical thing for simple antialiasing) if you export the graphic at a higher resolution (2 times or even more) and scale it down again. It basically has the same effect as multisampling, reducing this problem significantly. Another way is it to put another object under th...

I often work with pallets and sometimes i have the situation that i want to experiment with colors. Is it possible to use "named" colors that you can change like a gradient? Currently i used Linear Gradient with the same color on both ends. So if i change the gradient i can change the colo...

Then it should be implemented again. It's a feature i know from basically all graphic programs including Blender, Gimp, and so on. I tried to compile 0.46 under Ubuntu 10.10. After looking at the error messages i quickly decided not to continue. Anyway it would be nice to have this feature back agai...

I guess it are bugs. But as long they are not fixed it would come in handy. ;-) Also i currently noticed that converting a spiro curve to path (outline) in the node tools (button to the far right) does not work as expected. Converting it to a path first (usually adding some more nodes) and then conv...

I often notice that Inkscape creates doubled nodes. That in essential mean that two connected nodes (neighbors) of the same path have the exact same location. Right in this case they act as a single node. The only issue is, that it are two nodes and the artist has either to combine them or move them...

I will try to compile 0.46 on my system, hoping i'm still able to. Lets see if it has this feature, I'm very sure i was using without changing the code.

I just tested with Inkscape 0.46 and 0.47 (official builds for Mac OS X): On both versions 'Shift+Ctrl+drag' does not deselect the nodes within the dragged frame from the highlighted (selected) nodes. Do you still have the version installed that worked that way for you? On which platform? It was a ...

Alternatively if you want to use simple gausian blur (supported by more renders) : Make a copy of all objects, ungroup all this objects and convert them to pathes. After that you can "add" (boolean operation) them all together. Now you have a path, an outline of all Objects. Move it under ...

Deselecting nodes in 0.46 worked flawless. Which nodes, in the node tool? Or are you still talking about gradients? If this is about the node tool: do you have the transformation handles toggled on? In normal mode (default), it works as in the old tool (0.46, 0.47); with the transformation handles ...

@~suv: Yes the Edit > Paste style sometimes put the gradient elsewhere (usually i use Ctrl+Shift+V). Sometimes it is so far away that you can't even see it. As far as i remember this already happend in 0.46, but in very few cases. May be an issue while copying the previous object. Since it was mostl...