<?xml version="1.0" ?><rss version="2.0">
  <channel>
    <title>POV-Ray Bug Tracking System:</title>
    <lastBuildDate>Tue, 09 May 2017 15:37:11 +0000</lastBuildDate>
    <description>POV-Ray Bug Tracking System:POV-Ray: Recently opened tasks</description>
    <link>http://bugs.povray.org/</link>
        <item>
      <title>FS#336: #fopen w/o OPEN_TYPE crash povray (segfault)</title>
      <author>Pietro Bernardi</author>
      <pubDate>Sun, 06 Nov 2016 12:47:37 +0000</pubDate>
      <description><![CDATA[#fopen directive w/o OPEN_TYPE (yeah, I forgot it, some other languages have &#039;read&#039; as default value)<br />
<br />
expected behavior:<br />
Parse error msg &quot;line XXX, OPEN_TYPE missing in #fopen directive&quot;, then stop.<br />
<br />
observed behavior:<br />
crash - Segfault err (core dump) in Parsing stage<br />
<br />
minimal working example attached<br />
]]></description>
      <link>http://bugs.povray.org/task/336</link>
      <guid>http://bugs.povray.org/task/336</guid>
    </item>
        <item>
      <title>FS#335: macro works in variable but not in array</title>
      <author>Mike H</author>
      <pubDate>Sat, 06 Feb 2016 02:01:05 +0000</pubDate>
      <description><![CDATA[This doesn&#039;t work:<br />
<br />
#declare pavement_object = array[2]<br />
{<br />
	object {trash_can_macro()	scale 3/4			translate -x * 1/2},<br />
	object {potted_plant_macro(_CT_rand2)	scale 3/4	scale 3/2	translate -x * 1/2}<br />
}<br />
<br />
This does work:<br />
<br />
#declare trash_can_object = object {trash_can_macro()};<br />
#declare potted_plant_object = object {potted_plant_macro(_CT_rand2)};<br />
#declare pavement_object = array[2]<br />
{<br />
	object {trash_can_object	scale 3/4			translate -x * 1/2},<br />
	object {potted_plant_object	scale 3/4	scale 3/2	translate -x * 1/2}<br />
}<br />
<br />
Logically, I cannot see a reason for this to be so.]]></description>
      <link>http://bugs.povray.org/task/335</link>
      <guid>http://bugs.povray.org/task/335</guid>
    </item>
        <item>
      <title>FS#334: HLS colors</title>
      <author>Mike H</author>
      <pubDate>Sat, 23 Jan 2016 00:21:39 +0000</pubDate>
      <description><![CDATA[It would be nice to be able to specify colors in HLS as well as RGB.<br />
<br />
Currently, you can use a macor to convert individual colors. But this does not work in color_maps where you want smooth gradations/interpolations between two or several colors.]]></description>
      <link>http://bugs.povray.org/task/334</link>
      <guid>http://bugs.povray.org/task/334</guid>
    </item>
        <item>
      <title>FS#333: Make text in &quot;about&quot; alt+b dialog selectable with the mouse and copy-able</title>
      <author>Mike H</author>
      <pubDate>Mon, 18 Jan 2016 00:23:15 +0000</pubDate>
      <description><![CDATA[When you press alt+b or access the &quot;about&quot; dialog in the Help menu it displays some text including software version number and list of contributors.<br />
<br />
It would be nice to be able to select and copy this text using this mouse. Sometimes in the newsgroup I have to tell people what version of POVray I am using, and typing the version number can be a pain.]]></description>
      <link>http://bugs.povray.org/task/333</link>
      <guid>http://bugs.povray.org/task/333</guid>
    </item>
        <item>
      <title>FS#332: Progress animation in taskbar tabs</title>
      <author>Mike H</author>
      <pubDate>Fri, 15 Jan 2016 07:00:42 +0000</pubDate>
      <description><![CDATA[On Windows 7 and newer operating systems, some programs are able to display their progress in the taskbar buttons.<br />
<br />
Here is an example of Chrome downloading something and showing the progress in the taskbar:<br />
<br />
http://www.winbeta.org/sites/default/files/news/oldfashinoned.jpg<br />
<br />
Here is an example with Paint.NET instead:<br />
<br />
http://www.getpaint.net/images/pdn351_superbarProgress.png<br />
<br />
I think this feature would use fewer CPU resources than a) minimizing/maximizing the whole application window each time you want to check progress, or b) hovering the mouse over the taskbar button to show the thumbnails.]]></description>
      <link>http://bugs.povray.org/task/332</link>
      <guid>http://bugs.povray.org/task/332</guid>
    </item>
        <item>
      <title>FS#331: Intersection causes quadric to disappear</title>
      <author>Richard Callwood III</author>
      <pubDate>Mon, 27 Jul 2015 22:50:56 +0000</pubDate>
      <description><![CDATA[The following paraboloid renders correctly:<br />
<br />
intersection<br />
{ quadric { , , , -1 }<br />
  cylinder { 0, y, 1 }<br />
}<br />
<br />
However, when I extend the clipping cylinder downward:<br />
<br />
intersection<br />
{ quadric { , , , -1 }<br />
  cylinder { -y, y, 1 }<br />
}<br />
<br />
the object disappears completely in POV-Ray 3.7 and 3.7.1. In POV-Ray <br />
3.6.1, it renders as expected.<br />
<br />
POV-Ray 3.7.0.unofficial (self-compiled with g++ 4.8, but completely unaltered)<br />
POV-Ray 3.7.1-alpha.8150025.unofficial<br />
openSUSE 13.2 GNU/Linux<br />
<br />
This scene file illustrates the problem:<br />
<br />
// +w480 +h240<br />
#version 3.6; //[sic]<br />
<br />
global_settings { assumed_gamma 1 }<br />
<br />
camera<br />
{ location <br />
  look_at <br />
  right 2 * x<br />
  up y<br />
  angle 43.1038<br />
}<br />
<br />
#default { finish { diffuse 0.6 ambient rgb 0.15618 } }<br />
<br />
light_source<br />
{ ,<br />
  rgb 6856.3<br />
  fade_power 2 fade_distance 0.10417<br />
  spotlight point_at  radius 45 falloff 90<br />
}<br />
<br />
box<br />
{ -, <br />
  pigment { rgb 1 }<br />
}<br />
<br />
plane<br />
{ y, 0<br />
  pigment { checker rgb 0.05 rgb 1 }<br />
}<br />
<br />
intersection<br />
{ quadric { , , , -1 }<br />
  cylinder { 0, y, 1 }<br />
  pigment { green 0.5 }<br />
  translate <br />
}<br />
<br />
intersection<br />
{ quadric { , , , -1 }<br />
  cylinder { -y, y, 1 }<br />
  pigment { green 0.5 }<br />
  translate <br />
}<br />
<br />
On the right side, there should have been a cylinder capped with a paraboloid. A [[http://news.povray.org/povray.bugreports/thread/%3C55b39c37%241%40news.povray.org%3E/|thread has been started in povray.bugreports]]. Jerome has started to look at it.<br />
<br />
]]></description>
      <link>http://bugs.povray.org/task/331</link>
      <guid>http://bugs.povray.org/task/331</guid>
    </item>
        <item>
      <title>FS#330: Typo in QUICKRES.INI</title>
      <author>Jim Holsenback</author>
      <pubDate>Fri, 24 Jul 2015 14:49:07 +0000</pubDate>
      <description><![CDATA[Height=36084<br />
<br />
[640x360, AA 0.3]<br />
Width=640<br />
Height=36084<br />
Antialias=On<br />
Antialias_Threshold=0.3<br />
<br />
should be:<br />
<br />
[640x360, AA 0.3]<br />
Width=640<br />
Height=360<br />
Antialias=On<br />
Antialias_Threshold=0.3]]></description>
      <link>http://bugs.povray.org/task/330</link>
      <guid>http://bugs.povray.org/task/330</guid>
    </item>
        <item>
      <title>FS#329: Mesh_camera type 0 output seems</title>
      <author>Manson</author>
      <pubDate>Fri, 12 Jun 2015 10:37:22 +0000</pubDate>
      <description><![CDATA[ When using mesh_camera type ‘0’<br />
<br />
The first line of the mesh output seems to be repeated resulting in incorrect light colour values.<br />
<br />
If the first line of the texture is skipped then the values seem to be correct.]]></description>
      <link>http://bugs.povray.org/task/329</link>
      <guid>http://bugs.povray.org/task/329</guid>
    </item>
        <item>
      <title>FS#328: Ascii char &#039;=&#039; in filenames causes command line parsing failure</title>
      <author>Marco Costa</author>
      <pubDate>Wed, 04 Mar 2015 19:41:59 +0000</pubDate>
      <description><![CDATA[The following command fails with parsing error:<br />
povray  +OqXfFbD0Vg5XjZgi5sOefkvdF_oCGrZ1ChVhrQw==.png +IqXfFbD0Vg5XjZgi5sOefkvdF_oCGrZ1ChVhrQw==.pov +W1000 +H1000<br />
<br />
The following command succeeds:<br />
povray  +OqXfFbD0Vg5XjZgi5sOefkvdF_oCGrZ1ChVhrQw.png +IqXfFbD0Vg5XjZgi5sOefkvdF_oCGrZ1ChVhrQw.pov +W1000 +H1000<br />
<br />
<br />
Any option that gets a filename as parameter will fail if it contains &#039;=&#039;.<br />
<br />
It is a regression, as it worked fine with 3.6.]]></description>
      <link>http://bugs.povray.org/task/328</link>
      <guid>http://bugs.povray.org/task/328</guid>
    </item>
        <item>
      <title>FS#327: Support for non-ASCII characters in filename strings</title>
      <author>liujiaguo</author>
      <pubDate>Tue, 06 Jan 2015 10:01:01 +0000</pubDate>
      <description><![CDATA[pov 3.7 Can not identify the Chinese.I give the texture map filename in chinese,it turns out parse error.]]></description>
      <link>http://bugs.povray.org/task/327</link>
      <guid>http://bugs.povray.org/task/327</guid>
    </item>
      </channel>
</rss>
