Blend tool : different thickness

B-Vs-V

@b77 thank you for your reply... I've tried but I don't have yet the possibility to upload file.

b77

@PatrickM Make sure the file is not too big (copy the blend object to a new file if necessary) then upload it by clicking the last button.

VectorStyler

@PatrickM There could be some issue with the forum.
Try drag&drop into the text box when replying to the post. If the file is not too large, it should work.

B-Vs-V

encart

In both cases problem appears in 7&8th line
@vectoradmin File sent

VectorStyler

@encart Can be replicated. Looks like a bug.

VectorStyler

@PatrickM I will try to find out what settings are wrong on the forum.

encart

@vectoradmin This file contain another bug I'm fighting with. In often have problems with Undo/Redo. I tried to undo 5-10 steps and the lines created in Blend tool(as the last object) were still visible together with nodes from objects deleted previously. Deleted objects were present in Layer panel and I could select them, but werent visible on canvas even when I changed the fill and stroke. Just selection box was visible.

VectorStyler

@encart I add this to the backlog as a bug.

B-Vs-V

@encart said in Blend tool : different thickness:

@vectoradmin This file contain another bug I'm fighting with. In often have problems with Undo/Redo. I tried to undo 5-10 steps and the lines created in Blend tool(as the last object) were still visible together with nodes from objects deleted previously. Deleted objects were present in Layer panel and I could select them, but werent visible on canvas even when I changed the fill and stroke. Just selection box was visible.

I had similar issues too with Undo, even a line drawn with pencil on the artboard went out the artboard.
I've just opened the file from yesterday and the blended lines are not there (they were when I saved)...
0_1636713535437_814c1e23-9254-4220-8951-2f060829de41-image.png . I don't know if it helps.
Patrick

VectorStyler

@PatrickM The fix for earlier blend issue will be in the next build.
But this latest reported issue is not replicated yet.