
Differrent increments for line and curve(or spiral when its supported in Trails). Also added horizontal geometry points to list.
Really starting to look like something. I think about getting spirals functioning again, but I'm too focused on getting the editor sorted out.HakanSeven12 wrote: ↑Tue May 28, 2019 10:48 amDifferrent increments for line and curve(or spiral when its supported in Trails). Also added horizontal geometry points to list.
Waiting for itJoel_graff wrote: ↑Tue May 28, 2019 11:55 amReally starting to look like something. I think about getting spirals functioning again, but I'm too focused on getting the editor sorted out.
Its not important for basic road but in intersections you need to edit those lines by manually for seperate two road sections(or other surfaces like earthwork). Or you need to edit for different situation.Joel_graff wrote: ↑Tue May 28, 2019 11:55 amI was just thinking about your cross-section lines. You obviously generate separate Part.Line objects for each one, but do you need them as actual objects? Or are they there strictly as a visual reference? I ask because it is possible to do that without creating objects that show up in the tree view - but it means directly manipulating the scenegraph (which is what I'm dealing with right now...)
So what does 'editing' involve? I'm thinking about rolling that functionality into the horizontal alignment tool, since it really seems like it ought to be done there, but I could be wrong... In any case, the lines could be easily generated as scenegraph nodes to be switched on / off as needed - far more efficient than manipulating Part.Line objects.HakanSeven12 wrote: ↑Tue May 28, 2019 12:06 pmIts not important for basic road but in intersections you need to edit those lines for seperate two road sections(or other surfaces like earthwork). Or you need to edit those lines for different situation.
I dont have enough information about python and FreeCAD. I learned python when I started this workbench from an 1 and half hour video. Coin3D is stranger thing for me.Joel_graff wrote: ↑Tue May 28, 2019 12:41 pmSo what does 'editing' involve? I'm thinking about rolling that functionality into the horizontal alignment tool, since it really seems like it ought to be done there, but I could be wrong... In any case, the lines could be easily generated as scenegraph nodes to be switched on / off as needed - far more efficient than manipulating Part.Line objects.
I guess the idea would be that you'd create a non-visual python object (not a FeaturePython object) to manipulate the data as required and simply update the scenegraph nodes for the visualization. Unless having each cross section line appear in the treeview as a separate object is really helpful to the user, I would think the editing could be managed at the Coin3D scenegraph level, rather than as Part.Line objects.
I can add a group and move all wire in to it than make its visibility false.Joel_graff wrote: ↑Tue May 28, 2019 12:41 pmThat said, it's not as straightforward as building lines or FeaturePython objects, so I'm not suggesting going after that at the moment. But you may want to consider it in the future to eliminate cluttering the treeview.