ickby wrote:no. mostly because the code was merged into master a few hours ago and the branches are deleted now,

wait, the whole new partdesign/assembly work was merged? without an additional test request? before the release?

What's the purpose of the part object? I get that a body acts as a container for other features, but what does the part object do? The part object is a generic abstraction. It is intended be used for next means : - it is a placeable group of objects. (e.g. it's handy to see how two objects fits to ...

kcleung wrote:Should we discuss the intention of merging the assembly branch into FreeCAD after 0.16 with the core developers NOW?

IMHO it's not the time yet... I'm not an adherent of idea to merge in whatever state it is, so I'd like to propose to do it on next "test request"...

kcleung wrote:So are you going to merge the assembly branch into FreeCAD after 0.16? That's wonderful!

Note that it's mostly our desire, but we haven't discussed it with core developers yet...

e.g. if the input forbids angle more than 360°, the code will likely allow to input 359 rad... I was wrong about that... Its name is Precision::Confusion() but you can't use this in the core system since it's part of occ and this we don't want there. It would be nice to have such constant for FreeC...

wmayer wrote: But that's standard behaviour of all Qt spin boxes. Trying to make an adaptive step size can be very tricky.

not really, it's QuantitySpinBox and it should be enough to slightly alter the stepBy()...

<<=== the parenthesis seems wrong Seems both variants doesn't make scenes... Btw, the expression error text must be adjusted to the actually used operator. I'm not sure if exactly this line is intentionally or not, but there seems to be bug around there... e.g. if the input forbids angle more than ...

To find all cases where quantities with doubles is compared can be easily detected by using the keyword "explicit" in front of the constructor of Quantity Tried it... lots of hits in QuontityParser, but I haven't dig them any further — there were tones of them. This is already fixed in git commit 8...

Currently if a quantity is compared against a double (e.g. Precision::Confusion()) it will likely results in an expression with message "The error message is: Quantity::operator <(): quantities need to have same unit to compare". In the FreeCAD this can be triggered e.g. by this: Create a Pad Switch...

Thanks for reporting. I'm not positive why the bug doesn't triggers for us.. may be some dark magic around QApplication::notify working a bit different on windows and linux...
Pushed to git...