Manual talk:Text Editor Search Paths

The page talks about "Import Library Paths from POVRAY.INI " There are two places this file can be found, the global one in ..ini/povray.ini, and a local one in the current directory. Does this option look in both places?

I believe POV-Ray read in ..ini/povray.ini and then reads (if found) the local povray.ini, and then the Myfile.ini when rendering.

Stephen S

A local file in the current directory or a local file in the current user documents directory? From my observations, I've learned only that POV-Ray 3.6.1 and POV-Ray 3.6.2 look for this file in different places: POV-Ray 3.6.1 looks for this file in the ini directory under the installation folder and POV-Ray 3.6.2 looks for this file in the ini directory of the POV-Ray folder under My Documents (I've learned it recently and this behavior will be implemented in Bishop3D 1.0.4.0).

Hugo Arnaut 18:12, 27 June 2009 (UTC)

I'm thinking of 1.3 of the winpov help: 1.3 command-line options section 2 ''You can store it in a POVRAY.INI file in the current directory. POV-Ray looks for a POVRAY.INI file in the current directory whenever it starts rendering, but after it has read any POVRAY.INI file in the POV-Ray's "RENDERER" directory. Options in an INI file in the current directory override options in any copy of POVRAY.INI in the POV-Ray's "home" directory.''

--StephenS 20:55, 27 June 2009 (UTC)

I didn't know about local POVRAY.INI files... Anyway, Bishop3D can't expect any relevance of current directory at the time the import paths from POVRAY.INI takes place; therefore I think Bishop3D should only look for the global POVRAY.INI. I've changed the text of the explanation slightly (feel free to polish it).

PS. I think the POV-Ray manual section 1.3 is wrong, the global POVRAY.INI is kept in the INI folder and not in the RENDERER folder, or am I wrong?

--Hugo Arnaut 22:45, 27 June 2009 (UTC)

Please ignore the note above. The manual is correct.

--Hugo Arnaut 17:43, 30 June 2009 (UTC)