How to suppress leading zeros dimensions and increase decimal places in detailing?

Greetings:

A family table of a shim has been created where the thickness and
tolerances have 4 decimal places in the model.

When detailing it with #table, #repeat region, #simple the values show
leading zeros and with only 3 decimal places instead of 4. Could
someone please remind me how to suppress the leading zeros and increase
the precision from 3 to 4 decimal places?

All dimensions are in inches.

tolerance_standard = Ansi
lead_trail_zeros = std_default
lead_trail_zeros_scope = dims

VALUES SHOWN IN TABLE | SHOULD BE SHOWN AS
0.001 ± 0.000 | .0010 ± .0001
0.003 ± 0.000 | .0030 ± .0003
0.005 ± 0.001 | .0050 ± .0005
0.010 ± 0.001 | .0100 ± .0010

Any help would be greatly appreciated.

John

 

Greetings:

A family table of a shim has been created where the thickness and
tolerances have 4 decimal places in the model.

When detailing it with #table, #repeat region, #simple the values show
leading zeros and with only 3 decimal places instead of 4. Could
someone please remind me how to suppress the leading zeros and increase
the precision from 3 to 4 decimal places?

All dimensions are in inches.

tolerance_standard = Ansi
lead_trail_zeros = std_default
lead_trail_zeros_scope = dims

VALUES SHOWN IN TABLE | SHOULD BE SHOWN AS
0.001 ± 0.000 | .0010 ± .0001
0.003 ± 0.000 | .0030 ± .0003
0.005 ± 0.001 | .0050 ± .0005
0.010 ± 0.001 | .0100 ± .0010



Try the following
default_decimal_places=4 (in config.pro)
lead_trail_zeros = std_english
lead_trail_zeros_scope = all
and leave tolerance_standard=ANSI

Since drawing options are post facto and operate, generally, forward not backward, you'll probably have to delete and reinsert the table. You could save it first as a table file then recreate it 'From file'.

 

David,

Thanks for your suggestion and help.

I just find out that for undknown reason the parameter
model_digits_in_region has been set incorrectly to "no". After
correcting the value to "yes" the table displays the values as I
expected.

Many thanks for your time and help.

 

David,

Thanks for your suggestion and help.

I just find out that for undknown reason the parameter
model_digits_in_region has been set incorrectly to "no". After
correcting the value to "yes" the table displays the values as I
expected.

Well, I learned something new. Thanks!