Generally, point releases (18.2, 18.3, etc) are bug fixes.
Hard to backport this one, I think. It is attached to most of the other cosmetic changes in v0.19.
Generally, point releases (18.2, 18.3, etc) are bug fixes.
Not really, no. HLR provides the list of edges that we draw. Even the old Drawing WB used the HLR routines.freedman wrote: ↑Wed Aug 21, 2019 11:32 am One more question please. Is there a way to disable HLR or skip the HLR process, maybe a switch I could use in a macro? I would like to see what is possible using other approaches for pre or post processing. If there was a FreeCAD version in the past where it was possible to turn it off, I could use that also.
I presume that with HLR disabled we could still get a drawing but with all the lines and dots showing. Hoping that's true.
Thanks
The biggest truth in that thread is "Having a topologically and geometrically correct shape is a must for all occ operations (specially for boolean) ! Sewing is only one fix that should be applied among the others !"freedman wrote: ↑Wed Aug 21, 2019 8:02 pm I'll post this in the off chance it sparks a brain cell. It's old.
https://www.opencascade.com/content/hlr ... mes-faster
We could serialize and save the drawing geometry(lines). We don't do this now - we recreate the geometry on every recompute.freedman wrote: ↑Thu Aug 22, 2019 11:57 pm How about this:
Could we get a geometry list and run it against the HLR list and come up with two files (maybe more), hidden lines and view lines. Does this then happen:
1) The HLR would never need to run again on that view unless the model changes, dimensions come from the stored files.
2) Hidden line displaying would be lightning fast.
3) At document open, the HLR would not need to run, file data would be used.
4) The code required to make the additional files is just logic, no need for complicated processing.
This is pretty common on commercial CAD software. Also with the new link function, this is maybe no bad idea. I have an assembly where 19 parts have drawing in it. When i open this assembly, it loads a pretty long time. But i think this is minor issue and no bug. This is a feature request. Also i can live with that.wandererfan wrote: ↑Fri Aug 23, 2019 12:08 pm We could serialize and save the drawing geometry(lines).
This must be line list, but the idea is not bad. But every line need a property (show/hide). But the drawing has also a property with hide/show hidden lines. Also a drawing need this property in the future. That makes conficts. That is a very big task. Also this all makes only sense when the topological naming issue is solved.freedman wrote: Could we get a geometry list and run it against the HLR list and come up with two files (maybe more), hidden lines and view lines.
The HLR would never need to run again on that view unless the model changes, dimensions come from the stored files.
Hidden line displaying would be lightning fast.
I thought you would get a laugh out of that statement, I was speaking to logic of extracting lines,vertex,ect.."just logic"?
Getting the existing lines, vertices, etc from OCC is pretty straight forward and well documented. We don't look inside the brep file except for loading and saving.