Hi Guys,
I would suggest you concentrate on staying in sync with master, I will merge your changes in my assembly-next branch from time to time.

I really appreciate your work on that. Its really important and make the assembly possible (beside its the right way to do Part Design ;9 )

Mhh,
I have no trouble so far,
check out the latest commits in try again. Maybe a not committed file, but this commits were just a merge and a fix, so no new files....

If it still not go through cMake, try to find out what file and let me know...

Remember:
ViewProvider can have additional Properties. So, if there is a long discussion about the right way, just make it configurable.

And if you use some kind of margins, never use absolute values. Always try to use things like 1% of the BoundingBox...

Ok, leave the QPoint out of the interface, I will maybe add later a 3D point for drops in the 3dView on special geometry (represented by a ViewProviderGeometricObject) which have to be handled differently anyway...

Use ViewProvider or VPDocumentObject as you wish.

* Undo can not circumvented, if the programmer do not open a transaction the changes will appended to the open one or a anonymous transaction will be created automatic. * QPoint: you need it to determine the hit Item in the tree, then you need it... And for opening a context menu (see last point) * ...

Ah, I see..

The old interface is used mainly by the Group objects in FreeCAD. The new mimic will be broader but, as you saw already, needs more love. I stopped it till I get more of the basic Assembly stuff done to really use it..

jriegel, while you are around, could you remember what was the intention of introduction of the new API? Anything specific or just general enhancement? Have you gonna to add the corresponding API for drag? Is it essential to have the QPoint &pos in the call (I don't see how it could be interpreted ...

Sure, but you have to do always do some DAG processing (searching) which one is you tip. Or you just save a pointer to it.

The Detail interface replace the usage of SoFCSelection node and gives you more control. Which kind of (Inventor) Detail shows what kind of string is completely on you. FreeCAD selection is only interested in an Subelement string. The rest is local to the viewProvider...

Sure, replace the name!

If you see a document as a DAG, it can have more then one root objects, which are in no way easy to determine. Tip was introduced for a multi-document environment. A pure PartDesign document will have the Tip pointing to a Part. A Assembly document to the root Assembly/View. A FEM document to the An...