#Draftsight 2019 code

I think would be an interesting discussion if/how to integrate pivy trackers in draft since a major reorganization of its code could be on the horizon. I know you know them probably better than me. perhaps they rely more on Part to calculate the tracker object, to match exactly the document object they emulate. This is less or more how Draft Trackers work. If such a compound is active, all created Draft objects go in it automatically. We could try to make a Draft compound object that behaves like an App PArt or PartDesign Body or BuildingPart: if you double-click it, it becomes 'active'. Might be a good time to rethink the whole Draft Edit tool into something more ambitious So when an edge is moved, we know we need to recreate the face too. So one should first have a good sorting algo, that would find, for example, all faces that are part of a solid, or all edges that are part of a face. A compound can contain just about anything: Solids, shells, faces, edges and vertices. The main issue is sorting and figuring out what is inside a shape.

In fact, one could imagine a universal edit tool, that would work on just ANY FreeCAD shape. In any case, having one compound object that holds many entities is an interesting thing to explore. Grouping several objects into one is easy: Select many, create a compound, create a simple copy, delete the compound and the many objects. We should at some point do some good testing to assess how strong is really the impact of having, say, 1000 small individual line objects rather than one compound which holds 1000 lines. It seems, though, that this is really the only way to address performance issues with document objects without rewriting things in C++. I don't know if that makes it any clearer, or if what I'm describing is useful here. Finally, the trackers used for the rotation operation are destroyed. Then the geometry is turned back on, reflecting the permanent change. Once the user completes the rotation, the transformation would be applied to the original document geometry. It may be advantageous to hide the original document objects during the rotation. This single tracker would handle their rotation for the duration of the MMB click / drag operation. In this case, the selected elements could be converted into a custom tracker built on pivy_trackers. The task is the rotation of those objects. The command-task paradigm is simple: The command is a middle mousebutton click and drag when multiple 2D objects are selected. Let's say we wanted to create an adhoc rotation tool that lets the user rotate all selected lines about the center of the selection by clicking and dragging the middle mouse button (no task panel is needed).

#Draftsight 2019 update

Complete task and use the final state of the trackers to update the original document objects (or abort, destroying the trackers)

Perform the editing task operations using tracker objectsДҐ. Initialize the task by converting the document objects to pivy trackers or creating a framework of trackers to represent the editing operationsД¤. Click / execute a command to run a task which modifies / edits the objectsДЈ. Thus, the current workflow for trackers is:Дў. So, I really think I'd view pivy_trackers more as an editing tool that's generated on-demand and not constantly. Really, I think in the end, you'd be talking about rebasing the Draft tools to use trackers whenever geometry is modified, then update the document geometry when the operation is complete. I suppose a shim / wrapper class could be added, though.? Again, without a concrete use case to really look at, it's hard to say. and maybe you could use an existing draft tool on a tracker object, but I didn't really design it with that sort of thing in mind - the tracker object doesn't have a document object API for that level of compatibilty. Hard to say without a concrete use case.ДЄs far as using draft tools on trackers, pivy-trackers could be used *by* the draft tools, I suppose. However, I think it becomes more difficult to manage that well without using a 'task' as a context to mange their creation / destruction. In the end, it's nothing different than what's being done to render the document objects in the Scenegraph. You could load in a DXF and render the entire thing as trackers. It's not to stalk you, I'm really curious to understand how do you envision it I mean, could we have a document object that stores geometry like a whole dxf, but represent it through pivy trackers constantly? Or just represent it as a compound but turn it into pivy trackers when we need to edit it? And how difficult do you envision to use draft tools on it? And draft snap?