Fillet and Bevel on polylines problem?

Consider drawing a rectangle (or any shapes) by using polylines command (closed),
I cannot make fillet or Bevel on the start/end point of the polylines, but i can make bevel/fillet on other nodes that is not the start/end points.
On the other hand, if we draw rectangles using rectangle command, the bevel/fillet works on all nodes.

is it supposed to behave like this? If yes, can anyone explain why and how to fix this?
I'm pretty much sure the polylines is closed, because i have generated Gcode/toolpath based on polylines, and it works well on the machine.
I'm sorry if this is a beginner's mistake...
Or is it a bug? I saw some open problems about fillet, but a little different from this one.

I check this behavior is consistent on two computers with different OS:
-Ubuntu 18.04 (LibreCAD 2.1.2) and
-Windows (Librecad 2.1.x).

Thanks!

The screen-capture is an example, but only for fillet.


 

I have just tested it and have to confirm it. I don't know the reason, but there are many imperfections with LibreCAD, we have to live with it.
When drawing a polyline you want to be closed, when you have done the last point before closing, then press the "Close" button in the Tool Options bar above the drawing area. It will close automatically then, and the difference is, the start/end point responds to fillet then! Just found out.

Thank you for the reply.
Yes you are right, it works if I use the `Close` button.
I'm not very familiar with the close function, it seems to find the closest path between the initial and last point? But at least i know it can work.

dellus wrote

there are many imperfections with LibreCAD, we have to live with it.

Yes… i guess this is what happens when we decided to use open-source software.
we have to live with it

By the way, @Dellus, should we report this on librecad github or not?

I wouldn't expect this issue to be tackled by some developer, there are not many around. I see it as a minor glitch which can be worked around with the "Close" feature. But if you feel a desire to report it, feel free to do so!

I guess you are right. I read that they are developing the version 3.
It's a very good piece of software to be honest.
Let's just wait for the new version…

I agree, yet the work around could be documented on the wiki for example.