Why does autostack stack numbers before and after a pound sign?

[eganz]

"AutoStack only stacks numeric characters immediately before and after the caret, forward slash, and pound sign."

I like the autostack function for typing fractions, but do not like that it also stacks pound signs.  For example, in electrical jargon, we often describe a feeder as "2#12 & 1#12 grd - 1/2" C."  Autostack corrects this to "2/12 & 1/12

GRD - 1/2" C." (but with the fractions stacked of course; the forum text editor doesn't allow me to show that stacking in here).

Example:

The stack properties dialog box allows for some formatting and defaults, but I don't see a way to change this specific item.  Is there a way to keep autostack on for fractions, but off for the pound sign?

[eganz]

"AutoStack only stacks numeric characters immediately before and after the caret, forward slash, and pound sign."

I like the autostack function for typing fractions, but do not like that it also stacks pound signs.  For example, in electrical jargon, we often describe a feeder as "2#12 & 1#12 grd - 1/2" C."  Autostack corrects this to "2/12 & 1/12

GRD - 1/2" C." (but with the fractions stacked of course; the forum text editor doesn't allow me to show that stacking in here).

Example:

The stack properties dialog box allows for some formatting and defaults, but I don't see a way to change this specific item.  Is there a way to keep autostack on for fractions, but off for the pound sign?

[vinodkl]

Hello @eganz 

You can turn off autostart completely by typing in the command "MTEXTAUTOSTACK" and turning it "off". But I'm sure if you can only disable the autostacking with # key 🙂

[vinodkl]

Hello @eganz 

You can turn off autostart completely by typing in the command "MTEXTAUTOSTACK" and turning it "off". But I'm sure if you can only disable the autostacking with # key 🙂

[Kent1Cooper]

A fairly simple workaround, if you can remember to do it this way, is to first enter the content without the # signs:

then go back and put them in:

and they'll "stick":

It's the actual typing of the space [or Enter for a new line] immediately after the number after the # that triggers the stacking.  So if the space is already there after the number, and then you insert the # inside, stacking is not triggered.  Note that if numbers surrounding a # are the very end of the content, and you conclude with Ctrl+Enter or by picking out in the drawing area, the stacking doesn't happen.  Only space/Enter right after the number after the # causes it.

[Kent1Cooper]

A fairly simple workaround, if you can remember to do it this way, is to first enter the content without the # signs:

then go back and put them in:

and they'll "stick":

It's the actual typing of the space [or Enter for a new line] immediately after the number after the # that triggers the stacking.  So if the space is already there after the number, and then you insert the # inside, stacking is not triggered.  Note that if numbers surrounding a # are the very end of the content, and you conclude with Ctrl+Enter or by picking out in the drawing area, the stacking doesn't happen.  Only space/Enter right after the number after the # causes it.

[pendean]

.... or a simple tap of the backspace key after the fraction is created (when you add a space after it) will automatically undo it, PLUS you can keep typing (and that extra space is never lost to boot).

Way simpler to learn to do "muscle-memory" style than any of the other tips so far 🙂

[pendean]

.... or a simple tap of the backspace key after the fraction is created (when you add a space after it) will automatically undo it, PLUS you can keep typing (and that extra space is never lost to boot).

Way simpler to learn to do "muscle-memory" style than any of the other tips so far 🙂