Why isn't the appearance condition set to Page() = 2 for the 11th feature in the Visual Part Report?
This article explains the Appearance Conditions needed for the Visual Part report to run correctly.
Print Friendly View
written: 02/29/2008
last modified: 03/08/2024

Why isn't the appearance condition set to Page() = 2 for the 11th feature in the Visual Part Report? Also, the 21st feature?

The Visual Part Report allows you to visually run a report with a picture of your part in the middle and callouts to various features on the report. Each callout has an associated plot and stat summary. The report allows you to report on up to 30 features with 3 pages of 10 on each page. This can be reconfigured, but this is how the report is shipped.

WARNING: This article is for fairly advanced users of the report designer and deals with more advanced topics.

Each feature on the 3 pages has an Appearance Condition set to the Dim_Used_nn variable (discussed in a separately linked article). In addition, those objects on pages 2 and 3 have a second part of the Appearance Condition that checks the page number and only shows the object if it is on the correct page. For instance, feature 12 should only be shown on page 2. Therefore, its Appearance Condition is set to "dim_used_12 and Page() = 2". This tells the report to only show feature 12 if we it exists and we are currently printing the second page. As a second example, Feature 22's Appearance Condition is "dim_used_22 and Page() = 3".

For each feature, there are three objects associated; a rectangle (frame), the plot, and the numbers label.  For features 11 and 21, the plot and numbers label should have the Page() = x portion of the condition. The rectangle, however, should NOT have this added. The reason is a feature of the report called "Pagewrap Before".

In the rectangle's properties, you'll notice this property directly beneath the Appearance Condition. For the rectangle on feature 11, it is set to True. This tells the report to put a pagebreak just before drawing the rectangle. This essentially forces page 2 to happen. If we add the Page() = 2 to the condition, then it will be evaluated to false since page 2 hasn't been created yet, which means the pagewrap won't happen and the report will stop on page 1.

In addition, in the Layer Conditions you'll notice that Layer 1 has an Appearance Condition of "Page() = 1", but Layers 2 and 3 do not. In fact, if you add them for layer 2 (Page() = 2) and rerun the report, you'll notice that all the plots will disappear from page 2. This is because the layer condition is evaluated before the objects on the layer. Therefore, since the rectangle for dim 11 hasn't yet been drawn (it's contained in layer 2), the pagebreak hasn't been forced, which means Page 2 doesn't ever happen.

Applies To

QC-CALC Real-Time v.4.10
QC-CALC Real-Time v.4.00
QC-CALC Real-Time v.3.40


Reporting - QC-CALC 3.x
See more articles in this category