AutoNumbering
[I sould suggest you use the USERI1 and USERI2 System Variables instead, i.e. the Integer rather than Real-number versions.]
Kent Cooper, AIA 
Accepted solution
@Anonymous wrote:
....
When using the macro, the text "setvar" will appear and will rotate 1 degree clockwise per click.
....
That macro was written assuming that the current Text Style has a fixed height. So the Text command doesn't ask for one, and if your current Style doesn't have a fixed height, that is throwing off the inputs, making parts of the macro into answers to the wrong prompts. If you don't have it set a Style for you, you need to make sure the Style you want is the current one before you pick on the menu item. If that Style does not have a fixed height, you will need to add into the macro a response to the height prompt:
*^c^c_text;\YourDesiredHeight;;$M=....
Consider also forcing it to use 0 rotation, if that might not be the current rotation. In older versions, 0 is always the default, so that semicolon [= Enter] just before the $M puts the rotation at 0, but in newer versions it remembers the latest rotation, which is what you'll get by accepting the default, so you may want to force it to 0:
*^c^c_text;\YourDesiredHeight;0;$M=....
Kent Cooper, AIA
@Anonymous wrote:
....
Is it possible to attach this feature to a block?
....
If I understand what you mean by that, you could make a Block with an Attribute, and use an INSERT command instead of TEXT, having the Diesel expressions supply and increment the value for the Attribute. That way, the Style and height and rotation of the text part would be part of the Block definition, and you wouldn't need to deal with them in the macro.
As with the question of whether the Text Style has a fixed height, if you do it with a Block with Attribute, you would have to be careful about whether the Block is defined for uniform scaling, and supply the right number of answers to scale factor prompts, etc. So how it would be written exactly depends on the way the Block is defined [or whether it's always a Block in the drawing or might be an external drawing file], whether it has more than one Attribute, etc.
Kent Cooper, AIA
@SeeMSixty7 wrote:
.... also keep in mind these variables may already be being used by someone else. They may also contain values from previous use as a result. Something you can do is create an initializer in the USERS# variable that tells your macro which one to use....
I also thought of the fact that they might be used by other routines. If you find things don't work as expected, or something else doesn't work right after you've used this macro, and if that could be the reason, you could try using USERI4 and USERI5 instead of 1 and 2, on the assumption that the lower numbers are likely to be more "popular" and therefore more likely to be called for in other routines.
BUT if you are thinking of using the String ones USERS1-USERS5, bear in mind that while the Real-number ones and the Integer ones are saved in the drawing, for some unknown reason the String ones are not! If you use USERIx System Variables, you can close a drawing, and open it again later and carry on using the same macro and have it increment continuing from where you were before. But you can't save some kind of initializer or indicator in a USERSx one and have it "survive" into a subsequent editing session. One way to get around that could be to use Environment Variables, but I don't know whether they're a possibility in LT.
Kent Cooper, AIA