> 
> Linux mandrake 8.2, Kde 2.?, run povray from Konsole.
> I don't think of anything else for the moment.
> 
> Fabien
> 
> What system do you have ?
>
Red Hat 7.2, Gnome 1.? and povray started by pyvon.


-- 

_/ __/ __/ John Steinbeck
 \__ \__ \_______________________________________________________________

Post a reply to this message

Does povray deal correctly with spaces in the name of the scenes when 
you start it from a console ?

As far as I am concerned, the problem does not come from Pyvon.


Fabien




> 
>>Linux mandrake 8.2, Kde 2.?, run povray from Konsole.
>>I don't think of anything else for the moment.
>>
>>Fabien
>>
>>What system do you have ?
>>
> 
> Red Hat 7.2, Gnome 1.? and povray started by pyvon.
> 

Post a reply to this message

Fabien HENON wrote:
> Does povray deal correctly with spaces in the name of the scenes when 
> you start it from a console ?
> 
> As far as I am concerned, the problem does not come from Pyvon.
> 
> 
> Fabien

The Windows version has the same problem. I ran pvengine.exe from
a DOS prompt, passing it scene file names with spaces in the name
and I got the same sort of error message. I tried surrounding the
filename in quotes but that didn't solve the problem.

Attempting to run a scene file with one or more spaces in the name
in a Linux console does the same thing.

It's not Pyvon, it's POV-Ray. I still have MegaPOV (xmegapov) on
my system and it also has the same behavior. I don't know if it's
really that big of a deal that POV-Ray doesn't handle filenames
with spaces in it nicely on the commandline.

Maybe just place a note in your readme.txt file and/or on your
web site about this small issue with pov.

-Roz

Post a reply to this message

Fabien HENON wrote:
> Does povray deal correctly with spaces in the name of the scenes when 
> you start it from a console ?
> 
> As far as I am concerned, the problem does not come from Pyvon.
> 
> 
> Fabien

I found a fix for this problem. Instead of passing a space containing
filename on the command line with the +i switch, use Input_File_Name=...

For example, instead of a line like this:

povray +i"test file.pov" +a0.2 +w800 +h600

Use a line like this:

povray Input_File_Name="test file.pov" +a0.2 +w800 +h600


Hope this helps you guys out!

-Roz

Post a reply to this message

> Does povray deal correctly with spaces in the name of the scenes when 
> you start it from a console ?
>
Nope.
It can't parse it.
 
> As far as I am concerned, the problem does not come from Pyvon.
> 
You're right. :)

> Fabien


-- 


 \__ \__ \_______________________________________________________________

Post a reply to this message

In article <3D7### [at] netscapenet> , Roz <Rzl### [at] netscapenet>  
wrote:

> The Windows version has the same problem.

No, it has not.  It was explained in the p.windows some time ago why it does
not work with pvengine.  The problems you see are completely unrelated:

The X display init code preparses the command line and unfortunately does
not handle the arguments correctly.  Compiling POV-Ray without X display
support (probably adding #define X_DISPLAY_MISSING in config.h will be
sufficient) will resolve the problem.

    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

Thorsten Froehlich wrote:
> In article <3D7### [at] netscapenet> , Roz <Rzl### [at] netscapenet>  
> wrote:
> 
> 
>>The Windows version has the same problem.
> 
> 
> No, it has not.  It was explained in the p.windows some time ago why it does
> not work with pvengine.  The problems you see are completely unrelated:

I didn't peek at the p.windows newsgroup. All I did was test it and I get
the same behavior as I do with the Linux version.

When running the following command from a DOS prompt:

pvengine +i"test file.pov"

I get the following error in the Messages window of POV-Ray 3.5 for Windows:

This windows version by Cristopher J. Cason
Possible Command Line Error: File name or path parameter expected for 
switch 'I', found 'test'.
Command Line Error: Problem with command line or INI file.

When running the following command from a DOS prompt:

pvengine +i"testfile.pov"

it works. Maybe the cause of the problem isn't the same but the results
are, i.e. POV-Ray doesn't like filenames with spaces in it using the +i
switch.

> The X display init code preparses the command line and unfortunately does
> not handle the arguments correctly.  Compiling POV-Ray without X display
> support (probably adding #define X_DISPLAY_MISSING in config.h will be
> sufficient) will resolve the problem.

I'll give that a go. To me it's no big deal as there are ways around the
problem anyway like not using filenames with spaces in it or using an
ini file for the scene. Or, as I said in another post, use the
Input_File_Name setting right on the command line.

-Roz

Post a reply to this message

In article <3D7### [at] netscapenet> , Roz <Rzl### [at] netscapenet>  
wrote:

> it works. Maybe the cause of the problem isn't the same but the results
> are, i.e. POV-Ray doesn't like filenames with spaces in it using the +i
> switch.

No, this is incorrect.  You are not passing correct arguments to the Windows
version.  It is not meant to work like a plain commandline version.  in
Windows you have to start it the way I explained in:

Date: Thu, 15 Aug 2002 13:19:24 +0200
From: "Thorsten Froehlich" <tho### [at] trfde>
Newsgroups: povray.windows
Subject: Re: NO whitespaces allowed in Path to ini ?
Message-ID: <3d5b8e3f$1@news.povray.org>
Xref: news.povray.org povray.windows:4737


    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

Thansk, I'll give that a try.

Fabien H

Roz wrote:
> Fabien HENON wrote:
> 
>> Does povray deal correctly with spaces in the name of the scenes when 
>> you start it from a console ?
>>
>> As far as I am concerned, the problem does not come from Pyvon.
>>
>>
>> Fabien
> 
> 
> I found a fix for this problem. Instead of passing a space containing
> filename on the command line with the +i switch, use Input_File_Name=...
> 
> For example, instead of a line like this:
> 
> povray +i"test file.pov" +a0.2 +w800 +h600
> 
> Use a line like this:
> 
> povray Input_File_Name="test file.pov" +a0.2 +w800 +h600
> 
> 
> Hope this helps you guys out!
> 
> -Roz
>

Post a reply to this message

Thorsten Froehlich wrote:
> In article <3D7### [at] netscapenet> , Roz <Rzl### [at] netscapenet>  
> wrote:
> 
> 
>>it works. Maybe the cause of the problem isn't the same but the results
>>are, i.e. POV-Ray doesn't like filenames with spaces in it using the +i
>>switch.
> 
> 
> No, this is incorrect.  You are not passing correct arguments to the Windows
> version.  It is not meant to work like a plain commandline version.  in
> Windows you have to start it the way I explained in:
> 
> Date: Thu, 15 Aug 2002 13:19:24 +0200
> From: "Thorsten Froehlich" <tho### [at] trfde>
> Newsgroups: povray.windows
> Subject: Re: NO whitespaces allowed in Path to ini ?
> Message-ID: <3d5b8e3f$1@news.povray.org>
> Xref: news.povray.org povray.windows:4737

I looked in the p.windows newsgroup after your earlier post and found that
thread. That does describe the same problem. I understand what you're
saying in that for the Windows version, you need to specify /RENDER or
you'll get the error I got ;)

That doesn't help Fabien's problem however because that's a Windows specific
solution. Even recompiling with the config.h change you suggested won't
help him because he's trying to make a program work with existing
installations of POV-Ray. Hopefully, using Input_File_Name instead of +i
will solve this issue for him or at least be a good workaround.

-Roz

Post a reply to this message