In v3.7 RC7;
With reference to "2.2.8.2  Using INI Files", and sample with "MOREOPT   ;
Read MOREOPT.INI and continue with next line".
Including an ini file in another ini file; gives a message
"unknown key"
File renders ok

This error was noted back 20Apr2006. Is there a fix or a work-around?

Post a reply to this message

> In v3.7 RC7;
> With reference to "2.2.8.2  Using INI Files", and sample with "MOREOPT   ;
> Read MOREOPT.INI and continue with next line".
> Including an ini file in another ini file; gives a message
> "unknown key"
> File renders ok
>
> This error was noted back 20Apr2006. Is there a fix or a work-around?
>
>

How deep are your ini files nested?
I've rendered several files with nested ini files without ever 
encoutering that error message. Normaly, I hardly have any nesting 
deeper than 3 or 4.

Is it possible that one ini file tries to include a file that ultimately 
include it? In that case, you must have something like this:

#ifndef(This_Include)
#declare This_Include = version;
.
.
body if the include file
.
.
#end

That way, if the inc file have already been included, it won't get 
parsed a second time.



Alain

Post a reply to this message

Alain <kua### [at] videotronca> wrote:
> How deep are your ini files nested?
> I've rendered several files with nested ini files without ever
> encoutering that error message. Normaly, I hardly have any nesting
> deeper than 3 or 4.
>
> Is it possible that one ini file tries to include a file that ultimately
> include it? In that case, you must have something like this:
>
> #ifndef(This_Include)
> #declare This_Include = version;
> .
> .
> body if the include file
> .
> .
> #end
>
> That way, if the inc file have already been included, it won't get
> parsed a second time.

Are you talking about .ini files or .inc files?

Post a reply to this message

> Alain <kua### [at] videotronca> wrote:
>> How deep are your ini files nested?
>> I've rendered several files with nested ini files without ever
>> encoutering that error message. Normaly, I hardly have any nesting
>> deeper than 3 or 4.
>>
>> Is it possible that one ini file tries to include a file that ultimately
>> include it? In that case, you must have something like this:
>>
>> #ifndef(This_Include)
>> #declare This_Include = version;
>> .
>> .
>> body if the include file
>> .
>> .
>> #end
>>
>> That way, if the inc file have already been included, it won't get
>> parsed a second time.
>
> Are you talking about .ini files or .inc files?
>
>
>
Oups! My mistake. I almost never use ini files and missed the difference.

Anyway, is it possible that one ini file may have a reference to a 
previous one?

Post a reply to this message

Alain <kua### [at] videotronca> wrote:

> > Alain <kua### [at] videotronca> wrote:
> >> How deep are your ini files nested?
> >> I've rendered several files with nested ini files without ever
> >> encoutering that error message. Normaly, I hardly have any nesting
> >> deeper than 3 or 4.
> >>
> >> Is it possible that one ini file tries to include a file that ultimately
> >> include it? In that case, you must have something like this:
> >>
> >> #ifndef(This_Include)
> >> #declare This_Include = version;
> >> .
> >> .
> >> body if the include file
> >> .
> >> .
> >> #end
> >>
> >> That way, if the inc file have already been included, it won't get
> >> parsed a second time.
> >
> > Are you talking about .ini files or .inc files?
> >
> >
> >
> Oups! My mistake. I almost never use ini files and missed the difference.
>
> Anyway, is it possible that one ini file may have a reference to a
> previous one?
No, there are no references to previous ini files. In fact, running the example
in the help section will generate the error messages.

I think its just a mess-up in how the error messages are handled. If there is
another 'real' error in the code, then the reported error message does not make
any sense and editor opens up in a line that does have the real error. Remove
the reference to the ini file in the original ini file and then the actual error
is reported correctly.

As mentioned previously, the ini error messages does not stop POV from rendering
the one scene. I have not tried to see if an animation sequence will continue
through this error message.

Post a reply to this message

"Dr JC" <nomail@nomail> wrote:
> In v3.7 RC7;
> With reference to "2.2.8.2  Using INI Files", and sample with "MOREOPT   ;
> Read MOREOPT.INI and continue with next line".
> Including an ini file in another ini file; gives a message
> "unknown key"
> File renders ok
>
> This error was noted back 20Apr2006. Is there a fix or a work-around?

Also, my documentation reads MOREOPT, MYOPTS, and RERUN to refer to the files
moreopt.ini, myopts.ini, and rerun.ini.  This will not work in Linux or in Unix,
as the files names in these OSs are case-sensitive.

Post a reply to this message