So you want your CAD program to understand math?

I think it's the Pareto Principle.. I see it a lot throughout SW.. for simple things, yep it passes. As soon as things get slightly non trivial BAAAH!

from Wikipedia

*"It was also discovered that in general the 80% of a certain piece of software can be written in 20% of the total allocated time. Conversely, the hardest 20% of the code takes 80% of the time."*Thanks a lot. I am an Autodesk Inventor guy - nearly 15 years. I do use MathCAD (currently Prime 6.0): So. I am used to go by units. Despite, I have Solidworks license since 1917, I started just a month ago. I am getting better.

Roy Wickrama Arachchi wrote:

Thanks a lot. I am an Autodesk Inventor guy - nearly 15 years. I do use MathCAD (currently Prime 6.0): So. I am used to go by units. Despite, I have Solidworks license

**since 1917**, I started just a month ago. I am getting better.You must be very old.

Glenn Schroeder wrote:

Roy Wickrama Arachchi wrote:

Thanks a lot. I am an Autodesk Inventor guy - nearly 15 years. I do use MathCAD (currently Prime 6.0): So. I am used to go by units. Despite, I have Solidworks license

**since 1917**, I started just a month ago. I am getting better.You must be very old.

The computer back then would have been what, an abacus?

My guess is that since D1@Sketch1 and Spacing has inches as the units, the resulting answer is in inches. Why would it assume that the "int" function should remove the units?

Actually.... since both values have the unit of inches, a proper calculation would cancel the units.

I think it's bad for equations to have units. There's no way for SW to decide whether your result should have some unit or not. Equation results should be purely numerical. It's up to the user to get the numerical value they want, then they can apply that unitless numerical value to some entity that has units (like a dimension, etc.).

When you use dual dimension units, then in Equations table SW show you about value primary units.