 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
New bug:
1. Demo scenes in scenes\camera\ will not parse due to B10 camera {}
keyword ordering requirements.
Previously reported, not on official bug list:
1. Right-click -> 'open file' on any include directive causes Pov to
crash.
2. Pov crashes if the user accidentally loads a TIFF file with either the
PNG or JPEG loaders.
3. The inside_vector keyword is highlighted in the editor and accepted by
the parser even though Pov 3.5 doesn't appear implement any feature
which uses the inside_vector keyword.
4. Maximizing the render window during a trace will regularly leave a
one-line artifact. Screencaps available upon request.
Previously reported, on official bug list, but with new information:
1. The switch to the latest version of LibTIFF has not corrected TIFF
reading problems. Indeed, TIFF reading is even less stable under B10
than under B9. Specific test results with various TIFF subformats
available opon request.
2. Double clicking on the title bar to maximize Pov will only produce
the 'cannot select' dialog if the position of the un-maximized title
bar was below that of the lowest portion of the grey area (i.e. not
the message window) of the maximized Pov window.
Bugs reported by others which I have been able to confirm:
1. <llj84uk2findr74u9jpge6dlteqf19c70o@4ax.com>
CPU time used not reported in stream when render completes
normally.
2. <3c44497e$1@news.povray.org>
File -> Save As won't work if the destination filename is the
same as the original filename.
Win2K, C400, 384MB.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 1. Right-click -> 'open file' on any include directive causes Pov to
> crash.
I don't recall seeing this report. And it certainly doesn't crash here. Can
anyone else confirm this ?
> 3. The inside_vector keyword is highlighted in the editor and accepted by
> the parser even though Pov 3.5 doesn't appear implement any feature
> which uses the inside_vector keyword.
This means the keyword is recognized by the parser. It will have to be removed
from the parser before the highlighting will go away.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 16 Jan 2002 16:00:37 +1100, Chris Cason wrote:
>> 3. The inside_vector keyword is highlighted in the editor and accepted by
>> the parser even though Pov 3.5 doesn't appear implement any feature
>> which uses the inside_vector keyword.
>
> This means the keyword is recognized by the parser. It will have to be removed
> from the parser before the highlighting will go away.
It is indeed. I looked at this when it was first reported and not only is
it recognized by the parser (in the sense that it is in tokenize.cpp) but
it is also *used* by the parser, for mesh objects. The code that uses that
value has been commented out - probably by Nathan - but is still there. The
code to parse it should probably also be commented out.
--
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Chris Cason" <newsadmin-despam-@povray-no-spam.org> wrote in
news:3c45093e@news.povray.org:
>> 1. Right-click -> 'open file' on any include directive causes Pov to
>> crash.
> And it certainly doesn't crash here. Can anyone else confirm this ?
I suspect this will be as difficult to confirm as my prior reports that the
context menu open command doesn't work reliably. Judging from the last
thread on this topic[1], this problem is likely related my particular
povray.ini setup and likely isn't duplicable in stock installs.
Working on this premise, I just hacked up my povray.ini and found the
specific problem: the editor can't cope with library_path keywords that
point to network names. The following library_path will lock up the
editor:
Library_Path=\\celeron400\d\CG\userinclude
but this one won't:
Library_Path=d:\CG\userinclude
In the same test run I also determined that the editor can't find include
files contained in library paths which are specified without a fully-
qualified path. The editor does not appear to check library paths relative
to either the Pov installation directory or the location of the scene file
loaded into the editor. Personally, I'm inclined to call this a quirk in
need of documentation rather than a bug.
[1] Please refer to http://news.povray.org/povray.beta-test/20771/,
specifically <3c20bc6a@news.povray.org>, where you say that there was some
kind of bug in the editor, and <Xns### [at] 204 213191226>,
where I say that your bug fix crashes Pov on my systems.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> In the same test run I also determined that the editor can't find include
> files contained in library paths which are specified without a fully-
> qualified path. The editor does not appear to check library paths relative
> to either the Pov installation directory or the location of the scene file
> loaded into the editor. Personally, I'm inclined to call this a quirk in
> need of documentation rather than a bug.
Does this still happen ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Chris Cason" <newsadmin-despam-@povray-no-spam.org> wrote in
news:3c46171d@news.povray.org:
>> In the same test run I also determined that the editor can't find
>> include files contained in library paths which are specified without a
>> fully- qualified path.
> Does this still happen ?
'same test run' == diagnosing broken network names == only a few hours ago.
It should still happen unless Pov has evolved/updated/morphed itself while
I wasn't looking. ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Coridon Henshaw" <che### [at] sympaticoca> wrote in message
news:Xns### [at] 204213191226...
> 'same test run' == diagnosing broken network names == only a few hours ago.
> It should still happen unless Pov has evolved/updated/morphed itself while
> I wasn't looking. ;-)
I thought you had reported this in the past (and as I recalled I'd done
something about it. What, I can't remember). So maybe I thought you were
referring to the old report.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Chris Cason" <newsadmin-despam-@povray-no-spam.org> wrote in
news:3c464f61@news.povray.org:
> I thought you had reported this in the past (and as I recalled I'd done
> something about it. What, I can't remember). So maybe I thought you
> were referring to the old report.
I admit I may have been unclear. Allow me to recap:
bug #1: Context->open didn't work for files outside of the standard include
directory. Reported during beta 8. You implemented a fix for this
problem in beta 9.
bug #2: The beta 9 fix for bug #1 caused Pov to crash. I reported this
when beta 9 was released, then rereported (as it was not on the
official bug list) it when beta 10 was released.
In response to your request for confirmation for my second
report, I conducted further tests. These tests revealed that the
crashes were caused because some of my library_path entries are
network paths--something which the editor can't cope with.
bug #3: While I was conducting tests to isolate bug #2, I discovered an
unrelated glitch in that that include files specified in relative
library_paths won't be found by the context->open command.
I hope this is clear now.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
