Currently we note an effect in an existing project during the update of the property @PRINTORDER which we can not explain.
We procedures as follows:
1. Generating the required PageOrder.txt
2. Invoke Tools / Update other Objects... with the settings "Properties = on", "Print Order = on", Range = Project"
3. The @PRINTORDER property of each border receives the correct page number
After this, the scout is able to place the correct sheet number on the border by reading the @PRINTORDER property. So far so good.
Then, we add a new block on the top sheet which includes new sheets. These sheets have also the same borders as the other sheets of the project, where the update of the @PRINTORDER property worked without any problems.
We did the same procedure like above:
1. Generating the required PageOrder.txt
2. Invoke Tools / Update other Objects... with the settings "Properties = on", "Print Order = on", Range = Project"
3. The @PRINTORDER property of the old borders receives the correct page number. But the @PRINTORDER property of the borders of the new sheets received nothing and are empty.
I checked the "Setup / Settings / Sheet Numbering" - everythink is ok.
![]()
I add a new sheet in an old block. This sheet receives the correct value and is assigned to the @PRINTORDER property.
There is only the problem with new blocks and its underlying sheets.
Have anybody any idea and can explain this behavior?