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