Per recent discussions and issue work I think we should document the -CC 
option.

Reference :

http://news.povray.org/povray.windows/message/%3C584605a0%241%40news.povray.org%3E/#%3C584605a0%241%40news.povray.org%3E

and

https://github.com/POV-Ray/povray/issues/167

I think it comes to adding something like :

---

Create_Continue_Trace_Log=bool  Save state information in file on/off
+CC Save state information in file on
-CC Save state information in file off

The state or continue trave information file must exist for the 
Continue_Trace=true / +C option to work.

---

to the section:

http://wiki.povray.org/content/Reference:General_Output_Options#Resuming_Options

Also in that section we today have this bit:

"This option reads in the previously generated output file, displays the 
partial image rendered so far, then proceeds with the ray-tracing. This 
option cannot be used if file output is disabled with Output_to_file=off 
or -F."

However, I think "Output_to_file=off or -F" suppresses the creation of 
the final output image file not the state/log file needed to continue a 
trace. Thinking we might re-work the above paragraph to refer to the 
state/log file instead and drop reference to the output to file option 
here.

Aside: There are other documentation updates sitting in the two 
references above, but thinking we should go after those later in 
dedicated threads for sake of clarity.

Bill P.

Post a reply to this message

On 12/6/2016 6:43 AM, William F Pokorny wrote:
> Per recent discussions and issue work I think we should document the -CC
> option.

agreed ... i recall this feature being added but don't remember when. at 
first i thought back in 3.7 when Max_Image_Buffer_Memory was added but 
after looking i don't think so ... 3.7.1??

> I think it comes to adding something like :
>
> ---
>
> Create_Continue_Trace_Log=bool  Save state information in file on/off
> +CC Save state information in file on
> -CC Save state information in file off
>
> The state or continue trave information file must exist for the
> Continue_Trace=true / +C option to work.

yep ... thanks

> to the section:
>
> http://wiki.povray.org/content/Reference:General_Output_Options#Resuming_Options
>
>
> Also in that section we today have this bit:
>
> "This option reads in the previously generated output file, displays the
> partial image rendered so far, then proceeds with the ray-tracing. This
> option cannot be used if file output is disabled with Output_to_file=off
> or -F."
>
> However, I think "Output_to_file=off or -F" suppresses the creation of
> the final output image file not the state/log file needed to continue a
> trace. Thinking we might re-work the above paragraph to refer to the
> state/log file instead and drop reference to the output to file option
> here.

good catch ... think you're correct about -F

>
> Aside: There are other documentation updates sitting in the two
> references above, but thinking we should go after those later in
> dedicated threads for sake of clarity.

like what? might as well see if i can address those while i'm over there 
anyways

Post a reply to this message

Hi folks,

Am 07.12.2016 um 13:38 schrieb Jim Holsenback:
> On 12/6/2016 6:43 AM, William F Pokorny wrote:
>> Per recent discussions and issue work I think we should document the -CC
>> option.
> 
> agreed ... i recall this feature being added but don't remember when. at
> first i thought back in 3.7 when Max_Image_Buffer_Memory was added but
> after looking i don't think so ... 3.7.1??

Just did a quick code compare: 3.7.1 it is.

Post a reply to this message

On 12/07/2016 07:38 AM, Jim Holsenback wrote:
> On 12/6/2016 6:43 AM, William F Pokorny wrote:
>
> like what? might as well see if i can address those while i'm over there
> anyways
>

OK. Might be some thinking aloud on my part. Take a look at my comment to :

https://github.com/POV-Ray/povray/issues/167

and specifically within that comment the block with the leader:

"Documentation indicates:"

The list starts off with a set of 4 features our documentation has as 
available which are not in 3.7. I think the documentation should 
probably indicate these as Deprecated for the time being.

The two undocumented features near the bottom of the block should 
probably be restored to the documentation and also listed as Deprecated. 
Our code allows them to exist - and they no doubt do - in old ini files.

I don't know what to do with Antialias_Gamma_type as it didn't look to 
me like end users have ever seen it documented in any fashion, but 
others might know differently. I'd say leave it completely out of the 
documentation pending any other information.

Just below the block, in parens, I wonder about the text we have in the 
documentation about the very old and long gone Buffer_output and 
Buffer_Size options. Thinking it should just be deleted - yep, I missed 
documenting where I saw that text...

I've used the term "Deprecated" to be consistent with other 
documentation, but I believe all options marked this way are "Deprecated 
and Non-functional." Perhaps we should better indicate this.

There are further questions about how our code is handling many of these 
non-functioning option - you'll see I rolled a flyspray issue I think 
you opened into this github issue - but I don't think this is the 
newsgroup / issue in which to work those out.

I think a good first step with github #167 is to do some documentation 
updates to reflect the status today.

Bill P.

Post a reply to this message

Am 08.12.2016 um 14:41 schrieb William F Pokorny:

> I don't know what to do with Antialias_Gamma_type as it didn't look to
> me like end users have ever seen it documented in any fashion, but
> others might know differently. I'd say leave it completely out of the
> documentation pending any other information.

kPOVAttrib_AntialiasGammaType is just a (placeholder) companion to
kPOVAttrib_AntialiasGamma, just as kPOVAttrib_FileGammaType is a
(genuine) companion to kPOVAttrib_FileGamma. The latter two combine to
convey the information provided via the "File_Gamma" setting (with
kPOVAttrib_FileGammaType being used to convey special values such as
"sRGB"). Since "Antialias_Gamma" currently only supports float values,
the type portion is unused.

