summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKevin Rushforth <[email protected]>2006-04-19 18:26:03 +0000
committerKevin Rushforth <[email protected]>2006-04-19 18:26:03 +0000
commit6d26f19dddb6cfebf66bd86134a369ed54d92b2a (patch)
treef06a01b96b8ad8f36c80039e0d0afdd47958f1b8
parent4bba14792459698b5ed562b410cd94dc1fbc147b (diff)
Added note about new system property.
git-svn-id: https://svn.java.net/svn/j3d-core~svn/trunk@565 ba19aa83-45c5-6ac9-afd3-db810772062c
-rw-r--r--www/j3d1_4_0_01/RELEASE-NOTES.html38
1 files changed, 29 insertions, 9 deletions
diff --git a/www/j3d1_4_0_01/RELEASE-NOTES.html b/www/j3d1_4_0_01/RELEASE-NOTES.html
index 7f5e57c..64f3702 100644
--- a/www/j3d1_4_0_01/RELEASE-NOTES.html
+++ b/www/j3d1_4_0_01/RELEASE-NOTES.html
@@ -144,6 +144,15 @@ release.</p>
</th>
</tr>
<tr>
+ <td style="vertical-align: top; text-align: right;">160<br>
+ </td>
+ <td style="vertical-align: top;"><br>
+ </td>
+ <td style="vertical-align: top;">AlternateAppearance behaves
+differently in J3D 1.3.2 comparing to J3D 1.3.1<br>
+ </td>
+ </tr>
+ <tr>
<td style="text-align: right;"><span
style="font-family: monospace;"></span>244<br>
</td>
@@ -159,17 +168,28 @@ release.</p>
MasterControlThread when adding a Light<br>
</td>
</tr>
- <tr>
- <td style="vertical-align: top; text-align: right;">160<br>
- </td>
- <td style="vertical-align: top;"><br>
- </td>
- <td style="vertical-align: top;">AlternateAppearance behaves
-differently in J3D 1.3.2 comparing to J3D 1.3.1<br>
- </td>
- </tr>
</tbody>
</table>
+<p>NOTE: the fix for issue 249 (as well as 160) was to disable the
+"sole user" optimization, which was originally done to optimize the
+updating of
+frequently changing appearance attributes in cases where there was only
+one Shape3D using a particular Appearance. This optimization came at
+the expense of rendering performance in some cases, and was also the
+source of several
+bugs. Now that this optimization is disabled, rendering
+performance and stability should improve for most applications, but
+some
+applications may notice a slow-down in update performance. For this
+reason, we have added a new system property to re-enable the sole-user
+optimization.<br>
+</p>
+<ul>
+ <li><code>j3d.allowSoleUser</code> &#8211; If this flag is set to
+true, the 1.4.0-fcs behavior is restored, causing the sole-user
+optimization to be allowed when appropriate. The default value is false.<br>
+ </li>
+</ul>
<h3><a name="Changes_Since_1_3_2"></a>Changes Since 1.3.2</h3>
<h4>New Features</h4>
<p>Thw following new features have been added to the 1.4 version of the