The following Line in a batch file:

bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"

Please note the chr$(34) (=") around the path.
Gives the following error (below).

Seems that POV does not allow pathes with whitespaces at all outside of
".ini"-Files ?
If that is the case what do I do if the ".ini" File is somewhere where there
are whitespaces in
the file-path ?

If that behavior is wanted, it would be good to know.

thanks
--Theo

PS: :

**********
This Windows version by Christopher J. Cason
Possible Command Line Error: Could not open INI file
'f:\00_rpgm\01_bs\01_projekte\smpov'.
Possible Command Line Error: Could not open INI file
'1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini""'.
Parsing Options
...

Returned from renderer with error status

Post a reply to this message

On Tue, 13 Aug 2002 17:33:17 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:
> The following Line in a batch file:

only in batch file ?

> If that behavior is wanted, it would be good to know.

I don't know but you can always try short names equivalent.

ABX

Post a reply to this message

Hmmm ... to change all pathes to "short-name equivalent" first.

It could be a sollution if we would know that the resulting file would
always run on THAT particular computer. Which is infact NOT the case here
:-).

Hmmm. If there is no sollution to give the full path to POV, I guess I have
to restrict the proggy to a "non whitespace path".

thanks

--Theo

"ABX" <abx### [at] babilonorg> schrieb im Newsbeitrag
news:vo9iluktdb0a3th9s7pqmpqr99g98mgbsd@4ax.com...
> On Tue, 13 Aug 2002 17:33:17 +0200, "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
> > The following Line in a batch file:
>
> only in batch file ?
>
> > If that behavior is wanted, it would be good to know.
>
> I don't know but you can always try short names equivalent.
>
> ABX

Post a reply to this message

On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:
> Hmmm. If there is no sollution to give the full path to POV, I guess I have
> to restrict the proggy to a "non whitespace path".

I have just tested as
  pvengin.exe "abx test.ini"
and it worked fine. No idea what could be wrong in your situation.

ABX

Post a reply to this message