Post a reply to this message

On 12/8/2016 8:41 AM, William F Pokorny wrote:
> "Documentation indicates:"
>
> The list starts off with a set of 4 features our documentation has as
> available which are not in 3.7. I think the documentation should
> probably indicate these as Deprecated for the time being.

http://wiki.povray.org/content/Reference:Animation_Options#Field_Rendering

http://wiki.povray.org/content/Reference:General_Output_Options#Interrupting_Options
>
> The two undocumented features near the bottom of the block should
> probably be restored to the documentation and also listed as Deprecated.
> Our code allows them to exist - and they no doubt do - in old ini files.

i see from wiki history that i removed these back in sep 2013. besides 
the feature listing there was also some narrative as well. rather than 
restore all that and document as deprecated ... how about a well placed 
"Note" instead

> Just below the block, in parens, I wonder about the text we have in the
> documentation about the very old and long gone Buffer_output and
> Buffer_Size options. Thinking it should just be deleted - yep, I missed
> documenting where I saw that text...

http://wiki.povray.org/content/Reference:File_Output_Options#Output_File_Buffer

besides the content there's only a couple of other places that need to 
be touched to just get rid of it altogether ... nuke it?

> I've used the term "Deprecated" to be consistent with other
> documentation, but I believe all options marked this way are "Deprecated
> and Non-functional." Perhaps we should better indicate this.

i'm ok with this term mainly because it /is/ consistent with what's been 
done so far ... only possible drawback is confusion with /deprecated/ 
keyword. as long as <code> is used when taking about keyword and <em> is 
used otherwise i think we should be fine

Post a reply to this message

On 12/8/2016 11:35 AM, Jim Holsenback wrote:
> i see from wiki history that i removed these back in sep 2013. besides
> the feature listing there was also some narrative as well. rather than
> restore all that and document as deprecated ... how about a well placed
> "Note" instead

http://wiki.povray.org/content?title=Reference:Display_Output_Options&diff=8385&oldid=8161

Post a reply to this message

Am 08.12.2016 um 17:37 schrieb Jim Holsenback:
> On 12/8/2016 11:35 AM, Jim Holsenback wrote:
>> i see from wiki history that i removed these back in sep 2013. besides
>> the feature listing there was also some narrative as well. rather than
>> restore all that and document as deprecated ... how about a well placed
>> "Note" instead
> 
>
http://wiki.povray.org/content?title=Reference:Display_Output_Options&diff=8385&oldid=8161

Still accepted on the command line and in INI files, so might bring a
short description back in. Something to the effect that
platform-specific versions /may/ use these parameters for blah-blah.

(For instance - but please don't put this in the docs - the `+Dn`
setting might be revived by some future version to choose between a
windowed (sized to image), maximized (sized to screen) and fullscren (no
taskbar and such) mode for the preview.)

Post a reply to this message

On 12/08/2016 01:42 PM, clipka wrote:
> Am 08.12.2016 um 17:37 schrieb Jim Holsenback:
>> On 12/8/2016 11:35 AM, Jim Holsenback wrote:
>>> i see from wiki history that i removed these back in sep 2013. besides
>>> the feature listing there was also some narrative as well. rather than
>>> restore all that and document as deprecated ... how about a well placed
>>> "Note" instead
>>
>>
http://wiki.povray.org/content?title=Reference:Display_Output_Options&diff=8385&oldid=8161
>
> Still accepted on the command line and in INI files, so might bring a
> short description back in. Something to the effect that
> platform-specific versions /may/ use these parameters for blah-blah.
>
> (For instance - but please don't put this in the docs - the `+Dn`
> setting might be revived by some future version to choose between a
> windowed (sized to image), maximized (sized to screen) and fullscren (no
> taskbar and such) mode for the preview.)
>

I couldn't pick up any note with these old eyes. I agree with Christoph 
that bringing back a short description instead of the whole mess is 
probably in order.

Bill P.

Post a reply to this message

On 12/9/2016 1:14 PM, William F Pokorny wrote:
> On 12/08/2016 01:42 PM, clipka wrote:
>> Am 08.12.2016 um 17:37 schrieb Jim Holsenback:
>>> On 12/8/2016 11:35 AM, Jim Holsenback wrote:
>>>> i see from wiki history that i removed these back in sep 2013. besides
>>>> the feature listing there was also some narrative as well. rather than
>>>> restore all that and document as deprecated ... how about a well placed
>>>> "Note" instead
>>>
>>>
http://wiki.povray.org/content?title=Reference:Display_Output_Options&diff=8385&oldid=8161
>>>
>>
>> Still accepted on the command line and in INI files, so might bring a
>> short description back in. Something to the effect that
>> platform-specific versions /may/ use these parameters for blah-blah.
>>
>> (For instance - but please don't put this in the docs - the `+Dn`
>> setting might be revived by some future version to choose between a
>> windowed (sized to image), maximized (sized to screen) and fullscren (no
>> taskbar and such) mode for the preview.)
>>
>
> I couldn't pick up any note with these old eyes. I agree with Christoph
> that bringing back a short description instead of the whole mess is
> probably in order.
>
> Bill P.

i just went ahead and restored the whole thing and clarified the status: 
http://wiki.povray.org/content/Reference:Display_Output_Options#Display_Hardware_Settings

Post a reply to this message