- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Thank you for the help this is about to the point that I was able to get to using blocks and attributes. I am not the greatest with constraint variables so you may be able to get the next issues solved quickly as how perfectly you were able to accomplish the first part.
Issue 1: Say if you need to change the name of the structure callout to "4'%%c Outlet Control Structure" using this block will not automatically update the length of the red underline as a regular mleader would. Is there a way to have the red underline part of the leader automatically adjust to the length of text needed as a regular mleader does?
Issue 2: Is there a way to have the leader landing location have a handle. This would help with maneuverability and allow you to move the leader arrowhead location by dragging rather than the move command.
Issue 3: The way you have it setup with the first attribute as layer 1 and the second attribute as layer 2 is perfect. Is there anyway to add it so there's 3 or 4 attributes? This way if one part of the structure were to change you could just edit the individual definition than all of them as a paragraph whole?
Issue 4: Annotation is probably the most important in this problem. The reason being if I have to zoom in on a viewport of a complicated set of utilities I can just change the annotation scale and make a few tweaks if anything overlaps in the process. Before this block idea, I would have to go in and manually move all of the invert information to align with the mleader rim callout.
Again, thank you so much for being able to assist me in this problem! I wish a standard mleader would allow you to accomplish this simple task rather than having to jump through all these hoops just turn 1 line of text onto a different layer.