 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I wonder if there is a sense to explain in documentation what 'current
directory' means. I mean - what is 'current directory' in case of parsing
include file. Personaly I expect it is directory where include file is but
looks like it is directory of main scenefile (probably becouse of security
issues). I think 6.2.1 and 5.2.3.4 could be more precise in this part ( or I'm
not understanding some part of English ( or I'm a little oversensitive ( or
I'm missed some chapter with better explanation ))).
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> I wonder if there is a sense to explain in documentation what 'current
> directory' means. I mean - what is 'current directory' in case of parsing
> include file. Personaly I expect it is directory where include file is but
> looks like it is directory of main scenefile (probably becouse of security
> issues). I think 6.2.1 and 5.2.3.4 could be more precise in this part ( or I'm
> not understanding some part of English ( or I'm a little oversensitive ( or
> I'm missed some chapter with better explanation ))).
With a command line version of POV-Ray is should be clear what 'current
directory' means, it's probably because POV-Ray has been a command line
program in general in the past that this is not explained more detailed.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 02 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 04 Jun 2002 17:48:42 +0200, Christoph Hormann <chr### [at] gmx de>
wrote:
> With a command line version of POV-Ray is should be clear what 'current
> directory' means...
Is it directory where POV-Ray launched, POV-Ray exacutable is located,
scenefile is located or ini file is located ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Is it directory where POV-Ray launched, POV-Ray exacutable is located,
> scenefile is located or ini file is located ?
'Current directory' is always the 'working directory', ie. the directory
where you are currently, ie. the directory where you launch POV-Ray.
(In fact, in unix it's not easy for programs to know where they are
located exactly.)
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 4 Jun 2002 12:45:54 -0400, Warp <war### [at] tagpovrayorg> wrote:
> W?odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
> > Is it directory where POV-Ray launched, POV-Ray exacutable is located,
> > scenefile is located or ini file is located ?
>
> 'Current directory' is always the 'working directory', ie. the directory
> where you are currently, ie. the directory where you launch POV-Ray.
You mean content of 'Start in' field in MS Windows starting enviroment ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> > 'Current directory' is always the 'working directory', ie. the directory
> > where you are currently, ie. the directory where you launch POV-Ray.
>
> You mean content of 'Start in' field in MS Windows starting enviroment ?
No, i suppose the GUI versions of POV-Ray handle this on a per scene
basis, therefore a more detailed explanation of theis would belong in the
platform specific docs.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 02 Jun. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
news:3rrpfu8f5t7mvn5rj4ebgjc8jgncnakiu5@4ax.com...
> On 4 Jun 2002 12:45:54 -0400, Warp <war### [at] tagpovrayorg> wrote:
> > W?odzimierz ABX Skiba <abx### [at] babilonorg> wrote:
> > > Is it directory where POV-Ray launched, POV-Ray exacutable is located,
> > > scenefile is located or ini file is located ?
> >
> > 'Current directory' is always the 'working directory', ie. the directory
> > where you are currently, ie. the directory where you launch POV-Ray.
>
> You mean content of 'Start in' field in MS Windows starting enviroment ?
Where current open file is located, whether it be pov or inc, in Windows
anyway. I think the doc is intending you to know the file being worked on
(open) is going to cause it's path to be the current directory.
While I'm here just thought I'd mention section searching is failing me in
RC5 apparently. Any valid section number in the Index keyword find box used
to locate them fine, now it is going to the text of section 5.2.2.1.3
Interrupting Options.
This could be an isolated problem at the moment so I'll check on it again
later and post at the beta-test group later if it is still broken.
bob h
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 4 Jun 2002 13:09:22 -0500, "bob h" <omn### [at] charternet> wrote:
> Where current open file is located, whether it be pov or inc, in Windows
> anyway. I think the doc is intending you to know the file being worked on
> (open) is going to cause it's path to be the current directory.
You are right probably. Here is simple example what confused me - I have 3
files with following content:
C:\SCENE\SCENE.POV : #include "c:\test\test1.inc"
C:\TEST\TEST1.INC : #include "test2.inc"
C:\TEST\TEST2.INC : #debug "test\n"
When I open in WinPOV3.5RC5 SCENE.POV and start parsing then it fails on
#include keyword in TEST1.
File: c:\test\test1.inc Line: 1
Error: Could not find file 'test2.inc'
File: c:\test\test1.inc Line: 1
#include "test2.inc"
<----ERROR
Parse Error: Cannot open include file test2.inc.
File: c:\test\test1.inc Line: 1
Warning: Check that the file is in a directory specifed with a +L switch
or 'Library_Path=' .INI item. Standard include files are in the
include directory or folder. Please read your documentation carefully.
I want to point that documentation is not very accurate in this content.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
