Limiting Decimal Spaces for Areas

[dshall]

Does anybody know how to limit the decimal spaces for areas?  I am  not sure if my landscaper needs to put in 326.3468524 s.f. of sod.  I think 330 sf would be accurate enough.

 

 

bbb minimize decimal numbers 1.plan

[Joe_Carrick]

Only by using a user macro instead of the one Chief provides.  This has been discussed before and the macro posted in another thread.  Search the forum

[kMoquin]

Yes!

I'd love a setting for this.

The builder asked me to confirm that we needed 85.4541016 square feet of tile for the bathroom.

I asked him if my estimate was not accurate enough.

[HumbleChief]

My question is, how did this ever get out off the software engineer's desk and in to the program? And then remain in the program after a couple of updates? Really strange thinking IMO.

[Joe_Carrick]

OK guys,

 

Create an "Owner Context" - "Evaluated" macro named "Area Rounded" with the following contents:

x = area.round(0)

 

then use that macro in the Polyline Label.

 

I agree that 7 decimal places is too much and Chief should change that to 2-3 decimal places but with a user macro you have control.  In addition, you actually get the numerical value so it's possible to do math calculations within the macro.

[dshall]

......

 

....Create an "Owner Context" - "Evaluated" macro named "Area Rounded" with the following contents:

x = area.round(0)

 

then use that macro in the Polyline Label.

 

....

 

 

Joe,  I wish I new how to do what you are recommending,  but I don't.  i am not a programmer and I do not have time to learn.  I am looking for the answer.  I would like to hire you in about 2 weeks to get this crap worked out and then I will share in a video with others.

 

I wish the designers and the  programmers could stick to what they do best.

[dshall]

My question is, how did this ever get out off the software engineer's desk and in to the program? And then remain in the program after a couple of updates? Really strange thinking IMO.

I don't get it either.  

[dshall]

Yes!

I'd love a setting for this.

The builder asked me to confirm that we needed 85.4541016 square feet of tile for the bathroom.

I asked him if my estimate was not accurate enough.

 

LOL,  I am  going through this now with a site analysis of pervious and impervious areas.  I do not need any decimal spaces,  I am not a mechanical engineer.  The closest tolerance I am expected is to the whole number.

[kMoquin]

......

 

Joe,  I wish I new how to do what you are recommending,  but I don't.  

DSH just paste the text Joe provided in to the "Value" of the macro and select "Owner Object" from the context drop down.

 

Thanks Joe !!!!

[kMoquin]

and just change the (0) to the number of decimal places you want

i.e. x = area.round(1) gives you x.y as the output

x = area.round(2) gives you x.yy as the output

[dshall]

DSH just paste the text Joe provided in to the "Value" of the macro and select "Owner Object" from the context drop down.

 

Thanks Joe !!!!

 

Would it be possible to show a picture of the macro with Joe's fix shown and a pic of where I am to find this macro?  Thanks.

[HumbleChief]

Scott, see if this helps

 

[kMoquin]

here you go

The macro "Area Rounded" is one I created by clicking the "New" button in the DBX

[Joe_Carrick]

Would it be possible to show a picture of the macro with Joe's fix shown and a pic of where I am to find this macro?  Thanks.

Here are pics.

[HumbleChief]

Here are pics.

Joe you're showing area.round(0) instead of x=area.round(0) is the x= needed?

[Joe_Carrick]

Scott,

 

You might want to look at the June2016 Macro of the Month - Area_Perimeter_Volume since it already does all three (2 decimal places)

[Joe_Carrick]

Joe you're showing area.round(0) instead of x=area.round(0) is the x= needed?

only if you wanted to perform additional calculations.  A macro returns the value of the last line.

 

So if you wanted to multiply by some other value you could do this:

 

x = area.round(0)

x/3

 

which would display 1/3 of the area but that wouldn't be rounded.  If you wanted the result rounded you would change it to:

 

x = area

(x/3).round(0)

 

or you could write the macro as

 

(area/3).round(0)

[HumbleChief]

only if you wanted to perform additional calculations.  A macro returns the value of the last line.

 

So if you wanted to multiply by some other value you could do this:

 

x = area.round(0)

x/3

 

which would display 1/3 of the area but that wouldn't be rounded.  If you wanted the result rounded you would change it to:

 

x = area

(x/3).round(0)

 

or you could write the macro as

 

(area/3).round(0)

Thx

[Joe_Carrick]

BTW, some Polyline based objects (Roads, Driveways, Sidewalks, Slabs, Countertops, etc) have Default Labels that you can assign a macro to so that any time you create one of those objects it is automatically labeled.  All of those have the area attribute.

[HumbleChief]

BTW, some Polyline based objects (Roads, Driveways, Sidewalks, Slabs, Countertops, etc) have Default Labels that you can assign a macro to ....

Darned if I can find where that default setting might be...

[Joe_Carrick]

Sorry, not for Slabs or Countertops but check this

[DRAWZILLA]

if you have Joe's site package, it does it all for you automatically.

[SNestor]

I tried making this macro...rounded to two places...and the macro works fine...but, I get an evaluation error.  

 

Why would the macro work perfectly but generate an evaluation error?

 

 

[johnny]

My question is, how did this ever get out off the software engineer's desk and in to the program? And then remain in the program after a couple of updates? Really strange thinking IMO.

 

^^^^this.  its crazy since it would probably take all of 2 min. to fix for them.

[dshall]

Thanks guys,  I finally got it.  Some years I am a little slow on the uptake.