I've found a bug in the beta 8 Windows GUI.  The 'open' option on the 
context menu won't open files which are specified with a path, nor will it 
traverse the library_path to find files in include directories other than 
the one created by the Pov installation.

To test for the first portion of this bug, create an inc file and #include 
it with its fully-qualified name (e.g. "C:\temp\whatever.inc") in a pov 
scene.  Right click on the filename portion of the #include directive and 
pick the 'open' option from the context menu.

To test for the second portion of this bug, add a directory to Pov's 
library paths, place an include file there, #include the file, and attempt 
to use the context menu's open option.

In testing, beta 8's behavior was identical on both Win ME and Win2K.

Post a reply to this message

In article <Xns### [at] 204213191226> , 
che### [at] sympaticoca (Coridon Henshaw) wrote:

> To test for the first portion of this bug, create an inc file and #include
> it with its fully-qualified name (e.g. "C:\temp\whatever.inc") in a pov
> scene.  Right click on the filename portion of the #include directive and
> pick the 'open' option from the context menu.

Such file specifications are not supported and not documented to work (they
are only allowed for your convenience) and thus this part of your report is
not a bug.

The proper solution is to add a matching library_path "C:\temp\".  Of course
this will not fix the other problem (if it is there, I can't test it...!).

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in
news:3c1ea704$1@news.povray.org: 

> The proper solution is to add a matching library_path "C:\temp\".

Uhh, I just reported that the open function won't honor library_paths which 
point to anywhere other than the default include directory.  As far as I 
can tell there is no workaround for either of the two bugs.

Post a reply to this message

Coridon is right in that it doesn't find any files other some subfolders of
POV-Ray.  Can't even get the main folder to be seen by adding a
Library_Path=C:\Program Files\POV-Ray for Windows v3.5

If the file is in the include subfolder all is fine.

Looking at the POV-Win Help I see it might be possible to use any path:

1.10.11.3.3 Open "filename"

Whenever you open the context menu, the editor first looks underneath the
edit caret to see if there is a line that looks like a POV-Ray scene file
'#include' directive. If one is found, the name of the specified file is
placed into the menu in place of "filename". If one is not found, then it
may show "Copy ... to Command-Line" (see below).
If you then select this command, the editor will attempt to find and open
the file in a new edit window. The standard include paths (as defined in
PVENGINE.INI) will be searched if the file is not found relative to the
current directory.



"standard" implies otherwise, such that the following is the part "defined
in pvengine.ini":

[Permitted Input Paths]
1=%INSTALLDIR%
2=C:\WINDOWS\Fonts


I'd think it meant to say povray.ini where the Library_Path= lines are
normally located instead.  Other than that I don't see a place designating
it there.  Could someone please demystify this for us?

--
text{ttf"arial","bob h",.1,0pigment{rgb 9}translate<-1,-.2,3>}


"Coridon Henshaw" <che### [at] sympaticoca> wrote in message
news:Xns### [at] 204213191226...
> "Thorsten Froehlich" <tho### [at] trfde> wrote in
> news:3c1ea704$1@news.povray.org:
>
> > The proper solution is to add a matching library_path "C:\temp\".
>
> Uhh, I just reported that the open function won't honor library_paths
which
> point to anywhere other than the default include directory.  As far as I
> can tell there is no workaround for either of the two bugs.

Post a reply to this message

Wasn't it Coridon Henshaw who wrote:


>To test for the second portion of this bug, add a directory to Pov's 
>library paths, place an include file there, #include the file, and attempt 
>to use the context menu's open option.


The open works perfectly on my machine:-

POV 3.5b8, Win 98se, Celeron II 850, 128 Mb

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

In article <Xns### [at] 204213191226> , 
che### [at] sympaticoca (Coridon Henshaw) wrote:

>> The proper solution is to add a matching library_path "C:\temp\".
>
> Uhh, I just reported that the open function won't honor library_paths which
> point to anywhere other than the default include directory.  As far as I
> can tell there is no workaround for either of the two bugs.

You did not read my message - maybe you should...


    Thorsten

Post a reply to this message

In article <3c1f01ab@news.povray.org> , "bob h" <omn### [at] charternet> 
wrote:

> "Coridon Henshaw" <che### [at] sympaticoca> wrote in message
> news:Xns### [at] 204213191226...
>> "Thorsten Froehlich" <tho### [at] trfde> wrote in
>> news:3c1ea704$1@news.povray.org:
>>
>> > The proper solution is to add a matching library_path "C:\temp\".
>>
>> Uhh, I just reported that the open function won't honor library_paths
> which
>> point to anywhere other than the default include directory.  As far as I
>> can tell there is no workaround for either of the two bugs.

> Coridon is right in that it doesn't find any files other some subfolders of
> POV-Ray.  Can't even get the main folder to be seen by adding a
> Library_Path=C:\Program Files\POV-Ray for Windows v3.5

If either of you had actually read my message (and the part I quoted of the
original message) and paid any attention to the last sentence you would know
that I never said anything about *second* bug he reported other than that I
can't test it (because Macs don't have Windows installed by default ;-)

I am talking about the *first* bug he reported, which is not a bug.


    Thorsten

Post a reply to this message

On Tue, 18 Dec 2001 11:45:14 +0100, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> (Macs don't have Windows installed by default ;-)

Fixed in next beta ;-)

ABX

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3c1f1e3c@news.povray.org...
>
> If either of you had actually read my message (and the part I quoted of
the
> original message) and paid any attention to the last sentence you would
know
> that I never said anything about *second* bug he reported other than that
I
> can't test it (because Macs don't have Windows installed by default ;-)
>
> I am talking about the *first* bug he reported, which is not a bug.

I see, sorry if I was ignoring that but I was trying to understand the lack
of external file paths for that feature.  I had thought I could open
anything from anywhere before if it had a Library_Path to it so that's why I
suspected something had changed too.

So it comes down to the fact that only certain paths to files specified by
the POV-Ray installation and which are "standard" can be accessed (file
restrictions used or not).  What I'm unsure of is which ones those are, I'd
guess the include subfolder is pretty obvious, Coridon seems to have checked
other places.  Easy enough to find out myself which others are accessible as
well, if they actually can be.

Still, it might be good to document which ones are used (only the include
and current folder?).  If they were not mentioned specifically due to
differing directory layouts of various system platforms I can understand
that being generalized.
--
text{ttf"arial","bob h",.1,0pigment{rgb 9}translate<-1,-.2,3>}

Post a reply to this message

> context menu won't open files which are specified with a path, nor will it

It's not specified to be able to do this.

> traverse the library_path to find files in include directories other than
> the one created by the Pov installation.

I don't find that to be the case, myself. I tested this on paths listed in
povray.ini and it worked. It is possible that it could fail if the INI file
was not formatted the way that the editor expects. Could you post your INI
file here please ?

-- Chris

Post a reply to this message