Printing out-of-tolerance features only in a V4.1 report: not consistent.

[Jan d.]

Running V4.1. In report mode. If you hover over a dimension label and right click, you theoretically can get one of two different windows to pop up: One is called the "Label Properties" window where you can change the appearance of the label. The other is called "Report" window if you right click on label text. In the "Report" window, you can change a setting to ONLY print the out-of-tolerance features.

Here's my problem: in some of my programs, I can NEVER get this "Report" window to pop up. Whatever I try, I get this "Label Properties" window making an appearance again...

But on others, it just works like a charm!


This again baffles me. Has anybody experienced this before? Any work arounds? Are there other ways to instruct the report mode to only print out the out-of-tolerance features?



Thanks, Jan.

[JamesMannes]

try moving to the space between the reported dimensions and the header, but, when you get there move to the right side of the vertical lines making up the box portion of the dimension and header.



EDIT....
Also if you have difficulty in getting the edit part for report can insert a comment that goes to report that will give you some room in between?

[Jan d.]

As usual James, you're right on again.... The EDIT idea was it.

Boy, I'll end up owing my job to you...

There is still an issue though. In the help files they say that you can hover over the text and get the box to show up by right clicking, And that works in half my programs. In the other half it does NOT.

However, I added a couple of comments. Hover over the comments and right click. That did it!

I still believe there's a bug, but this workaround is darn simple...


Thanks again James, Jan.


Where are the reputation points when you need them??????????

[JamesMannes]

Yes, I would agree that it is a bug. When I get a chance I'll call it in. Kind of busy today to get on the horn with Tech Support.

[JaredHess]

...There is still an issue though. In the help files they say that you can hover over the text and get the box to show up by right clicking, And that works in half my programs. In the other half it does NOT.

Hi Jan,

I think it's probably working fine. Although I think the powers that be could have made the interface a little more user-friendly; I admit it can seem somewhat hit and miss in its current design.

Here's how it works:
* If you right-click on a table-like dimension and click Edit it will display the Label Properties dialog box.
* If you right-click on a text-only dimension and click Edit it will display the Report dialog box.
* If you right-click on any white space outside of a label and click Edit, it should also display the Report dialog box.

The help file could be more clearly written. It says, in the "Changing the Report Window's Contents" topic, "If you right-click on any reporting text, a small Edit button appears...." and then using that button will display the Report dialog box. By "any reporting text" I meant the text-only reporting text (not the table-like dimension format).

I will work on updating that help file topic.

[Jan d.]

Ahhhh. Now I get it.

You are absolutely right. Click anywhere around the table-like dimensions (even in the white) and the "Report" dialogue comes up. I do not need to insert additional comments. No need trying to hit the text inside that table-like dimension.

I think the help file funneled my actions into trying to hit that text inside the table-like dimension. And when that did not work all the time, it generated this thread.

The odd thing though: in some of my programs, I can indeed hit the text inside the table-like dimension and the Report dialogue pops up. In another similar program, I absolutely can't get it to pop up. Same call, different program.

But obviously that is a minute issue now that I understand how it really works. Simple enough now.

Thanks for your help guys.



Jan.

[JamesMannes]

Yeah I knew how it worked, but I was getting some of the same problems you were Jan. I have additional comments at the top of all my programs, so I thought that would be a nice easy way to get past the problem. It does still have issues with where you click.