Mario Pascucci Wrote:So, including connectivity to primitives is surely a good starting point, but at the present state of library it can lead to unwanted/weird connectivity issues: you need to delete some connections derived by primitives in final part. This is a major issue in autodetect strategy. In my connection library some parts are inserted only to avoid autodetection, that includes unwanted and wrong connection points.
Exactly, this is why I use the SNAP_CLEAR meta in LDCad in order to drop (some) of the inherited information in certain files in order to redo it in the local file.
Another problem might be the continuation of e.g. a hole present in a primitive (e.g. stud with hole) into a higher part. The stud with hole primitive might have the hole defined as it's used manytimes as is (so not it's only 4ldu deep). But in some parts it continues into the higher structure (e.g. a 1x1 round brick) and has to be dropped / redone.
But in the end the inheritance system is mostly very positive, you just need to 'certify' all bricks just like with BFC mechanism.