User talk:Jholsenback - Revision history

Wfpokorny: Removed question on potential documentation... Apparently me confused.

2017-01-08T14:52:59Z

Removed question on potential documentation... Apparently me confused.

Wfpokorny: Question on potential pattern documentation versus actual behavior.

2017-01-08T14:10:54Z

Question on potential pattern documentation versus actual behavior.

Jholsenback: more activity updates

2016-12-31T20:07:20Z

more activity updates

Jholsenback: activity updates

2016-12-31T19:46:56Z

activity updates

Jholsenback: more activity updates

2016-12-31T13:53:31Z

more activity updates

Jholsenback: activity updates

2016-12-31T13:13:17Z

activity updates

Jholsenback: minor addition

2016-12-23T11:47:54Z

minor addition

Jholsenback: arrgh

2016-12-23T11:12:40Z

arrgh

Jholsenback: more housekeeping

2016-12-23T11:11:26Z

more housekeeping

Jholsenback: housekeeping

2016-12-23T11:05:02Z

housekeeping

@@ Line 7: / Line 7: @@
    <li>{{Done}} A new finish parameter <code>use_alpha</code> has been added to suppress highlights and reflections depending on pigment transparency. [[Reference:Finish|See-It]]</li>
    <li>{{Done}} A new special pigment pattern <code>user_defined</code> has been added to define the pigment color directly in terms of a set of functions. [[Reference:User Defined Pattern|See-It]]</li>
