GDI printing enhancement: New printing directive //META, args can be used to embed unspecified meta data in the printfile. The //META lines will not print or display in APEX, but will remain in the file, possibly of use to archival or other post-printing routines. Currently there is only one special //META command that means anything to A-Shell:
//META, FTP, dirflag, Hostpath, Localpath
If the FTP META command is seen by APEX running within ATE, it will attempt to perform an FTP transfer of hostfile to/from localpath, depending on the direction code (dirflag), which should be one of (0,1,2,3,A,B,C,D) - as used by AG_FTP (see the Dev Guide for details.)
Hostpath should be in native format, to be understood by the FTP server on the host.
Localpath should be in PC format, or it may use the special syntax "@.xxx" where xxx is the desired file extension. The "@." will be replaced by the complete filespec of the file currently being printed or previewed, minus its extension. This is useful for sending printfile sidecar files which will be matched up later based on having the same filename, but where you don't know the complete filename that will be assigned by ATE or APEX to the printfile. (ATE/APEX typically create versions of the original file, in the Documents\APEX directory, with a unique numeric suffix.)
Note: since //META will not be recognized by A-Shell versions prior to 5.1.1133, the syntax //;META,... is also allowed. (//; indicates a comment line normally, so A-Shell will not display the line, but 5.1.1133+ will still recognize it.)
Also see the print filter ATPXFR.SBX (distributed in the SOSLIB) for another approach to making sure that auxiliary files related to printing (such as images referenced by an //IMAGE directive) are transferred to the remote PC before needed during printing.
