 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
RC5, SuSE Linux 7.3, 128MB, P3 600
An empty .povrayrc in home directory causes POV-Ray to render a 100x100
image without displaying it on screen.
--
Felix Wiemann
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3ce93c11@news.povray.org> , Felix Wiemann <Fel### [at] gmx net>
wrote:
> RC5, SuSE Linux 7.3, 128MB, P3 600
> An empty .povrayrc in home directory causes POV-Ray to render a 100x100
> image without displaying it on screen.
So what? If you specify not appropriate settings what is supposed to happen?
POV-Ray to guess which image size and display you want when you don't tell it?
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> Felix Wiemann wrote:
>> RC5, SuSE Linux 7.3, 128MB, P3 600
>> An empty .povrayrc in home directory causes POV-Ray to render a 100x100
>> image without displaying it on screen.
>
> So what? If you specify not appropriate settings what is supposed to
> happen? POV-Ray to guess which image size and display you want when you
> don't tell it?
Use the values in povray.ini?
--
Felix Wiemann
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 20 May 2002 21:03:30 +0200, Felix Wiemann wrote:
> Thorsten Froehlich wrote:
>> Felix Wiemann wrote:
>>> RC5, SuSE Linux 7.3, 128MB, P3 600
>>> An empty .povrayrc in home directory causes POV-Ray to render a 100x100
>>> image without displaying it on screen.
>>
>> So what? If you specify not appropriate settings what is supposed to
>> happen? POV-Ray to guess which image size and display you want when you
>> don't tell it?
>
> Use the values in povray.ini?
Linux uses .rc files not .ini files, this is a hangover from your windows
day.
Let go of the past and it will all get better:-)
--
sphere{z*5,1pigment{rgb.5}finish{reflection.3specular.5}}box{<-50,-3,-50>
<50,-2,50>pigment{checker/*\__\\__/ * \_\\__*/scale 2}finish{ambient.7}}
light_source/*__\\__\\__\\__\\__\( ~ )\__\\__\\__\\__\\*/{<2,5,1>*4,1}
/*\\__\\__\\__\\__\\__\\__\\__\\__\~ -/__\\__\\__\\__\\__\\*//* Steve */
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Linux uses .rc files not .ini files, this is a hangover from your windows
> day.
From the docs, section 5.1.2 Using INI Files:
Note: although the term 'INI file' is used by POV-Ray, this was implemented
before the widespread acceptance of Microsoft Windows, and while POV-Ray's
INI files are almost identical to those of Windows, there are some minor
differences (the foremost being that it is legal to have multiple instances
of the same item in a section). INI files are used on all platform versions
of POV-Ray, not just on the Windows platform
Anders
P.S. Ingo, that note is missing a period at the end. :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3ce96a13@news.povray.org> , "Anders K." <and### [at] prostard2gcom>
wrote:
>> Linux uses .rc files not .ini files, this is a hangover from your windows
>> day.
>
> From the docs, section 5.1.2 Using INI Files:
>
> Note: although the term 'INI file' is used by POV-Ray, this was implemented
> before the widespread acceptance of Microsoft Windows, and while POV-Ray's
> INI files are almost identical to those of Windows, there are some minor
> differences (the foremost being that it is legal to have multiple instances
> of the same item in a section). INI files are used on all platform versions
> of POV-Ray, not just on the Windows platform
It says nothing about povray.ini being read at startup, does it? Actually, it
can't because that is a platform specific thing, so:
The Unix documentation however, does still call the file povray.ini while it
should say povray.rc...
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> Anders K. wrote:
>> From the docs, section 5.1.2 Using INI Files:
>>
>> Note: although the term 'INI file' is used by POV-Ray, this was
>> implemented before the widespread acceptance of Microsoft Windows, and
>> while POV-Ray's INI files are almost identical to those of Windows, there
>> are some minor differences (the foremost being that it is legal to have
>> multiple instances of the same item in a section). INI files are used on
>> all platform versions of POV-Ray, not just on the Windows platform
>
> It says nothing about povray.ini being read at startup, does it?
It doesn't, but:
There's a povray.ini in povray35 (and if there isn't, POV-Ray generates a
warning).
The windows version uses povray.ini, so the unix version should do so, too.
> Actually, it can't because that is a platform specific thing, so:
Why? There's no problem having a povray.ini on any system (AFAIK at least).
> The Unix documentation however, does still call the file povray.ini while
> it should say povray.rc...
When do people learn that Unix doesn't need those stupid windows
extensions? ;) The file is called ".povrayrc".
README.unix says:
The default povray.ini file that is shipped with the Unix archive
assumes that POV-Ray will be installed under /usr/local/lib/povray31.
If you are not installing POV-Ray there, you should edit the
Library_Path specifications in this file to point to the location
where POV-Ray is installed. Each user should copy this file to
".povrayrc" in their home directory.
So it's not a bug that POV-Ray doesn't read povray.ini if there's .povrayrc
in home directory, but it's IMO not the expected behavior. I think it might
really be a better solution to read .povrayrc *and* povray.ini because
otherwise the user probably would have to copy povray.ini. The
configuration in povray.ini makes much more sense than (some of) POV-Ray's
default values.
BTW, README.unix (and maybe README, too) have to be UPDATED!
--
Felix Wiemann
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 21 May 2002 04:22:35 -0400, Felix Wiemann wrote:
> So it's not a bug that POV-Ray doesn't read povray.ini if there's
> .povrayrc in home directory, but it's IMO not the expected behavior. I
> think it might really be a better solution to read .povrayrc *and*
> povray.ini because otherwise the user probably would have to copy
> povray.ini. The configuration in povray.ini makes much more sense than
> (some of) POV-Ray's default values.
The general rule is that more specific files trump less specific files.
There's a system-wide default povray.ini, which can be overridden by a
user-level ~/.povrayrc. All of this is very typical Unix behavior, though
system-level files are likely to be found in /etc rather than
/usr/local/lib/povray* and end in .conf rather than .ini. Beyond that, a
more specific collection of default settings can be defined per directory,
which defines things at a project level, which is more specific than
either the user or system level.
Merging collections of settings rather than ignoring everything but the
most specific file isn't a bad idea, but it's a bit late for 3.5. Perhaps
the best thing to do is to copy povray.ini to ~/.povrayrc as specified in
the docs, edit as needed, and copy .povrayrc to foo/povray.ini when
starting a new project, explicitly specifying all settings at each level.
> BTW, README.unix (and maybe README, too) have to be UPDATED!
True, there are a bunch of 3.1 references still in there.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