Sounds intresting to me. I have win2k. My POV does as if the """ would not
be there.
Do you have W2k or ... ?

--Theo

"ABX" <abx### [at] babilonorg> schrieb im Newsbeitrag
news:t2biluk6a6ijm0onqr5r9q3eci07eribo4@4ax.com...
> On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
> > Hmmm. If there is no sollution to give the full path to POV, I guess I
have
> > to restrict the proggy to a "non whitespace path".
>
> I have just tested as
>   pvengin.exe "abx test.ini"
> and it worked fine. No idea what could be wrong in your situation.
>
> ABX

Post a reply to this message

In article <3d5926a8@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> Seems that POV does not allow pathes with whitespaces at all outside of
> ".ini"-Files ?

It is not POV-Ray's problem but that of your shell.  It separates the path
into two separate arguments.  Read up in your shell documentation how to
specify special characters in command lines.

    Thorsten

Post a reply to this message

On Tue, 13 Aug 2002 18:53:37 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:
> Sounds intresting to me.
> I have win2k.

NT4 Sp6 here.

ABX

Post a reply to this message

Good to know. My shell is the CMD.exe from W2k.
However, 'll take that problem for Version 2 ...
thanks for trying
-Theo


"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d593ab2$1@news.povray.org...
> In article <3d5926a8@news.povray.org> , "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
>
> > Seems that POV does not allow pathes with whitespaces at all outside of
> > ".ini"-Files ?
>
> It is not POV-Ray's problem but that of your shell.  It separates the path
> into two separate arguments.  Read up in your shell documentation how to
> specify special characters in command lines.
>
>     Thorsten

Post a reply to this message

Try putting the parameter into quotation marks.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

I did that, they have been in Quotation marks (=chr$(34) - isn't ?).

"Warp" <war### [at] tagpovrayorg> schrieb im Newsbeitrag
news:3d5a7357@news.povray.org...
>   Try putting the parameter into quotation marks.
>
> --
> #macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb
x]
> [1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
> -1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// -
Warp -

Post a reply to this message

Theo Gottwald * wrote:
> 
> I did that, they have been in Quotation marks (=chr$(34) - isn't ?).

Quotation marks - ""

-- 
Ken Tyler

Post a reply to this message

"Ken" <tyl### [at] pacbellnet> wrote in message
news:3D5AFC2D.6C2F62D7@pacbell.net...
>
>
> Theo Gottwald * wrote:
> >
> > I did that, they have been in Quotation marks (=chr$(34) - isn't ?).
>
> Quotation marks - ""
>


    The point Theo is trying to make, and is actually quite clear from his
original post, is that the parameter _was_ in Quotation marks. chr$(34), as
Theo puts it, _is_ a quotation mark. To quote from Theos original question :

"The following Line in a batch file:

bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"

Please note the chr$(34) (=") around the path."

See, he even makes a point of stating that he is using quotation marks
around the file path parameter.

So, Theos original question still stands - why does this not work ?
--
Pandora/Scott Hill/[::O:M:C::]Scorpion
Software Engineer.
http://www.pandora-software.com

Post a reply to this message

Yes, ... they say its because of the Win2k-shell.
One person reports that he can do it under WinNT.

However due to these problems SMPOV (www.it-berater.org/smpov.htm )
has a text-file which say that you have to avoid pathes with whitespaces.

(In fact Pandora is right - we are not 100% shure why it does not work here
on my PC's ...)

--Theo

"Pandora" <pan### [at] pandora-softwarecom> schrieb im Newsbeitrag
news:3d5b07e0@news.povray.org...
> "Ken" <tyl### [at] pacbellnet> wrote in message
> news:3D5AFC2D.6C2F62D7@pacbell.net...
> >
> >
> > Theo Gottwald * wrote:
> > >
> > > I did that, they have been in Quotation marks (=chr$(34) - isn't ?).
> >
> > Quotation marks - ""
> >
>
>
>     The point Theo is trying to make, and is actually quite clear from his
> original post, is that the parameter _was_ in Quotation marks. chr$(34),
as
> Theo puts it, _is_ a quotation mark. To quote from Theos original question
:
>
> "The following Line in a batch file:
>
> bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
> 1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"
>
> Please note the chr$(34) (=") around the path."
>
> See, he even makes a point of stating that he is using quotation marks
> around the file path parameter.
>
> So, Theos original question still stands - why does this not work ?
> --
> Pandora/Scott Hill/[::O:M:C::]Scorpion
> Software Engineer.
> http://www.pandora-software.com
>
>

Post a reply to this message

On Thu, 15 Aug 2002 06:42:38 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:

>(In fact Pandora is right - we are not 100% shure why it does not work here
>on my PC's ...)

What are your regional settings?


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

"Theo Gottwald *" <The### [at] t-onlinede> wrote in message
news:3d5b3128@news.povray.org...
> Yes, ... they say its because of the Win2k-shell.
> One person reports that he can do it under WinNT.
>
> However due to these problems SMPOV (www.it-berater.org/smpov.htm )
> has a text-file which say that you have to avoid pathes with whitespaces.
>
> (In fact Pandora is right - we are not 100% shure why it does not work
here
> on my PC's ...)
>


    And the cmd shell has changed very little, if it all, between NT4 and
2K. I can see absolutely no reason why it should not work on your machine,
as you have described the problem.

--
Pandora/Scott Hill/[::O:M:C::]Scorpion
Software Engineer.
http://www.pandora-software.com

Post a reply to this message

POV-Ray will render files with spaces in their names from the command 
line, but it fails if there is a space in a *directory* that is 
specified in the path.

this works: pvengine "the image.pov"
this does not: pvengine "a folder with spaces\image.pov"

I'm also using Win2k.

Note that this CANNOT be a problem with the shell, as the command line 
is passed as one string to WinMain, or via GetCommandLine in Windows. 
The application is responsible for splitting out parameters.  (usually 
in the C runtime startup code before calling main, so it still may be 
outside of the POV code)

-josh

Post a reply to this message

"Josh Seagoe" <rab### [at] junocom> wrote in message
news:3d5b3e36@news.povray.org...
> POV-Ray will render files with spaces in their names from the command
> line, but it fails if there is a space in a *directory* that is
> specified in the path.
>
> this works: pvengine "the image.pov"
> this does not: pvengine "a folder with spaces\image.pov"
>


    Ah! A question for the WinPOV developer(s) :

    Is WinPOV parsing the directory path part separately from the filename
using strtok ? and is it being passed a delimiter list that includes 'space'
?

--
Pandora/Scott Hill/[::O:M:C::]Scorpion
Software Engineer.
http://www.pandora-software.com

Post a reply to this message

Then maybe we open a separate thread here with that ?
I am not shure if the developers read every small posting.

However seems you got the point.

--Theo

"Josh Seagoe" <rab### [at] junocom> schrieb im Newsbeitrag
news:3d5b3e36@news.povray.org...
> POV-Ray will render files with spaces in their names from the command
> line, but it fails if there is a space in a *directory* that is
> specified in the path.
>
> this works: pvengine "the image.pov"
> this does not: pvengine "a folder with spaces\image.pov"
>
> I'm also using Win2k.
>
> Note that this CANNOT be a problem with the shell, as the command line
> is passed as one string to WinMain, or via GetCommandLine in Windows.
> The application is responsible for splitting out parameters.  (usually
> in the C runtime startup code before calling main, so it still may be
> outside of the POV code)
>
> -josh
>
>
>

Post a reply to this message

In article <3d5b3e36@news.povray.org> , Josh Seagoe <rab### [at] junocom>  
wrote:

> Note that this CANNOT be a problem with the shell, as the command line
> is passed as one string to WinMain, or via GetCommandLine in Windows.
> The application is responsible for splitting out parameters.  (usually
> in the C runtime startup code before calling main, so it still may be
> outside of the POV code)

Well, given that the source code is available, isn't this guessing game
redundant?

    Thorsten

Post a reply to this message

In article <3d5926a8@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
> 1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"

Did you try to put "/RENDER" in front of the path in the various possible
combinations?

    Thorsten

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3d5b51a6$1@news.povray.org...
>
> Well, given that the source code is available, isn't this guessing game
> redundant?
>


    Have you actually looked at the startup code for WinPOV ? It's quite
complex - the developers are for more likely than any of us, mere mortals
(even a software engineer like me), to be able to quickly find the source of
this bug and fix it - information like this will be helpful to them in
knowing where in the source the bug is likely to reside.
    Having said that, and having thought about it a little, I think this
could be quite a difficult bug to fix - it's probably caused by the fact
that you can pass a number of command line parameters to pov and the
parameters are separated by spaces... though why, then, spaces in the file
name work ok, but spaces in the directory path doesn't, I'm not sure...

--
Pandora/Scott Hill/[::O:M:C::]Scorpion
Software Engineer.
http://www.pandora-software.com

Post a reply to this message

Principially  you are right, Torsten.

In this particular case....

If I 'll go and search mistakes in the POV-Sourcecode,
you'll have to render with watercolor and paper next week :-).

**********************************************


"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5b51a6$1@news.povray.org...
> In article <3d5b3e36@news.povray.org> , Josh Seagoe <rab### [at] junocom>
> wrote:
>
> > Note that this CANNOT be a problem with the shell, as the command line
> > is passed as one string to WinMain, or via GetCommandLine in Windows.
> > The application is responsible for splitting out parameters.  (usually
> > in the C runtime startup code before calling main, so it still may be
> > outside of the POV code)
>
> Well, given that the source code is available, isn't this guessing game
> redundant?
>
>     Thorsten

Post a reply to this message

No i did not.
can I hear out of your message that this would change something ?


"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5b51f6$1@news.povray.org...
> In article <3d5926a8@news.povray.org> , "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
>
> > bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
> > 1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"
>
> Did you try to put "/RENDER" in front of the path in the various possible
> combinations?
>
>     Thorsten

Post a reply to this message

On Tue, 13 Aug 2002 18:59:42 +0200, ABX <abx### [at] babilonorg> wrote:

>On Tue, 13 Aug 2002 18:53:37 +0200, "Theo Gottwald *"
><The### [at] t-onlinede> wrote:
>> Sounds intresting to me.
>> I have win2k.
>
>NT4 Sp6 here.
>
>ABX
I've just tried

pvengine "c:\program files\pov-ray for windows v3.5\insert
menu\images.ini"

on WinXP Pro and got the following in the message window


Calling rendering engine with parameters '"c:\program files\pov-ray
for windows v3.5\insert menu\images.ini"'
Preset INI file is 'C:\PROGRAM FILES\POV-RAY FOR WINDOWS
V3.5\RENDERER\QUICKRES.INI', section is '[320x240, No AA]'.
Rendering using command line '"c:\program files\pov-ray for windows
v3.5\insert menu\images.ini"'.
Persistence of Vision(tm) Ray Tracer Version 3.5 win32 (.icl)
  This is an official version prepared by the POV-Ray Team. See the
   documentation on how to contact the authors or visit us on the
   internet at http://www.povray.org/.
Copyright 1991-2002 POV-Ray Team(tm)
This Windows version by Christopher J. Cason
Possible Command Line Error: Could not open INI file 'c:\program'.
Possible Command Line Error: Could not open INI file 'files\pov-ray'.
Possible Command Line Error: Could not open INI file 'for'.
Possible Command Line Error: Could not open INI file 'windows'.
Possible Command Line Error: Could not open INI file 'v3.5\insert'.
Possible Command Line Error: Could not open INI file
'menu\images.ini'.

<snip>

Post a reply to this message

In article <3d5b56c5$1@news.povray.org> , "Pandora" 
<pan### [at] pandora-softwarecom> wrote:

> Have you actually looked at the startup code for WinPOV ?

Yes it is complex and looking at the code will be a bit more difficult.
However, I usually use a debugger to track such bugs.  Then it is really
easy.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d5b6c53$1@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> can I hear out of your message that this would change something ?

Yes, of course.  Under WinDOS 2000 this works just fine...

pvengine /RENDER "c:\Programme\POV-Ray for Windows\ini\test.ini"

    Thorsten

Post a reply to this message

On Tue, 13 Aug 2002 17:58:21 +0200, ABX <abx### [at] babilonorg> wrote:

>On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
><The### [at] t-onlinede> wrote:
>> Hmmm. If there is no sollution to give the full path to POV, I guess I have
>> to restrict the proggy to a "non whitespace path".
>
>I have just tested as
>  pvengin.exe "abx test.ini"
>and it worked fine. No idea what could be wrong in your situation.
>
>ABX

I've just had a look at the source code and I can see why it's not
working for myself or Theo - what I can't understand is why it works
for ABX. The source code doesn't seem to be different for W2k/XP and
NT4. The only thing I can think of is to ask ABX whether he has
test.ini as well as "abx test.ini" in his folder?

Cheers,

Scott

Post a reply to this message

Thorsten said, that the /RENDER switch will solve the problem.

--Theo


"Scott Moore" <sdm### [at] zoomcouk> schrieb im Newsbeitrag
news:9e5nlucq0g1ep9ncg9nsea3j7n86p56h58@4ax.com...
> On Tue, 13 Aug 2002 17:58:21 +0200, ABX <abx### [at] babilonorg> wrote:
>
> >On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
> ><The### [at] t-onlinede> wrote:
> >> Hmmm. If there is no sollution to give the full path to POV, I guess I
have
> >> to restrict the proggy to a "non whitespace path".
> >
> >I have just tested as
> >  pvengin.exe "abx test.ini"
> >and it worked fine. No idea what could be wrong in your situation.
> >
> >ABX
>
> I've just had a look at the source code and I can see why it's not
> working for myself or Theo - what I can't understand is why it works
> for ABX. The source code doesn't seem to be different for W2k/XP and
> NT4. The only thing I can think of is to ask ABX whether he has
> test.ini as well as "abx test.ini" in his folder?
>
> Cheers,
>
> Scott

Post a reply to this message

On Thu, 15 Aug 2002 14:38:39 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:

>Thorsten said, that the /RENDER switch will solve the problem.
>
>--Theo
>

Yes, I saw his post but the documentation (5.1.2) says

You may specify additional INI files on the command-line by simply
typing the file name on the command line. For example:

  POVRAY MYOPTS.INI


Does this mean the docs need to be updated to mention that spaces in
the filename aren't allowed?

(BTW. As I'm mentioning the docs, do all platforms build the source to
pvengine or povray? On Windows the .exe is pvengine - but the docs, as
shown above, suggest it's povray.exe - do the docs need updating for
this also?)

Cheers,

Scott

Post a reply to this message

In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore 
<sdm### [at] zoomcouk>  wrote:

> Does this mean the docs need to be updated to mention that spaces in
> the filename aren't allowed?
>
> (BTW. As I'm mentioning the docs, do all platforms build the source to
> pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> shown above, suggest it's povray.exe - do the docs need updating for
> this also?)

The documentation is clear that it is about the command-line version of
POV-Ray, not the GUI versions and it does refer you to the GUI version
documentation for specifics of those versions.  Where?  Well, in the
introduction of the command-line options in section 5 in case you missed it.

If you don't read the documentation carefully and get burned that is not a
bug in POV-Ray but in your method of reading the documentation.  The
suggested way to read it is from section 1 to the last section.  It is not
recommended to use it for reference purposes only.  That way you _will_ miss
very important details!

    Thorsten

Post a reply to this message

For myself I can say that I even printed out on paper all pages that seemed
to be about that.

- The genreal output optins
- Tracing options
- Shell Output Options
- etc.

and I did not understand that even there is a command like /RENDER
but that is the place where i would have expected to find it. (MY mistake ?)

One thing is true, me and - be honest 99% of all people - (IF they read
instructions) they take them
part by part when they need it.

I can however state here that this works perfect: now (and I did not expect
anything else):


********
bin\pvengine.exe  /EXIT /RENDER "D:\Dokumente und
Einstellungen\user@teop\Desktop\White space
betwen\COM\abyss_08152002_174636_87176_1_0x0-80x120a.ini"
********

--Theo
"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5bbd65$1@news.povray.org...
> In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore
> <sdm### [at] zoomcouk>  wrote:
>
> > Does this mean the docs need to be updated to mention that spaces in
> > the filename aren't allowed?
> >
> > (BTW. As I'm mentioning the docs, do all platforms build the source to
> > pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> > shown above, suggest it's povray.exe - do the docs need updating for
> > this also?)
>
> The documentation is clear that it is about the command-line version of
> POV-Ray, not the GUI versions and it does refer you to the GUI version
> documentation for specifics of those versions.  Where?  Well, in the
> introduction of the command-line options in section 5 in case you missed
it.
>
> If you don't read the documentation carefully and get burned that is not a
> bug in POV-Ray but in your method of reading the documentation.  The
> suggested way to read it is from section 1 to the last section.  It is not
> recommended to use it for reference purposes only.  That way you _will_
miss
> very important details!
>
>     Thorsten

Post a reply to this message

In article <3d5bcf0b@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> and I did not understand that even there is a command like /RENDER
> but that is the place where i would have expected to find it. (MY mistake ?)

Yes.  Try section 1.9.1 (the platform specific part of the help), which
explains to you that you can give it certain command line options to the GUI
version in the first place.  It also does not seem to suggest anywhere that
it will work without the /RENDER option at all...

    Thorsten

Post a reply to this message

On Thu, 15 Aug 2002 16:40:33 +0200, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore 
><sdm### [at] zoomcouk>  wrote:
>
>> Does this mean the docs need to be updated to mention that spaces in
>> the filename aren't allowed?
>>
>> (BTW. As I'm mentioning the docs, do all platforms build the source to
>> pvengine or povray? On Windows the .exe is pvengine - but the docs, as
>> shown above, suggest it's povray.exe - do the docs need updating for
>> this also?)
>
>The documentation is clear that it is about the command-line version of
>POV-Ray, not the GUI versions and it does refer you to the GUI version
>documentation for specifics of those versions.  Where?  Well, in the
>introduction of the command-line options in section 5 in case you missed it.
>
>If you don't read the documentation carefully and get burned that is not a
>bug in POV-Ray but in your method of reading the documentation.  The
>suggested way to read it is from section 1 to the last section.  It is not
>recommended to use it for reference purposes only.  That way you _will_ miss
>very important details!
>
>    Thorsten

I never said there was a bug - I merely asked two questions ... the
answer of which were no. I guess it's a problem with your method of
reading emails 8o)

Cheers,

Scott

Post a reply to this message

We should accept here, that Thorsten has put a lot of time and work in the
POV-project,
while we "nebies" just come here and do get all things "on the silver
plate".

I can understand that this is sometimes annoying for him.

However Thorsten, we are grateful for you efforts and patience.

--Theo


"Scott Moore" <sdm### [at] zoomcouk> schrieb im Newsbeitrag
news:kgonlugsq8g3erdttrhqmbrgv9ai2armiv@4ax.com...
> On Thu, 15 Aug 2002 16:40:33 +0200, "Thorsten Froehlich"
> <tho### [at] trfde> wrote:
>
> >In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore
> ><sdm### [at] zoomcouk>  wrote:
> >
> >> Does this mean the docs need to be updated to mention that spaces in
> >> the filename aren't allowed?
> >>
> >> (BTW. As I'm mentioning the docs, do all platforms build the source to
> >> pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> >> shown above, suggest it's povray.exe - do the docs need updating for
> >> this also?)
> >
> >The documentation is clear that it is about the command-line version of
> >POV-Ray, not the GUI versions and it does refer you to the GUI version
> >documentation for specifics of those versions.  Where?  Well, in the
> >introduction of the command-line options in section 5 in case you missed
it.
> >
> >If you don't read the documentation carefully and get burned that is not
a
> >bug in POV-Ray but in your method of reading the documentation.  The
> >suggested way to read it is from section 1 to the last section.  It is
not
> >recommended to use it for reference purposes only.  That way you _will_
miss
> >very important details!
> >
> >    Thorsten
>
> I never said there was a bug - I merely asked two questions ... the
> answer of which were no. I guess it's a problem with your method of
> reading emails 8o)
>
> Cheers,
>
> Scott
>

Post a reply to this message

Thorsten Froehlich wrote:
> In article <3d5b3e36@news.povray.org> , Josh Seagoe <rab### [at] junocom>  
> wrote:
> 
>>Note that this CANNOT be a problem with the shell, as the command line
>>is passed as one string to WinMain, or via GetCommandLine in Windows.
>>The application is responsible for splitting out parameters.  (usually
>>in the C runtime startup code before calling main, so it still may be
>>outside of the POV code)
> 
> Well, given that the source code is available, isn't this guessing game
> redundant?

Yes, but it takes a while to download and unzip the source, then locate 
the appropriate file and find the code within it, especially for someone 
who's never really delt with this code before.  (and using a debugger 
would require compiling it all)  OTOH, I know immediately from 
experience that the shell is not responsible for parsing like that under 
Windows.

-josh

Post a reply to this message

In article <3d5bfd26@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> We should accept here, that Thorsten has put a lot of time and work in the
> POV-project, while we "nebies" just come here and do get all things "on the
> silver plate".
>
> I can understand that this is sometimes annoying for him.

No, not that ;-)  I only have a problem when the newbies look on the silver
plate and start complaining about it not being polished well enough :-(

Apart from that, what I really hate is when people just appear and make
suggestions or complain without even knowing anything about the subject.
Nothing else gets me aggressive more quickly.

Especially as I have to admit that I know only as much as anybody else can
find out in a few minutes about many parts of the POV-Ray core code.  It is
just too complex for a single person to understand it completely.  Yet, if a
person never looks into it at all but still makes suggestions and
assumptions how POV-Ray behaves or should behave they are wrong 99.9% of the
time and their laziness only wastes everybodies time reading the nonsense...

> However Thorsten, we are grateful for you efforts and patience.

Thanks.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d5c0495@news.povray.org> , Josh Seagoe <rab### [at] junocom>  
wrote:

> Yes, but it takes a while to download and unzip the source, then locate
> the appropriate file and find the code within it, especially for someone
> who's never really delt with this code before.

Hey, I don't look into the Windows frontend source code too often either.  I
can count the instances I did look into the Windows frontend during POV-Ray
3.5 development on one hand.  And I never compiled it myself completely
either.  Nor do I use Windows on a regular basis.  Yet by carefully checking
the docs I am able to solve most problems...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Thu, 15 Aug 2002 22:29:08 +0200, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <3d5bfd26@news.povray.org> , "Theo Gottwald *" 
><The### [at] t-onlinede> wrote:
>
>> We should accept here, that Thorsten has put a lot of time and work in the
>> POV-project, while we "nebies" just come here and do get all things "on the
>> silver plate".
>>
>> I can understand that this is sometimes annoying for him.
>
>No, not that ;-)  I only have a problem when the newbies look on the silver
>plate and start complaining about it not being polished well enough :-(
>
>Apart from that, what I really hate is when people just appear and make
>suggestions or complain without even knowing anything about the subject.
>Nothing else gets me aggressive more quickly.
>

Whoa there ... calm down ... there was never any intention to complain
about pov-ray ... hell, I think it's the best bit of free software
I've ever seen - I've been tinkering with it ever since 1992 (still a
newbie mind you). I'm a c++ developer myself and would love to be able
to contribute some code\patch back to the pov community, such is my
admiration of what the team has done over the years.

what you take to be my complaining is actually the result of my being
an over-enthusiastic fan. I guess you're the kind of person who tends
to think the worst of people, eh? <chuckle>

Okay?

Have I reassured you that my posts weren't meant to be negative?

Shall we shake hands then? Maybe I'll render an open hand and send it
to p.b.i - you could render the other one and post it back <grin>

Shall I stop this inane rambling as it's just getting silly now? (I'm
also quite tired now ... off to sleep ... guten nacht)

Cheers,

Scott

PS I'm still curious as to a post ABX sent in this thread when he said
that    pvengine "abx test.ini"   worked perfectly. I'm going to have
nightmares about this now!

Post a reply to this message

"Scott Moore" <sdm### [at] zoomcouk> schrieb im Newsbeitrag
news:djfoluco30t6hmg5i1chlai4da27gn93vl@4ax.com...
> On Thu, 15 Aug 2002 22:29:08 +0200, "Thorsten Froehlich"
> <tho### [at] trfde> wrote:
>
> >In article <3d5bfd26@news.povray.org> , "Theo Gottwald *"
> ><The### [at] t-onlinede> wrote:
> >
> >> We should accept here, that Thorsten has put a lot of time and work in
the
> >> POV-project, while we "nebies" just come here and do get all things "on
the
> >> silver plate".
> >>
> >> I can understand that this is sometimes annoying for him.
> >
> >No, not that ;-)  I only have a problem when the newbies look on the
silver
> >plate and start complaining about it not being polished well enough :-(
> >
> >Apart from that, what I really hate is when people just appear and make
> >suggestions or complain without even knowing anything about the subject.
> >Nothing else gets me aggressive more quickly.
> >
>
> Whoa there ... calm down ... there was never any intention to complain

It isjust a general statement not targetting anybody.

> Have I reassured you that my posts weren't meant to be negative?

I was not thinking about your posts.  It was really just a general
statement.

    Thorsten

Post a reply to this message