Problem with creating closed paths

[aydsys]

hello.

I am new to inkscape. I get this unexpected behavior when closing a path, please see the video
https://vk.com/club1459225?w=wall-1459225_271%2Fall
There are also similar issues when editing paths with the nodes tool

How to fix it please help

Thank you

[brynn]

Welcome to the forum!

Are you using the "Triangle In" shape option on purpose?  When you use that particular shape option, the Powerstroke LPE is automatically applied to the path.  For a reason which I don't understand, powerstroke doesn't work on a closed path.  (although I think I heard that the next version will fix that....it seems like I heard that, but can't remember where)

Also, testing on my own canvas, I'm finding it's behaving strangely with corner/cusp nodes.....  This has to be a known problem -- it's too blatant!

Well anyway, for your problem, if you didn't use the powerstroke on purpose, just choose None in the Shape dropdown menu, on the control bar.  Or if you don't want to draw the path again, then select it, and do Path menu > Remove Path Effect (bottom of the menu). 

If you are using it on purpose, don't close the path.  If you need the path to at least look like it's closed, we can help with various tricks.

Oh!  Or if I'm correct that it's going to be fixed in the next version, it might actually already be fixed, which means you could install the development version.

Let me do a little research, and maybe I can find out for sure.

[brynn]

No luck with the research.  But it might not be very hard to install the development version, and just try it.  I've kind of lost track where to get it anymore.  But someone else should be by before too long, who can give you the correct link.

(Meanwhile, I guess I should report the problem I found.  If I learn anything more about your problem, I'll post again )

[Moini]

Yes, either remove the path effect or don't close the path (you can put the nodes above each other, without closing it).
In Inkscape 0.92.2, this just doesn't work (and I think it also doesn't work in 0.92.3, probably will in 0.93).

[brynn]

doesn't work in 0.92.3, probably will in 0.93)

I didn't realize there was going to be 0.92.3.  I thought the next release was going to be 0.93.  But if that's the case, that means it's not fixed yet, even in dev version.

[aydsys]

Phew, it worked, thanks for clarifying. I was afraid it was because my pc is obsolete, and i will not be able to carry my project. thanks

[Moini]

Uhm... It is fixed, in the dev version for 0.93.

[brynn]

You mean there's a dev version for 0.93, before 0.92.3 is released?

[Moini]

Yes, of course. We've had a stable development branch (0.92.x) and a new-features-and-big-changes (0.93 or master) development branch since the release of 0.92 in January 2017 - this is common for Inkscape, also before that, only the numbers change.

[brynn]

Oh, I always thought the development version was for whatever the next release is going to be.  I thought it was all  linear -- that you don't have version 0.93 until the last 0.92.x is released.

So if there are things which are fixed in the 0.93 development versions, they might not be in the next 0.92.x release?  From my uneducated (in programming) perspective -- why wouldn't you want to release everything that's fixed in whatever the next release is?

[Moini]

Because some fixes can only be done on the code of a specific version, they depend on other changes, but those changes are too big for a 0.92.3.

[brynn]

Ok, thanks