"Chris Cason" <newsadmin-despam-@povray-no-spam.org> wrote in
news:3c200e45@news.povray.org: 

>> 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.

That may be so, but it does seem inconsistant that the editor won't find 
files referenced by path even though a) the renderer will and b) the editor 
will find files included by a path when the renderer chokes on a parsing 
error.  Frankly, I'm at a loss to understand why this behavior could be 
considered desirable in anything but a Microsoft product.
 
> Could you post your INI file here please ?

Povray.ini on my WinME box:

Display=On
Verbose=On
Display_Gamma=2.2
Bounding_Threshold=3
Render_Console=off
Buffer_Size=16
+B
+fn
Output_File_Name=c:\povImages\
Library_Path=\\celeron400\ddrive\CG\userinclude
Library_Path=\\celeron400\ddrive\CG\userinclude\old
Library_Path=\\celeron400\ddrive\CG\userinclude\galaxy
Library_Path=\\celeron400\ddrive\CG\userinclude\lensflare
Library_Path=\\celeron400\ddrive\CG\userinclude\plates
Library_Path=\\celeron400\ddrive\CG\userinclude\pyramid
Library_Path=\\celeron400\ddrive\CG\userinclude\city
Library_Path=\\celeron400\ddrive\CG\maps
Library_Path=\\celeron400\ddrive\CG\fleet\include
Library_Path=\\celeron400\ddrive\CG\scenes\background
Library_Path=C:\Program Files\POV-Ray for Windows v3.5\INCLUDE
Library_Path=C:\WINDOWS\Fonts

Povray.ini on my Win2K box:

;                     PERSISTENCE OF VISION RAY TRACER
;
;                           POV-Ray VERSION 3.5
;
;                         SAMPLE POVRAY.INI FILE
;
;  The general form of the options is "Variable=value".  Everything 
;  between the equals sign and the end of the line is considered part 
;  of the value.  The spacing and layout is free-form but only one option 
;  per line is allowed.  Variables and values are not case-sensitive.  
;
;  Note: characters after a semi-colon are treated as a comment
;
;  Traditional POV-Ray switches beginning with + or - are also allowed
;  and they may be given with more than one switch per line.  
;
;  These options have been put in this file because they will help
;  you get up and running quickly.  This file assumes you have installed
;  the program in the C:\POVRAY3 drive and directory.  If you have
;  installed the program on a different drive or directory you must edit
;  the appropriate lines below.  See the general documentation for full
;  instructions on how to use INI options.
;
;  Add your own options at the bottom and/or edit these to suit.
;
;
; Width of image in pixels.  Accepts integer values.
;
Width = 320
;
;
; Height of image in pixels.  Accepts integer values.
;
Height = 240
;
; Sets minimum number of objects before auto bounding kicks in.
;
Bounding_Threshold = 3
;
;
; Turn display on
Display=On
;
; Turn verbose mode on
Verbose=On
;
;
; Specify path to search for any files not found in current
; directory.  Up to 10 such paths may be specified.
; These were added by the install process with your installation
; drive and directory already patched in.
;
Library_Path=D:\Program Files\POV-Ray for Windows v3.5\INCLUDE
Library_Path=C:\WINNT\Fonts

Output_File_Name=d:\cg\images\

Width=320
Height=240
Display_Gamma=2.2
Bounding_Threshold=3
Test_Abort=on
Test_Abort_Count=100
Verbose=on
Render_Console=off
Buffer_Size=16
+B
+fn
Output_File_Name=d:\CG\Images\
Library_Path=d:\CG\INCLUDE
Library_Path=d:\CG\userinclude
Library_Path=d:\CG\userinclude\old
Library_Path=d:\CG\userinclude\galaxy
Library_Path=d:\CG\userinclude\lensflare
Library_Path=d:\CG\userinclude\plates
Library_Path=d:\CG\userinclude\pyramid
Library_Path=d:\CG\userinclude\city
Library_Path=d:\CG\maps
Library_Path=d:\CG\fleet\include
Library_Path=d:\CG\scenes\background
;
; Note: include_header ignored by beta 8.  Reported.
;
Include_Header=d:\cg\userinclude\beta8fix.inc

Post a reply to this message

To put a twist on this I now get the include file opened okay from c:\temp
folder.  Don't think I even shut down the computer, only Hibernated it since
before.

BTW, I have 23 library paths while the Scene Help states only 20 can be used
(section 5.2.3.4) and I thought the limit had been increased in v3.1.  If I
use 26 it causes an error so the limit must actually be 25 instead.
--
text{ttf"timrom""bob h"0,0pigment{rgb 7}translate 7*z}

