Difference between revisions of "preprocessFile"

From Bohemia Interactive Community
Jump to navigation Jump to search
Line 56: Line 56:
<!-- CONTINUE Notes -->
<!-- CONTINUE Notes -->
<dl class="command_description">
<dd class="notedate">Posted on July 25, 2014 - 16:35 (UTC)</dd>
<dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt>
<dd class="note">
<!-- DISCONTINUE Notes -->
<!-- DISCONTINUE Notes -->
Essentially what the preprocessFile command does is it refers to the contents of a file as a string:<br/>
Example 1:
<code><t align = 'center' valign = 'middle' shadow = '0' size = '2'>structured text</t></code>
<code>_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: <br/>
<code>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.

Revision as of 18:38, 25 July 2014



Posted on March 4, 2008
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
Use preprocessFileLineNumbers instead as it provides more context information on error.
Posted on December 17, 2013
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. PreprocessFile.jpg

Bottom Section