ragohix769 wrote: ↑Mon Feb 07, 2022 12:34 pm
I don't understand Thomas. Maybe you mean "normal" Offset that without "2d"?
I mean this
1.png
Ah ok.
I was talking about (BIM_Offset2D) not that in Part, maybe it's another command.
Attachments
wepz.png (41.81 KiB) Viewed 899 times
After #ElonMuskBuyTwitter I'm no more on Twitter, that's really enough
=> Now you can find me here on #Mastodon: https://mastodon.uno/@opensoul - I hope more people do the same
ragohix769 wrote: ↑Sun Feb 06, 2022 10:04 pm
Another problem that I have with Draft 2d offset: I select a wire or a sketch and when I use 2doffset, it automatically change the view to a nonsense or random position. I have to find the item then in the view. I don't know if this happen only to me, it's really annoying
I cannot confirm this one.
You are right Chris, sorry: the problem that I have reported it's with BIM_Offset2D. Maybe I'll open a thred more specific.
Last edited by ragohix769 on Mon Feb 07, 2022 2:43 pm, edited 1 time in total.
After #ElonMuskBuyTwitter I'm no more on Twitter, that's really enough
=> Now you can find me here on #Mastodon: https://mastodon.uno/@opensoul - I hope more people do the same
Roy_043 wrote: ↑Sun Feb 06, 2022 6:26 pmDraft_Offset does not handle sketches very well. See the attached file. Only the sketch in white (consistent direction and no arcs) is handled properly.
Yes, confirmed.
OS: Fedora 34 (Workstation Edition) (GNOME/gnome)
Word size of FreeCAD: 64-bit
Version: 0.20.27008 (Git)
Build type: Release
Branch: (HEAD detached at 9162733)
Hash: 91627338a44371fe9a8e815b4900f62558af98a1
Python version: 3.9.9
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: English/United States (en_US)
Edit:
Oops, it's not that simple. Will have to do some more checks.
I have update the PR. The connect function in intersections.py did not work properly if no intersection was found between the 1st segment and the last segment. It would then use the undefined v2 value to create a line segment. The problem would only occur if closed=True. I have also refactored the function.
This will fix the issue in the OP, but not the other issues reported in this thread.
