| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 771.1 | OA$PAGE_LENGTH | UTRTSC::BOSMAN | We're just sugar mice in the rain | Mon Jun 01 1992 13:57 | 6 |
| Steve,
Just check the special symbol OA$PAGE_LENGTH, and change it if you
wish. I bet you get 57 the first time you do a GET OA$PAGE_LENGTH.
Sjaak.
|
| 771.2 | | WAYOUT::ALLAMS | | Tue Jun 02 1992 09:06 | 20 |
|
Sjaak,
Yes I do get 57. Where is this symbol set up, and why does it not
get changed by any of the print settings? Also, my customer says
that this 'used to work'. Presumably the merge reads this symbol,
and formats the document accordingly - what other symbols does it read?
As for the 132 column mode, again, where does the merge function get
it's defaults from - are they from the new document, or the template
document, or from somewhere completely different, as per oa$page_length
???
Steve
|
| 771.3 | (-) | UTRTSC::BOSMAN | We're just sugar mice in the rain | Tue Jun 02 1992 11:44 | 22 |
| Steve,
� Yes I do get 57. Where is this symbol set up, and why does it not
� get changed by any of the print settings? Also, my customer says
� that this 'used to work'. Presumably the merge reads this symbol,
� and formats the document accordingly - what other symbols does it read?
During the initialization phase when you invoke ALL-IN-1. You have to
change it yourself to to meet your own requirements. Another symbol
MERGE uses is OA$PAGE_NUMBER (See the APR 2 for using MERGE).
� As for the 132 column mode, again, where does the merge function get
� it's defaults from - are they from the new document, or the template
� document, or from somewhere completely different, as per oa$page_length
A quick test I just did pointed out that the default comes from the
user settings (the same when he creates a new document). To force the
MERGE output document to have the settings you want, you can append an
empty WPS-PLUS document (with the required settings) to the output
document.
Success, Sjaak.
|
| 771.4 | | WAYOUT::ALLAMS | If you're not confused, you're misinformed. | Mon Jun 08 1992 12:06 | 17 |
|
Ok,
This all seems to work ok if you set oa$page_length and
have your settings set to wide screen, the problem is that
my customer insists that he has never heard of oa$page_length -
and I did have to talk him through setting it, and that it USED
to work ok.
Is the guy who wrote the merge function around to describe where
it gets all its setting from?
Steve
|
| 771.7 | WPS-PLUS and MERGE settings | IOSG::NEWLAND | Richard Newland, IOSG, REO1-D/4A | Mon Jun 22 1992 20:01 | 41 |
| Re: .0
There are two different types of 'print settings' involved here.
1. the 'WPS-PLUS print settings', which apply only if you are
creating a WPS-PLUS document.
2. MERGE special symbols which apply for all types of output
documents.
When a new document is created and a template document is specified on the
continuation menu the initial content of the new document is the result of
processing directives from a template file (see MERGE function description
in APR for more information). The template file can optionally contain
MERGE directives. Specifying a template is not equivalent to making a copy
of a document and editing the output because in that case the MERGE
function will not be used.
If you are creating a WPS-PLUS document and the template document is also a
WPS-PLUS document then the output document will have the WPS-PLUS print
settings of the template document.
When the MERGE operation is performed the value of OA$PAGE_LENGTH
determines if page breaks are generated every OA$PAGE_LENGTH lines. If
OA$PAGE_LENGTH is 0 then no page breaks are generated.
A possible cause of the customer seeing a change in behaviour is that other
applications are changing the value of OA$PAGE_LENGTH.
It may be better for the page length value to be specified in the template
document. For example, if the template does not require page breaks then
add the the following line
<&OA GET OA$PAGE_LENGTH = 0>
to the beginning of the template document. When OA$PAGE_LENGTH is set in
this way it's original value is restored at the end of the MERGE operation.
Richard
|
| 771.8 | Settings from WPSDEF.WPL? | SANFAN::LESLIE_DA | Greetings & Solutions | Mon Jun 29 1992 08:22 | 11 |
| Gee, this is not the behavior I found using WPS-PLUS templates in
general. In doing a merge of a WPS-PLUS file to a WPS-PLUS file, it
appeared that the resulting document inherited the default file cabinet
attributes in the user's WPSDEF.WPL file. This was on ALL-IN-1 V2.3.
This was so much so, that I had seen code which copied a WPSDEF.WPL
file from a common area into the OAUSER directory (then deleted after
the file was created).
Maybe I missed something here (or maybe it changed in a later version)?
Dan
|