about cspsubdiv:
the actual behaviour doesn't look like it's unwanted. there is an actual method that is explicitly designed to check for the distance from a point to its handle, and it is within the cspsubdiv.py.
other than that i have no way to determine what was intended since the "class" is not documented in any way.
after a quick search i found my conjecture confirmed: cspsubdiv is only used by flatten.py, and flatten is requesting a unitless number from the user, cspsubdiv is not intended to check for a specific length of some sort, so it is not a deficiency.
i could propose a change to cspsubdiv in terms of a new parameter that enables a check for the real length while preserving compatibility or something like that, but then i have to wait for that proposal to be fulfilled before i can use it to fix my bug.
if you want that just say it and i will do the proposal.
thanks Alvin.
about cspsubdiv:
the actual behaviour doesn't look like it's unwanted. there is an actual method that is explicitly designed to check for the distance from a point to its handle, and it is within the cspsubdiv.py.
other than that i have no way to determine what was intended since the "class" is not documented in any way.
after a quick search i found my conjecture confirmed: cspsubdiv is only used by flatten.py, and flatten is requesting a unitless number from the user, cspsubdiv is not intended to check for a specific length of some sort, so it is not a deficiency.
i could propose a change to cspsubdiv in terms of a new parameter that enables a check for the real length while preserving compatibility or something like that, but then i have to wait for that proposal to be fulfilled before i can use it to fix my bug.
if you want that just say it and i will do the proposal.