-   <li>{{Done}} A new pattern <code>potential</code> has been added to define a pattern based on the <em>potential</em> field of a <code>blob</code> or <code>isosurface</code> object.[[Reference:Potential Pattern|See-It]]
+   <li>{{Done}} A new pattern <code>potential</code> has been added to define a pattern based on the <em>potential</em> field of a <code>blob</code> or <code>isosurface</code> object.[[Reference:Potential Pattern|See-It]]</li>
    <li>{{Done}} The <code>map_type</code> keyword now supports the Angular Map projection for light probes, popularized by Paul Devebec, as <code>type 7</code> [[Reference:Bitmap Modifiers#The map_type Option|See-It]]</li>
    <li>{{Done}} Native support for repetition has been added to the <code>crackle</code> pattern to avoid the discontinuities in the pattern caused by repeat warps. [[Reference:Crackle Pattern|See-It]]</li>

@@ Line 7: / Line 7: @@
    <li>{{Done}} A new finish parameter <code>use_alpha</code> has been added to suppress highlights and reflections depending on pigment transparency. [[Reference:Finish|See-It]]</li>
    <li>{{Done}} A new special pigment pattern <code>user_defined</code> has been added to define the pigment color directly in terms of a set of functions. [[Reference:User Defined Pattern|See-It]]</li>
-   <li>{{Done}} A new pattern <code>potential</code> has been added to define a pattern based on the <em>potential</em> field of a <code>blob</code> or <code>isosurface</code> object.[[Reference:Potential Pattern|See-It]]</li>
+   <li>{{Done}} A new pattern <code>potential</code> has been added to define a pattern based on the <em>potential</em> field of a <code>blob</code> or <code>isosurface</code> object.[[Reference:Potential Pattern|See-It]]
    <li>{{Done}} The <code>map_type</code> keyword now supports the Angular Map projection for light probes, popularized by Paul Devebec, as <code>type 7</code> [[Reference:Bitmap Modifiers#The map_type Option|See-It]]</li>
    <li>{{Done}} Native support for repetition has been added to the <code>crackle</code> pattern to avoid the discontinuities in the pattern caused by repeat warps. [[Reference:Crackle Pattern|See-It]]</li>

@@ Line 68: / Line 68: @@
 <p>The focus of this change was correcting unix console messages. There was previously no notice 'p' and 'q' were active for +D renders. The final pause, if using +P, had always incorrectly said hitting any key would continue/quit when only 'q', enter or detecting on the SDL window would. Enabling 'p' to also continue from the final pause in addition to mid render ones makes 'p' operation consistent throughout the render (and it was cleaner code-wise). Forgot to mention yesterday this change is self-documenting due the prompts to the console changing to reflect it.</p>
-   <li>The <code>version</code> pseudo-variable will now evaluate to the effective language version at the time the expression is parsed, <em>except</em> when used in a <code>#version</code> directive, in which case the behavior remains unchanged. The requirement to start each scene with a <code>#version</code> statement is now more strongly enforced for POV-Ray 3.7 scenes. An error is reported if the scene file <em>does not begin</em> with a <code>#version</code> directive but <em>does</em> have a <code>#version 3.71</code> (or later) directive anywhere in the main scene file
+   <li>{{Done}} The <code>version</code> pseudo-variable will now evaluate to the effective language version at the time the expression is parsed, <em>except</em> when used in a <code>#version</code> directive, in which case the behavior remains unchanged. The requirement to start each scene with a <code>#version</code> statement is now more strongly enforced for POV-Ray 3.7 scenes. An error is reported if the scene file <em>does not begin</em> with a <code>#version</code> directive but <em>does</em> have a <code>#version 3.71</code> (or later) directive anywhere in the main scene file</li>
-  <br>
+   <li>Using <code>ambient</code> with a suspiciously high value in a non-legacy scene will now issue a warning, unless <code>emission</code> is also specified</li>
    <li>A long-standing undocumented inconsistency in the treatment of backslashes in string literals, in which backslashes were essentially <em>not</em> interpreted as escape characters <em>if</em> the parser expected a filename, has been cleaned up. Backslashes are now treated as escape characters in all string literals. <em>requires</em> <code>#version 3.71</code> or later

@@ Line 51: / Line 51: @@
 =====Image Files=====
 <ol>
-   <li>By default, gamma handling of NetPBM (PPM/PGM) in and output files now follows the official NetBPM standard, which mandates gamma-encoding using the ITU-R BT.709 transfer function. As usual this can be overridden by the <code>gamma</code> input file parameter or <code>File_Gamma</code> INI setting, respectively
+   <li>{{Done}} By default, gamma handling of NetPBM (PPM/PGM) in and output files now follows the official NetBPM standard, which mandates gamma-encoding using the ITU-R BT.709 transfer function. As usual this can be overridden by the <code>gamma</code> input file parameter or <code>File_Gamma</code> INI setting, respectively</li>
+   <li>{{Done}} The <em>Compression</em> setting now affects more file types: Specifying <code>Compression=1</code> with file type <code>T</code> (Targa) will now generate compressed Targa (same as file type <code>C</code>), and explicitly specifying <code>Compression=0</code> with file type <code>P</code> (Netpbm PPM/PGM) will generate <em>plain</em> (ASCII) Netpbm rather than <em>raw</em> (binary)</li>
    <li>POV-Ray will now try to auto-detect whether an input TIFF file with alpha channel uses <code>premultiplied</code> or <em>non-premultiplied</em> alpha mode, rather than blindly presuming <code>premultiplied</code> alpha</li>
-   <li>The interaction of <code>transmit all</code> and <code>filter all</code> with an image's alpha channel has been changed to be more intuitive: rather than adding the image's transparency to the user-specified transparency, the image's opacity is now effectively multiplied with the user-specified opacity. (requires <code>#version 3.71</code> or later)
+   <li>{{Done}} The interaction of <code>transmit all</code> and <code>filter all</code> with an image's alpha channel has been changed to be more intuitive: rather than adding the image's transparency to the user-specified transparency, the image's opacity is now effectively multiplied with the user-specified opacity. (requires <code>#version 3.71</code> or later)</li>
    <li>The image file format previously referred to as <em>IFF</em> (now more precisely referred to as <em>IFF-ILBM</em>) is now associated with the <code>.lbm</code> file extension in addition to the <code>.iff</code> extension

@@ Line 98: / Line 98: @@
 <ol>
    <li>{{Done}} Array elements no longer have to be of the same type. [[Reference:Array|See-It]]</li>
-   <li>Dithering is now fully supported for Radiance HDR output files
+   <li>{{Done}} Dithering is now fully supported for Radiance HDR output files. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
-    <br>
+   <li>{{Done}} Trailing whitespace in INI files no longer causes a warning. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
-    <em>No change seems needed (except maybe in the "what's new" section), since the docs never said otherwise [[Reference:File_Output_Options#Output_File_Dithering|See-It]] (CLi)</em>
+   <li>{{Done}} Animation status messages now include the nominal frame number. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
-  </li>
+   <li>{{Done}} POV-Ray for Windows now reports file names and line numbers of warnings. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
-   <li>Trailing whitespace in INI files no longer causes a warning
+   <li>{{Done}} Radiosity can now honor the <code>brilliance</code> setting of a surface. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
    <li>{{Done}} Color maps, pigment maps and the like are no longer limited to 256 entries.</li>
      <ul>
@@ Line 120: / Line 114: @@
      </ul>
    </li>
-   <li>The number of components per blob is no longer artificially limited. [[Reference:Blob|Over-Here]]
+   <li>{{Done}} The number of components per blob is no longer artificially limited. [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
 </ol>

@@ Line 29: / Line 29: @@
    <li>{{Done}} The <code>max_extent</code> function as used to determine the size of an image map in pixels can now also be used on normal maps and density files</li>
    <li>{{Done}} Macros up to a certain size (currently hard-coded to 65536 characters per macro) are now cached in memory, improving parsing speed of invocations especially when the macro in question is defined in a different file</li>
-   <li>All instances of <code>gray</code> in keywords or INI file options can now alternatively be spelled <code>grey</code>. Previously this was only the case inside function definitions where it applied only to the <code>.gray</code> color pseudo-component</li>
+   <li>{{Done}} All instances of <code>gray</code> in keywords or INI file options can now alternatively be spelled <code>grey</code>. Previously this was only the case inside function definitions where it applied only to the <code>.gray</code> color pseudo-component [[Documentation:Tutorial Section 1#Changes and New Features Summary|See-It]]</li>
    <li>{{Done}} A new inbuilt constant <code>tau</code> has been added</li>
    <li>{{Done}} The <code>#declare</code> and <code>#local</code> syntax has been extended to support tuple-style assignments.
-<p><em><strong>Markup completed. Please review before I add to documentation proper. Also indicate where in to insert/add:</strong></em> [[User_talk:Jholsenback#Code_Snippet.27s_Comments_and_Content_Related|See-It]]</p></li>
+[[Reference:Declare and Local Directives|See-It]]</li>
    <li>{{Done}} The macro syntax has been extended to allow for <code>optional</code> parameters</li>
    <li>{{Done}} The creation of a log for the <code>+C</code> render abort-continue feature can now be suppressed using <code>-CC</code> to save disk space</li>
@@ Line 128: / Line 128: @@
 ====Code Snippet's Comments and Content Related====
 <p>Use this section for <em>code snippet's</em> to be included in reference. Comments and content related items are welcome too.</p>
 ===3.7.1 Scene File Checklist===

@@ Line 145: / Line 145: @@
 <pre>
-// Is this valid? ie: &lt; and &gt; or just a typo
+// Is this valid? ie: &lt; and &gt; if so just remove this line
 #declare &lt; ID1, ID2, ... &gt; = VECTOR_EXPR;

@@ Line 129: / Line 129: @@
 <p>Use this section for <em>code snippet's</em> to be included in reference. Comments and content related items are welcome too.</p>
 <p>New tuple-style syntax extensions has been added to <code>#declare</code> and <code>#local</code> in order to simplify passing multiple values out of a macro:</p>
@@ Line 144: / Line 145: @@
 <pre>
-#declare < ID1, ID2, ... > = VECTOR_EXPR;
+// Is this valid? ie: &lt; and &gt; or just a typo
 //This statement is fully equivalent to:
@@ Line 172: / Line 174: @@
 <p>Left-hand side elements in tuple assignments can now be prepended with the <code>optional</code> keyword. If an element is flagged this way, or left empty, the corresponding right-hand side element may be an uninitialized identifier or left empty. In this case, the respective left-hand side element remains unchanged (it is NOT undefined).</p>
 <p>An array initializer may now be prepended with the <code>optional</code> keyword ...</p>
@@ Line 181: / Line 182: @@
 <p>... in this case, each individual element of the initializer may be an uninitialized identifier or left empty.</p>
-<pre>Make sure to include this ... also relevant for macro parameters and array initializers!</pre>
+<p class="Note"><strong>Note:</strong> Due to parser limitations, <em>uninitialized identifiers</em> do <em>not</em> encompass uninitialized array elements. This limitation also applies to optional macro parameters.</p>
-<p class="Note"><strong>Note:</strong> Due to parser limitations, <em>uninitialized identifiers</em> do <em>not</em> encompass uninitialized array elements. This limitation also applies to optional macro parameters.</p>
+<p>END tuple-style syntax extensions</p>
 ===3.7.1 Scene File Checklist===

@@ Line 31: / Line 31: @@
    <li>All instances of <code>gray</code> in keywords or INI file options can now alternatively be spelled <code>grey</code>. Previously this was only the case inside function definitions where it applied only to the <code>.gray</code> color pseudo-component</li>
    <li>{{Done}} A new inbuilt constant <code>tau</code> has been added</li>
-   <li>The <code>#declare</code> and <code>#local</code> syntax has been extended to support tuple-style assignments. The main purpose is to allow macros to return a set of values rather than just a single one</li>
+   <li>{{Done}} The <code>#declare</code> and <code>#local</code> syntax has been extended to support tuple-style assignments.
    <li>{{Done}} The macro syntax has been extended to allow for <code>optional</code> parameters</li>
    <li>{{Done}} The creation of a log for the <code>+C</code> render abort-continue feature can now be suppressed using <code>-CC</code> to save disk space</li>
@@ Line 40: / Line 41: @@
    <li>{{Done}} Support for the ITU-R BT.709 and BT.2020 transfer functions has been added to POV-Ray's gamma handling portfolio</li>
    <li>{{Done}} A new function-based user-defined camera type <code>user_defined</code> has been added</li>
-   <li>Light sources distance-based fading can now be set to obey an inverse-power law at all distances</li>
+   <li>{{Done}} Light sources distance-based fading can now be set to obey an inverse-power law at all distances [[Reference:Light Source#Light Fading|See-It]]</li>
    <li>{{Done}} CIE L*a*b* conversion macros have been added to <em>colors.inc</em> [[Reference:Colors.inc#Color_macros|See-It]]</li>
    <li>{{Done}} A new include file <em>colors_ral.inc</em> has been added containing predefined colors according to the RAL Classic standard [[Reference:Colors_ral.inc|See-It]]</li>