|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This may be due to my system and setup (Win7 64 bit). But in the help file:
enter. I get a list of keywords below it and a list in the RHS window
(okay so far). If I click on, say, adc_bailout in the RHS window. I get
the entry for it displayed with the header at the top of the screen.
If I double click on it in the LHS window the display goes to the header
for 3.4.1 Global Settings.
click on aa_level in the LHS window nothing happens. Nor does anything
happen for the next two entries, to absorption. Double clicking on
just below it. But
I could go on. (I often do ;-) )
BTW the help for 3.6.2 does something similar.
The fact that I have not seen anyone mention this makes me suspicious
that it is something to do with my system. If that is so what can I do?
Oops! there is an entry from JamesB7271 on 11th of March 2012.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05/17/2013 07:03 AM, Stephen wrote:
> This may be due to my system and setup (Win7 64 bit). But in the help file:
> enter. I get a list of keywords below it and a list in the RHS window
> (okay so far). If I click on, say, adc_bailout in the RHS window. I get
> the entry for it displayed with the header at the top of the screen.
> If I double click on it in the LHS window the display goes to the header
> for 3.4.1 Global Settings.
> click on aa_level in the LHS window nothing happens. Nor does anything
> happen for the next two entries, to absorption. Double clicking on
>
> just below it. But
>
> I could go on. (I often do ;-) )
>
> BTW the help for 3.6.2 does something similar.
>
> The fact that I have not seen anyone mention this makes me suspicious
> that it is something to do with my system. If that is so what can I do?
>
> Oops! there is an entry from JamesB7271 on 11th of March 2012.
>
well i think this is partially due to the reference section
reorganization ... also <indexentry> tags that weren't in the proper
place since whenever. previously with the more linear lay-out the
<indexentry> the tag could appear in the section just before the /real/
landing place so you wouldn't have to scroll up slightly to be at the
beginning of the target section. the re-org was done hastily in that
when the section was moved, care wasn't taken to make sure that the tag
was also moved. having said all that i /have/ fixed those problems as
i've came across them, but have postponed the herculean task to ferret
out /all/ of the problematic tags
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17/05/2013 4:33 PM, James Holsenback wrote:
> well i think this is partially due to the reference section
> reorganization ... also <indexentry> tags that weren't in the proper
> place since whenever. previously with the more linear lay-out the
> <indexentry> the tag could appear in the section just before the /real/
> landing place so you wouldn't have to scroll up slightly to be at the
> beginning of the target section. the re-org was done hastily in that
> when the section was moved, care wasn't taken to make sure that the tag
> was also moved. having said all that i /have/ fixed those problems as
> i've came across them, but have postponed the herculean task to ferret
> out /all/ of the problematic tags
This has been bugging me for years so it is not new.
Would you like me to compile a list of what I can find and either post
them here or send them to you?
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05/17/2013 11:59 AM, Stephen wrote:
> On 17/05/2013 4:33 PM, James Holsenback wrote:
>> well i think this is partially due to the reference section
>> reorganization ... also <indexentry> tags that weren't in the proper
>> place since whenever. previously with the more linear lay-out the
>> <indexentry> the tag could appear in the section just before the /real/
>> landing place so you wouldn't have to scroll up slightly to be at the
>> beginning of the target section. the re-org was done hastily in that
>> when the section was moved, care wasn't taken to make sure that the tag
>> was also moved. having said all that i /have/ fixed those problems as
>> i've came across them, but have postponed the herculean task to ferret
>> out /all/ of the problematic tags
>
> This has been bugging me for years so it is not new.
> Would you like me to compile a list of what I can find and either post
> them here or send them to you?
>
We could probably gain a little more traction if I was to let you (and
anyone else who wants to) go after those as you find them. I'd be
willing to coach you up on the process that I've used in the past.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17/05/2013 5:33 PM, James Holsenback wrote:
>
> We could probably gain a little more traction
Pass that by me again, in English. :-P
> if I was to let you (and
> anyone else who wants to) go after those as you find them. I'd be
> willing to coach you up on the process that I've used in the past.
Hmm! Do you have a sandbox or version control or something that will
defend against ham fistedness?
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05/17/2013 12:58 PM, Stephen wrote:
> On 17/05/2013 5:33 PM, James Holsenback wrote:
>>
>> We could probably gain a little more traction
>
> Pass that by me again, in English. :-P
stand a better chance of getting it done -vs- spinning your wheels
>> if I was to let you (and
>> anyone else who wants to) go after those as you find them. I'd be
>> willing to coach you up on the process that I've used in the past.
>
> Hmm! Do you have a sandbox or version control or something that will
> defend against ham fistedness?
>
yep ... the wiki has revision control
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17/05/2013 7:33 PM, James Holsenback wrote:
> On 05/17/2013 12:58 PM, Stephen wrote:
>> On 17/05/2013 5:33 PM, James Holsenback wrote:
>>>
>>> We could probably gain a little more traction
>>
>> Pass that by me again, in English. :-P
>
> stand a better chance of getting it done -vs- spinning your wheels
>
I know, I know. I was just joshing you. ;-)
>>
>> Hmm! Do you have a sandbox or version control or something that will
>> defend against ham fistedness?
>>
>
> yep ... the wiki has revision control
Okay dokay. Count me in but be aware that I've never done anything like
this before. So it is not just the 101 course I'll need.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05/17/2013 07:03 AM, Stephen wrote:
> This may be due to my system and setup (Win7 64 bit). But in the help file:
> enter. I get a list of keywords below it and a list in the RHS window
> (okay so far). If I click on, say, adc_bailout in the RHS window. I get
> the entry for it displayed with the header at the top of the screen.
> If I double click on it in the LHS window the display goes to the header
> for 3.4.1 Global Settings.
> click on aa_level in the LHS window nothing happens. Nor does anything
> happen for the next two entries, to absorption. Double clicking on
>
> just below it. But
>
> I could go on. (I often do ;-) )
>
> BTW the help for 3.6.2 does something similar.
>
> The fact that I have not seen anyone mention this makes me suspicious
> that it is something to do with my system. If that is so what can I do?
>
> Oops! there is an entry from JamesB7271 on 11th of March 2012.
>
I reviewed all the cases you mentioned above, and the indexentry tag for
those entry /all/ appear to be in the proper place ... I'm thinking the
algorithm that produces the search-able index has some problems.
http://wiki.povray.org/content/Reference:Global_Settings
{{#indexentry:adc_bailout, global_settings}}
{{#indexentry:keyword, adc_bailout}}
==ADC_Bailout==
http://wiki.povray.org/content/Reference:Media
==Sampling Parameters & Methods==
<p>Media effects are calculated by sampling the media along the path of
the ray. It uses a process called <em>Monte Carlo integration.</em>
POV-Ray provides three different types of media sampling. The
<code>method</code> keyword lets you specify what sampling type is used.</p>
<p class="Note"><strong>Note:</strong> As of version 3.5 the default
sampling <code>method</code> is 3, and it's default for
<code>intervals</code> is 1. Sampling methods 1 and 2 have been retained
for legacy purposes.</p>
{{#indexentry:aa_threshold, media}}
{{#indexentry:keyword, aa_threshold}}
{{#indexentry:aa_level, media}}
{{#indexentry:keyword, aa_level}}
http://wiki.povray.org/content/Reference:Numeric_Expressions
{{#indexentry:abs}}
<p><code>abs(A)</code><br>Absolute value of <code>A</code>. If
<code>A</code> is negative, returns <code>-A</code> otherwise returns
<code>A</code>.</p>
{{#indexentry:acos}}
<p><code>acos(A)</code><br>Arc-cosine of <code>A</code>. Returns the
angle, measured in radians, whose cosine is <code>A</code>.</p>
http://wiki.povray.org/content/Reference:Media#Absorption
{{#indexentry:absorption, media}}
{{#indexentry:keyword, absorption}}
===Absorption===
<p>The <code>absorption</code> keyword specifies a color of light which
is absorbed when looking through the media. For example,
<code>absorption rgb<0,1,0></code> blocks the green light but
permits red and blue to get through. Therefore a white object behind the
media will appear magenta. The default value is
<code>rgb<0,0,0></code> which means no light is absorbed, meaning
all light passes through normally.</p>
http://wiki.povray.org/content/Reference:Global_Settings
{{#indexentry:charset, global_settings}}
{{#indexentry:keyword, charset}}
{{#indexentry:ascii, global_settings}}
{{#indexentry:keyword, ascii}}
{{#indexentry:utf8, global_settings}}
{{#indexentry:keyword, utf8}}
{{#indexentry:sys, global_settings}}
{{#indexentry:keyword, sys}}
==Charset==
<p>This allows you to specify the assumed character set of all text strings.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm glad this is being worked on! There are a lot of index entries that go
nowhere and are annoying.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|