Parametric Text to display value

[mark4017]

i would like the parametric text to display just the value of a parameter without the unit of measure,  i want the value to be displayed not the expression 

[Warmingup1953]

Expression and value probably can't be swapped, I am almost certain. In what case do you find this Standard inappropriate?

[mark4017]

i was hoping there would be an option  to do something like  value -(unit) 

[HughesTooling · Accepted solution]

Looks like Value/units works.

[mark4017]

that worked , thank you

[ccyokes]

If you find a way to display 1.5 as 1 1/2 instead, I'll be glad to share with the other posts on this parametric text. That's the last remaining unknown I am aware of that the official documentation decided wasn't important to include.

For anyone who happens to see this post instead of the others first, an apostrophe can be typed by using the escape character \. For example 'can\'t'. This also works to add a tab or new line with \t and \n respectively. Since parametric text is forced and not optional, this escape character is critically important to be able to use a textbox as... a textbox.

Probably a bug that will get patched out, but for now at least you can use the textbox shortcut to start a sketch and then the textbox is normal instead of parametric. For me (don't remember if this is default or not) this is done by pressing Ctrl+T while on the Solid tab (rather than the sketch tab).

[ChrisHeerschap]

Huh, unintuitive and undocumented, but it does work. Thank you!

Would be nice to be able to change the output units - if I enter "4 in" in a parameter that is in a metric document, the parameter expands to '101.6 mm'.

Now how about controlling the formatting of the number, like {param.value:.3f} in the Parametric Text plugin? So 1.093347 shows up as "1.093".

Or zero padding a version number like {_.version:02d} so design version 4 displays as "04".

Both are basic capabilities that I use regularly.

Was initially excited to see that plugin's capability integrated into Fusion but quickly discovered it's far more limited. Looks like I'll be continuing to use the plugin for the foreseeable future.

[ChrisHeerschap]

First, a correction - 1.093347 would display as 1.093 by default. Thought this might be set in the document settings, but can't find it there.

Digging through the docs, I did find that you can use the "floor(param)" function to drop the decimal. The manufacturing function reference lists "floorto" which drops anything past the number of decimal places specified, but this doesn't look to be supported in the design tab so can't be used in parametric text.

You can fake around it by using "floor(param*10)/10" to get a single decimal point - or "round(param*10)/10" depending on how you want it to work. eg, 90.25 becomes 90.2 with floor and 90.3 with round.

You can fancy it up by creating a unitless user param "decimals" and then change the above to: "round(param*10^decimals)/10^decimals". Big problem here is if you want four, tough cookies, because of the correction at the top, you run out at 3 decimal places. Not likely a real problem, (for me at least) but still a limitation.

Setting decimal places and dropping the units then becomes: "round(param * 10 ^ decimals) / 10 ^ decimals/ mm". It works, but... ewww.

It sure would be nice to just be able to use printf formatting codes which are so native for those of us who understand them. (like the PT plugin!)

Still haven't figured out how to reference document-specific things like document filename version, the active configuration description, or the comment on a parameter.

[ChrisHeerschap]

You could probably write a really ugly function that converts "1.5" to "1 1/2" but it would be really non-trivial, especially since we're missing the most basic functions like fp() to return the floating point portion of a value, so returning just the ".5" of "1.5" with the available functions itself is tricky enough.

So I managed to write this up which works only for quarters. (and it turns out, not even that)

Create parameter	Value
fp	( floor(param * 100) - floor(param) * 100 ) / 100
fraction	if(fp == 0.25 mm; '1/4'; if(fp == 0.5 mm; '1/2'; if(fp == 0.75 mm; '3/4'; '')))
text	floor(param) / mm + ' ' + fraction

Anything other than an exact quarter gets dropped, and for some reason the "3/4" case fails, it returns "fp" of 0.75 mm but the "if( fp = 0.75mm;" conditional fails. It seems like fp is somehow different. Stumped on this one but giving up after fighting it for a bit.

Might be a simpler way to do it but I'm not seeing it based on the documentation and my own experimentation.

[HughesTooling]

@ChrisHeerschap You can get the floating point portion using parm % 1mm but it doesn't work in the if statement correctly. Oddly it only works with the quarters less than 1 and 1.75mm but fails with pretty much all other numbers ending with a quarter! Don't know if there's some rounding going that shows as the value but the if statement is using an unrounded value.

[john.koerner]

This solution is very close, but it fails due to how Fusion internally stores some of these values and due to floating point representation of the numbers.  We can change the functions a bit to achieve the desired result by working with whole numbers that have been rounded to ensure accuracy.  

fp	round(Test % 1 mm * 100)
fraction	if(fp == 25 mm; ' 1/4'; if(fp == 50 mm; ' 1/2'; if(fp == 75 mm; ' 3/4'; '.' + fp)))
text	floor(Test) / mm + '' + fraction