Profile Edges - Why Div by Zero Error?

[falviani]

Hi,

Here's my setup:
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18750 (Git)
Build type: Release
Branch: master
Hash: a3e88a399fb6395a20f4cf5c7e3ed70e61c9e22f
Python version: 3.6.7
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)

I built a super simple test to see what the effect of the compensation factor was in the profile edges operation. There are 2 20mm squares. One has the profile set to outside, with a -1 compensation; my guess was that the cut would be on the edge. The other has the profile set to inside, with a +1 compensation; again my guess was that it would be on the edge. I keep getting the 'fullsteps = int((start - stop) / size)' zero division error-but I can't figure out what is the wrong value. The freeCAD file is attached - could anyone point out the obvious error I'm making.

I'm afraid I'm finding the UI hard to figure out - the Op values don't seem to match what I'm expecting, and having fake values followed by real values in parenthesis in the depth area of the property pane seems counter-intuitive.

Thanks in advance,
Frank

[mlampert]

Interesting - I don't get that error, a simple recompute seems to produce the correct results. The error looks like you depth is 0, StartDepth == FinalDepth ?

Code: Select all

OS: Debian GNU/Linux bullseye/sid (LXQt//usr/share/xsessions/lxqt)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18833 (Git)
Build type: Debug
Branch: feature/tool-bit-poc
Hash: 71f1e952a32c389bc6ef6f1a8411c6e43fcaed54
Python version: 3.7.5
Qt version: 5.12.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/Canada (en_CA)

[falviani]

Hmm..I just downloaded the latest Win10 nightly:
OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18778 (Git)
Build type: Release
Branch: master
Hash: f55cf3ef103532c9718c108bd856a4ef06ad49a5
Python version: 3.6.7
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)

and the recompute cleared everything up. A transient bug, obviously.

I ran the job and measured the results, getting the results I expected.