Numbered List Using Callouts

[theory.]

My company's standard for listing construction notes is to show each number inside a hexagon so it looks just like the callouts we place in the drawing (see screenshot). The problem is that as you modify, add, and remove notes in the list you have to manually move the numbered hexagons to stay in line with the notes.

I would like to come up with a workaround for having to manually move the numbered hexagons every time we update the notes but I'm not sure how to attack it. I figured the easiest solution would be if you could customize the numbering in an MTEXT numbered list so it shows the number with a hexagon around it but I don't believe that's possible. I also thought about using LISP but I'm somewhat of a novice in writing it, plus the user would likely have to run the routine each time they update the notes (which means they may forget to do so). I guess I'm leaning towards trying to accomplish this task using a dynamic block but thus far I can't figure out how I would make it function properly.

Has anyone ever run into a similar situation and what was your solution? Or does anyone have any ideas on how this could be accomplished? It seems like something that could be done, in theory, and it would certainly add efficiency on projects but I can't seem to come up with a solid solution.

Any help is appreciated.

Thanks!

[pendean]

There is no ability to add shapes inside MTEXT in AuoCAD, even with LISP or other customizations. You can find a font that offers that shapes in all its numbers, but those tend to have a limit as well.
Q: how would a dynamic block be different from a regular block in this instance? Unless your spacing as totally fixed I'm not sure that's a working solution either.

Hang around and see what others suggest.

[richardC38RY]

I think the best way is to do it with a regular block, each block in the drawing of each number will be copies of the same block and you can just click on one, change the number then run the ATTSYNC command which will make all blocks of the same name match it.

[imadHabash]

Hi,

i suggest to make your Notes as a block with attributes.

[vinodkl]

Hi @theory. 

At my office were using a Dynamic block with visibility for the construction notes. Usually, there would not be much of changes in the construction notes project to project and there would be one or two variations in the construction notes. So we have to created 6-7 different variation construction notes and created a dynamic block and change it based on the project using the visibility grips. If in case we want any changes in the construction notes other than what is create for a new project then we can alter it from the block editor🙂

[ВeekeeCZ]

Have you tried to use a table? Numbers in one column, notes in second. Edits might be easier then.

[ChicagoLooper · Accepted solution]

You can use a TABLE (go to Annotate Tab=>Tables Panel=>Table Icon). Combine this a BLOCK with an attribute. Make the block a hexagon. Make the attribute a number centered inside the block.

For the TABLE, make it two columns and as many rows as needed. For the left column: click in top left cell=>Right click=>Insert=>Block=>Select your Hex_Num block=>OK. See image-1.  After inserting the block, click-and-drag the cyan grip to the bottom of Table. At this point, all the blocks will have the same attribute but if you go to Properties Palette, you can edit the attribute. 

Image-1

For right column, enter description as needed. See image-2.

Image-2

When printed, the TABLE looks like this. See image-3.

Image-3

You may increase the height of a row in order to add more mtext or to provide spacing between descriptions. Either way, the Hex_Num block will remain in the Top Center justified position. Since both the block and descriptions have the same Vertical Margin, they will always line up. Customize the height for each individual row as needed.   

Red=Critical factors that make it work. See image-4.

Image-4

[theory.]

Thanks Looper (and Z9E3zK5E). I'll give this a try. The thought of using a table had crossed my mind, briefly, but I was overthinking how I would do it. This seems fairly straightforward. I'll report back.

[theory.]

This worked pretty well. I inserted the callout block into the left column. Using the fill grip to copy the callout block down the column worked like a charm as did changing the number attribute in the properties panel. The only part I struggled with was the vertical cell margin and the text height in the left column which seem to limit how narrow the cell height can be for each row. Even with a vertical cell margin of .04 and a text height of .01, the minimum row height it will allow is .485 so notes that have a single line of text have a larger spacing than all other notes. But I can live with it.

I really appreciate the walkthrough. It was extremely clear and helpful. We'll use this method on our next project and see how we like it.

Thanks!

[ChicagoLooper]

Try making the margins apply to all rows and all columns, this mean the vertical and horizontal margins should be the same for each individual cell.

EXAMPLE: If one cell has a vertical margin of 0.04 and text height of 0.10 then all cells in this ROW will be 0.18 or taller. Why? Because the numbers add up like this: Text height + margin above the text + margin below the text = 0.18. If you want a cell height of only 0.14 you won't be able to shrink the cell down to anything shorter than 0.18. In a case like this, you'll need to find the guilty cell(s) and change the vertical margins to 0.02 or less. Text hgt + margin above text + margin below text = 0.14.

It's good to make all vertical margins the same and by then same, I mean make them all zero.  If you are justifying to Top Center and Top Left then allow your text to 'touch' the top of cell. Doing it this way will allow you to make the ROW height the same height as your mtext height and that's the shortest possible cell height allowed. Later, you may adjust the vertical margins and row heights to get the look you want. 

[sdg]

That worked for me except I don't have the Attributes section in the Table's Properties box. Do you know why? I don't know to change the numbers - 

[sdg]

I now see why - the block has to be a dynamic block. Now it works!