Hide Keyed in Dimension??

[Peter Warcholyk]

Good Morning Folks,

I have two "keyed" in dimensions that I assign to a variable, and then take the absolute value of them.

I assign another variable that I use to add the first two together.

I then construct a generic point and insert the last variable. So far, so good.

How can I prevent the two "keyed" in dimensions from showing up in the report??

In the dimension line, I have selected "None" for the output, yet it still shows up in my report.

Thanks in advance for your assistance.

Best Regards,
ZydecoPete

[T Miller]

Edit prefs/edit window layout turn off comments

[Peter Warcholyk]

T Miller,

Thanks for the quick response; however, unfortunately this did not achieve the result that I was looking for.

The two "keyed" in items still showed up in the report.

Regards,
ZydecoPete

[rebeldude]

You can put them in as a "input" comment. Assign the comment into the generic point. You may have to turn the "report " in comment off too though.. Sometimes it defaults to report on and sometimes it doesn't

[craiger_ny]

Output Report, statistics, both, none. Look for something like that in the dimension block You want "none" You will see this in command mode for that dimension. The option is there for every type of dimension I believe.

Craig

[craiger_ny]

OK here is what you need to do

Change this:

DIM 2 = KEYED IN DIMENSION  OUTPUT=BOTH
AX    MEAS   NOMINAL    +TOL     -TOL      DEV    OUTTOL 
M    2.0050   2.0000   0.0313   0.0313   0.0050   0.0000 ------#-----

to this:

DIM 2 = KEYED IN DIMENSION  OUTPUT=NONE
AX    MEAS   NOMINAL    +TOL     -TOL      DEV    OUTTOL 
M    2.0050   2.0000   0.0313   0.0313   0.0050   0.0000 ------#-----

See what I did?

Craig

[Peter Warcholyk]

Hello Craig,

Currently, my dimension line looks like this;

DIM KEY12= KEYED IN DIMENSION OUTPUT=NONE

The results still show up in the report. This is not a super big deal.
I'm just trying to learn more about pcdmis. There must be a way to "hide" this little @@[email protected]!#[email protected]#[email protected]#$

Thanks for your Input !!

ZydecoPete

[craiger_ny]

Does it show up when you re-execute the program? I use that to keep regular dimensions from showing that I don't want to show and it works. I wonder if for some reason Keyin dimensions are treated differently. That stinks man.

Craig

[djayne]

Use a marked set and unmark the section you do not want to report. -Maybe?

[Matthew D. Hoedeman]

Get the data as a COMMENT~INPUT statement. You can use that data in variable too. Why didn't you show him that method, booger-boy?

[Peter Warcholyk]

Thanks for the advice,

Forgot to mention, I am using ver3.7mr3, reasonably stable.

Craig; yes I have tried to re-execute the program, and it still shows up.

Djayne; I am actually using a marked set. If I "unmark" the keyed in dimension,
then it will not ask me to "key" in a value, and therefore my calculated dimension will not work.
So in order for it to work, the "keyed" in features do need to be marked.

Thanks to All !!

ZydecoPete

[rebeldude]

If you do it as an input comment, it will still prompt you and it will carry it to a generic feature though. honest.. I do it all the time

[craiger_ny]

Get the data as a COMMENT~INPUT statement. You can use that data in variable too. Why didn't you show him that method, booger-boy?

I was thinking that next but I thought what he wanted to do could be done. I don't get it, I use the none option for "fake" dimensions in my bonus tolerance scripting that I don't want to show in the report and it works. I guess Keyin dimensions get a different treatment. At this point I'd do what Matt says and set a variable.

Craig

[Peter Warcholyk]

This message may be a duplicate, if so I apologize.

Yes, I have tried to re-execute the program. It still shows up.

I am also using marked sets. When I tried to unmark the keyed in features, then I am not able to input my required information to do the calculation.
Therefore, I do need to keep these features "marked".

Thanks to All for your assistance !!

ZydecoPete

[Paul Barriage]

Another vote for the Comment - Input version. It gives you much more control of something you hand enter. If you add numbers into the text prompt, i.e.- staing the tolerance to the operator, you may need to put quotes around the number.