 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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] pacbell net> 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
|
|
| |
| |
|
|
From: Theo Gottwald *
Subject: Re: NO whitespaces allowed in Path to ini ?
Date: 15 Aug 2002 00:42:16
Message: <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 ...)
--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
|
|
| |
| |
|
|
From: Josh Seagoe
Subject: Re: NO whitespaces allowed in Path to ini ?
Date: 15 Aug 2002 01:37:58
Message: <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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"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
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: NO whitespaces allowed in Path to ini ?
Date: 15 Aug 2002 03:00:54
Message: <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
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: NO whitespaces allowed in Path to ini ?
Date: 15 Aug 2002 03:02:14
Message: <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
|
|
| |
| |
|
|
|
|
| |