Post a reply to this message

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

> That may be so, but it does seem inconsistant that the editor won't find
> files referenced by path even though a) the renderer will and b) the editor
> will find files included by a path when the renderer chokes on a parsing
> error.

Path specifications in POV files are not guaranteed to work in POV-Ray.  To
the contrary, they are discouraged!  As I said before, anything that does
work is more or less not intentionally *disabled* for your convenience
(because the used system functions happen to just handle the file
specification), but adding code would be to explicitly enable path
specifications in POV-Ray, which will not happen.

NOTE: Future versions may not work path specifications in scene files at
all.  You use them at your own risk.

Be happy with it or feel free to use another program.

    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

"bob h" <omn### [at] charternet> wrote in message
news:3c205b65@news.povray.org...
>
> BTW, I have 23 library paths while the Scene Help states only 20 can be
used
> (section 5.2.3.4) and I thought the limit had been increased in v3.1.  If
I
> use 26 it causes an error so the limit must actually be 25 instead.

I suspect there's some jostled order going on because using 25 paths worked
then didn't, only if 24.  Then that failed and back to 23.  My guess is that
the order of them in povray.ini isn't followed exactly and can skip to the
last one ignoring others exist if the file is found.  Had long success with
22 or 23 though.  So I presume 20 as the true limit is still valid.

Post a reply to this message

> That may be so, but it does seem inconsistant that the editor won't find
> files referenced by path even though a) the renderer will and b) the editor
> will find files included by a path when the renderer chokes on a parsing
> error.  Frankly, I'm at a loss to understand why this behavior could be
> considered desirable in anything but a Microsoft product.

What it comes down to is the amount of code and time I am willing to devote
to adding much smarter library path stuff to the editor (since it can't use
the code in povray itself). Recall I am a volunteer and Microsoft is a $500
billion dollar company (and even they don't always get it right).

-- Chris

Post a reply to this message

> error.  Frankly, I'm at a loss to understand why this behavior could be
> considered desirable in anything but a Microsoft product.

a statement of fact was made, that being that it was not supported. where
was it said to be 'desirable' ?

in any event, the reason it wasn't working was due to a bug, which is now
fixed. even though hard-coding these paths in scene files is non-portable,
the editor will allow it.

Post a reply to this message

"Chris Cason" <newsadmin-despam-@povray-no-spam.org> wrote in
news:3c20b2d1@news.povray.org: 

>> Frankly, I'm at a loss to understand why this behavior could be
>> considered desirable in anything but a Microsoft product. 
 
> Recall I am a volunteer and
> Microsoft is a $500 billion dollar company (and even they don't always
> get it right). 

Uhh, I'm slamming *Microsoft* for their design practicies...


Speaking of the context menu's open function, I regret to tell you that 
this command causes beta 9 pvengine to cease responding to messages.  It 
doesn't trap, but won't react to anything other than a hard kill from ctrl-
alt-del. This will occur sporadically when attempting to load an include 
which is specified by absolute path, but it will always occur when 
attempting to load an include which is in a library path.

Tested on my WinME P3-866; my povray.ini is unchanged from what I posted 
earlier.

Post a reply to this message

Wasn't it Coridon Henshaw who wrote:

>Speaking of the context menu's open function, I regret to tell you that 
>this command causes beta 9 pvengine to cease responding to messages.  It 
>doesn't trap, but won't react to anything other than a hard kill from ctrl-
>alt-del. This will occur sporadically when attempting to load an include 
>which is specified by absolute path, but it will always occur when 
>attempting to load an include which is in a library path.
>
>Tested on my WinME P3-866; my povray.ini is unchanged from what I posted 
>earlier.

That's odd. On my machine it will quite happily open include files that
are in the normal library path and in extra library paths that I have
added to povray.ini.

I have had one situation where beta 9 povwin stopped responding to me,
but all I was doing at the time was starting it up by double-clicking on
a pov file. Killing it with ctrl-alt-del and then restarting it didn't
cure the problem. Each time it started it started minimised; clicking on
the task bar opened the main window; clicking anywhere on the main
window caused the window to change from active window colours to
inactive window colours.

I ended up having to reinstall to get it to work again.

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

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

> I ended up having to reinstall to get it to work again.

Did you try rebooting ? Or checking the task list in case another
instance was hiding away somewhere ?

Post a reply to this message