Text TAG

[MichaelT_123]

Hi Fellows,

… as I promised in:

https://forums.autodesk.com/t5/fusion-design-validate-document/text-bounding-box-and-parameterizatio...

Here is the one possible, not necessarily elegant, but potentially workable method of creating a framed text TAG (a label).

The attached file shows the main tricks, which I hope should be obvious to most. The following points should help to clarify the design intent even further:

• There are a couple of user parameters driving the design
• Dimensions are based on a font height (as referred to in the text dialog box)
• Alongside various factors (descriptions in the respective UParams comments)
• Font factors should be 'customized' based on the selected font
• The design flow assumes that the font is of a mono-spaced family.
• If not, you must rely on your 'good luck.'
• The actual text can not be parametrized, so it must be entered manually
• Consequently, counting the text length is also required (n_t param)
• It is advisable to convert the TAG to direct modelling form before including it in the destined design.
• As this would avoid unnecessary clattering of the latter.
• The solution is about a fast TAG creation rather than a fully parametric workflow.
• The method can be 'customized' as per requirements.
• Even a multiline TAG option could be easily implemented.

As the epilogue (or one would hope prologue),… a couple of additional points:

• The above method can be API scripted, presenting to the user a 'fool-proof' solution
• I even committed one for the previous incarnation of sketchTextObject
• But because this particular area is in the 'panta rhei'  state, it would be a lavish effort
• The current text graphic procedure already has necessary data, which, when exposed, would give essential handles to deal with text (e.g. precise outline bbox, indentations)  
• It is perhaps a couple of lines of code
• Currently, the 'string' data type is not permitted as a user parameter.
• Upgrade in this area, …. and parametric text can become a reality in the basic design flow, … without external scripts.
• Thus, … bang on F360 doors!

The attached file can be used in any legal activity you can fathom. Play with it as you wish … but responsibility is yours!

Attached files:

TextTAG.f3d                 F3D              (0.2MB)          https://a360.co/49bkq0w 

Regards

MichaelT

[MichaelT_123]

Hi Fellows,

… as I promised in:

https://forums.autodesk.com/t5/fusion-design-validate-document/text-bounding-box-and-parameterizatio...

Here is the one possible, not necessarily elegant, but potentially workable method of creating a framed text TAG (a label).

The attached file shows the main tricks, which I hope should be obvious to most. The following points should help to clarify the design intent even further:

• There are a couple of user parameters driving the design
• Dimensions are based on a font height (as referred to in the text dialog box)
• Alongside various factors (descriptions in the respective UParams comments)
• Font factors should be 'customized' based on the selected font
• The design flow assumes that the font is of a mono-spaced family.
• If not, you must rely on your 'good luck.'
• The actual text can not be parametrized, so it must be entered manually
• Consequently, counting the text length is also required (n_t param)
• It is advisable to convert the TAG to direct modelling form before including it in the destined design.
• As this would avoid unnecessary clattering of the latter.
• The solution is about a fast TAG creation rather than a fully parametric workflow.
• The method can be 'customized' as per requirements.
• Even a multiline TAG option could be easily implemented.

As the epilogue (or one would hope prologue),… a couple of additional points:

• The above method can be API scripted, presenting to the user a 'fool-proof' solution
• I even committed one for the previous incarnation of sketchTextObject
• But because this particular area is in the 'panta rhei'  state, it would be a lavish effort
• The current text graphic procedure already has necessary data, which, when exposed, would give essential handles to deal with text (e.g. precise outline bbox, indentations)  
• It is perhaps a couple of lines of code
• Currently, the 'string' data type is not permitted as a user parameter.
• Upgrade in this area, …. and parametric text can become a reality in the basic design flow, … without external scripts.
• Thus, … bang on F360 doors!

The attached file can be used in any legal activity you can fathom. Play with it as you wish … but responsibility is yours!

Attached files:

TextTAG.f3d                 F3D              (0.2MB)          https://a360.co/49bkq0w 

Regards

MichaelT