Hi realthunder, just a request, maybe already in development: is it possible to implement a sort of copy&paste aux function to replace two elements on a constrain? If you are using Linux, there is already a keyboard shortcut to help with this process, it works like this Select a geometry elemen...

But please can you check why it's impossible to use the trim tool to trim edges? Currently, the attached geometry is just a faithful projection of the external edge. There is no way to make any change on that. I'll see if I can extend it to support trimming. BTW, I saw somewhere else that you are a...

OK ... so ... the constraint I use is now of type App::FeaturePython, to which I add an App::PropertyPlacement (called AttachmentOffset): I see. If the sole purpose of this constraint object is to provide an offset, then it makes more sense to change it to App::PlacementPython, simply like this. co...

What I understand from this is that this dragger temporarily disables the App::Placement of any object, and replaces it with its own Placement. And when it's done, it stores the value in the App::Placement of the object ... except that the Expression Engine doesn't allow the overwrite. There is som...

Just right click the item in the tree view and select 'Transform'. Or is there other thing you want? I rather though about shamelessly copying that cool feature It's a TaskCSysDragger isn't-it ? Yes, but its usage is kind of complex, which is why there is ViewProviderDragger. Any view provider deri...

emills2 wrote: ↑Tue Feb 19, 2019 12:50 am

realthunder wrote: ↑Tue Feb 19, 2019 12:09 am The error message happens when some python code wants to retrieve geometry shape

that was my guess too, but the error doesn't tell me where to look. selection, subelements, etc?

Bug fixed. Are you testing with your own build of my branch?

completely different topic related to usage of FreeCAD_assembly3. is this thread the correct place for all FreeCAD_assembly3 questions? Somehow missed your post in the middle. Just saw it. Yes, any question related to asm3. It will be easier to identify the problem if you can send me the file. In a...

Can you tell me if my perception is close to the reality of Asm3 (or its future?) and what I did not understand? Your understanding is pretty much okay, just a few small points. Asm3 retains only the simplified geometries of the subassembly objects, for example the functional surfaces already used ...

In AWS (or Asm4) there is an App::Placement called 'Offset' for each part, that must be edited and parameters set numerically, but that placement could also be manipulated by the dragger in the same manner as in Asm3. This would be a very useful feature, and combined with the LCS snapping would all...

next step: any part with 3 coincident plane constraints. block type object (20% - 70% of remaining real world model constraints) this covers objects that could have had an LCS, but were not sufficiently predictable. in this case, it's easier to match 3 plane than to create the special case LCS. but...