Hey Mick,
You are right, dcs_2dplan does work. Sorry for the bad info.
My code for sections works like this:
http://SmartLister.com/files/section.aviNo audio, 8 meg.
You mentioned hatching.
That is why I automate the section command "with" my automated dview code. Section produces regions. They are always closed and dependable to hatch. I have not added the hatching code yet either. I am getting it done. Just not as elegant and professional as you.
In some ways I have no issue with blocks. Because I am using dview with clipping planes ACAD puts everything there I need. The only time blocks are an issue is if I want to run the section command too.
The views generated are dview with only the front clipping plane turned on. If they do not want the beyond entities that can always add a back clipping plane in their viewport later. No one ever does this in the cabinet field though. However, I think I am going to have to do that on the project I am working on now. I am creating a new type of wall for buildings and I am going to want to automate a single wall in view, without seeing the walls beyond. I really like the way my code runs because it does not generate any additional entities in ACAD, unless they run the section command with it. When they change the model the view updates automatically, except for the section regions ones. But you do not need to use that particular utility all the time. It is only when there is bleed through of features beyond inside the solids.
You may notice in the video that I create a viewport too. This creates the layer for the viewport, "vports", sets the color, and then after they pick the points for the viewport it sets the viewport to hide on plot and clears dviews clipping planes. I do this because once you create a view in a viewport with dview and set clipping planes, afterwards, for weird reason, when you create a new viewport ACAD puts your previous clipping plane settings in the new viewport. You have to run dview at the command line and clear the clipping planes to see properly in the new viewport, so I just run it for them when I create the new viewport. Hell man, much of the this code is sendcommand. I am surprised it works as well as it does, but soon I need to automatically dimension everything. I hope it does not fall apart or become overloaded at that point.
