Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/11/2024 in all areas

  1. UPDATE I found the solution... sourceDoc.SendCommand "_copybase" & vbCr & basePoint(0) & "," & basePoint(1) & "," & basePoint(2) & vbCr Instead of... sourceDoc.SendCommand "_copybase" & basePoint(0) & "," & basePoint(1) & "," & basePoint(2) & vbCr 'vbCr' was required after initialising the command and before the base point coordinates are entered.
    1 point
  2. This is partly a data problem. You might be able to create a dynamic block, which you can move and scale to fit the various sizes of column (or footing or whatever). The block contains attributes for each piece of data, which you can read/export fairly easily. It's also easy to select a specific type of block, put them in a set, and process each one. It's also partly a drafting problem. With different lengths for the codes, it's hard to use separate attributes, because they'll overlap. You could include code to input/validate and output/filter a group of codes, but there's no way to prevent someone from manually breaking your system. I can't tell what the "position numbers" mean, so I can't tell you how to generate them. There is software out there for drawing and labeling rebar. Some of them cost money. I don't know if you can generate the labels the way you need to, or if there's a way to customize them. AutoLISP has the benefit of being free (apart from the time you spend writing and debugging it), and it's infinitely customizable.
    1 point
  3. I got it working It works great. Thank you.
    1 point
×
×
  • Create New...