Difference between revisions of "preprocessFile"
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "|= Game name" to "|Game name=") |
Lou Montana (talk | contribs) m (Text replacement - "|= Game version" to "|Game version=") |
||
| Line 4: | Line 4: | ||
| ofpr |Game name= | | ofpr |Game name= | ||
| − | |1.85| | + | |1.85|Game version= |
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 15:11, 1 September 2019
Notes
- Posted on March 4, 2008
- Alef
- File path is always relative to mission directory. If script dir\a.sqf includes dir\b.sqf, use "dir\b.sqf" and not "b.sqf".
- Posted on July 8, 2011
- kju
- Use preprocessFileLineNumbers instead as it provides more context information on error.
- Posted on December 17, 2013
- Killzone_Kid
- The main difference between preprocessFile and preprocessFileLineNumbers is that the latter adds #line directive to the target file, which allows to log the __LINE__ error happened at and the __FILE__ error happened in.
- Posted on July 25, 2014
- BrotherhoodOfHam
Essentially what the preprocessFile command does is it refers to the contents of a file as a string:
Example 1:
boop.html:<t align = 'center' valign = 'middle' shadow = '0' size = '2'>structured text</t>init.sqf:_text = parseText preprocessFile "boop.html"; hint _text;
This is especially useful for long strings, and it works on files with any file extension as long as they can be edited with a text editor.
Example 2:
init.sqf:
hint preprocessFile "description.ext"; copyToClipboard preprocessFile "mission.sqm";The above is all valid. However, using *.jpg or any other files saved in an image format is not possible.
