Author Topic: Thoughts on Block Library  (Read 350 times)

0 Members and 1 Guest are viewing this topic.

MSTG007

  • Water Moccasin
  • Posts: 2393
  • I can't remeber what I already asked! I need help!
Thoughts on Block Library
« on: May 13, 2019, 08:55:47 AM »
What are your thoughts on managing / creating a block library? What is the best practice would you say?

Keep all blocks in (one) dwg.

Keep separate dwgs for each block.

The end result would be that the user would access the blocks via the tool palette.


what do you think?
Autodesk Infrastructure Design Suite 2019

MP

  • Seagull
  • Posts: 17400
Re: Thoughts on Block Library
« Reply #1 on: May 13, 2019, 09:49:06 AM »
Keep separate dwgs for each block.
The end result would be that the user would access the blocks via self updating dialog(s).

this
\|// Set goal. Experiment tirelessly until
|Oo| practice has become expertise.  Loop.
|- | LinkedIn | Dropbox

dgorsman

  • Water Moccasin
  • Posts: 2394
Re: Thoughts on Block Library
« Reply #2 on: May 13, 2019, 10:16:14 AM »
When dealing with multiple clients, there may be cases where some blocks need to be different but not others.  When you have multiple blocks defined in a single file it makes managing a default/override arrangement difficult.  I usually prefer individual source files and let the SFSP determine which block is inserted.
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)
      {NextTime(PlanAhead);}
   finally
      {MasterBasics;}

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 6935
  • AKA Daniel
Re: Thoughts on Block Library
« Reply #3 on: May 13, 2019, 10:28:03 AM »
Both

kdub

  • Mesozoic relic
  • SuperMod
  • Swamp Rat
  • Posts: 1367
  • class keyThumper<T>:ILazy<T>
Re: Thoughts on Block Library
« Reply #4 on: May 13, 2019, 04:05:56 PM »
It depends ...
called Kerry in my other life

Sometimes the question is more important than the answer.
#ridesober