![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Thorsten Froehlich" wrote:
> Ah, finally an interesting suggestion. This sounds
> like something that is possible to do easily and
> still avoids the problem of users taking the output
> as a POV-Ray error message.
>
> What do other people think?
I'm not sure how it will look, but if it means that we'll be able to direct
formatted strings to the error stream, then by all means use it! That's all
I ever asked for.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Rune wrote:
> I'm not sure how it will look, but if it means that we'll be able to direct
> formatted strings to the error stream, then by all means use it! That's all
> I ever asked for.
Let me see if I have this right....
The POV-Team spent a couple of years and went through countless
development versions to come up with a releasable version of
POV-Ray v3.5.
The TAG did alpha testing on no less than 10 alpha versions of
POV-Ray v3.5.
The pre-beta testers had no less than 15 versions to test and
and ask modifications for.
We are now in *public* beta testing at version #6 of what is
supposed to be a *feature locked* version of the program.
And you are still making feature requests?
When will you be satisfied enough to allow the POV-Team to move
on to other things, like v4.0 for example?
This is all rhetorical and no need for you to reply...
--
Ken Tyler
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Let me see if I have this right....
>
> The POV-Team spent a couple of years and went through countless
> development versions to come up with a releasable version of
> POV-Ray v3.5.
>
> The TAG did alpha testing on no less than 10 alpha versions of
> POV-Ray v3.5.
>
> The pre-beta testers had no less than 15 versions to test and
> and ask modifications for.
>
> We are now in *public* beta testing at version #6 of what is
> supposed to be a *feature locked* version of the program.
>
> And you are still making feature requests?
That's what it looks like to me... I mean, a program can only reach a
certain level of perfection before it is "final", and people can move on to
work on the next version... I feel we should have had a final by now... How
many months/years of this do we really need? At this rate, we'll never see
4.0... Of course, I might just be overreacting... Ghaa... I've got to go
study... midterms this week...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Doh! I reread all this thread, and sorry if my post wasn't
perfect.
Note that
> > Right now as you said somewhere earlier,
> > the user can "guess" the behaviour. Doh!
didn't mean I accused you of being happy with the
current situation!
You said
> As the documentation is not clear what happens
> with the output, it is up to the user interpretation.
which I rewrote my (wrong?) way, from memory.
Anyway, I hope ingo is still reading this one,
because the only thing that needs to be changed
is the documentation, it seems.
--
Adrien Beau adr### [at] free fr http://adrien.beau.free.fr/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Ken" wrote:
> Let me see if I have this right....
>
> And you are still making feature requests?
It's not a feature request, it's a bug report.
There's a bug *somewhere* but we can't seem to agree whether it's in the
program or in the documentation.
Anyway, the latest development is that in a reply to Warp Thorsten seem
willing to fix the bug, and he asks for our opinions. And then I reply that
I think it's a great idea. And then you complain about it for some reason.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
#macro verboseFatal(stString)
#warning stString
#error ""
#end
verboseFatal("\n\nA Simple Solution ?\n\n")
// Povingly ,
// Philippe
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> #macro verboseFatal(stString)
> #warning stString
> #error ""
> #end
>
> verboseFatal("\n\nA Simple Solution ?\n\n")
File: C:\Docs\pov\test3.pov Line: 3
#warning stString
#error "" <----ERROR
Parse Error: User error directive hit.
Returned from renderer with error status.
Very helpful... BTW, #debug stString doesn't work either.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> > #macro verboseFatal(stString)
> > #warning stString
> > #error ""
> > #end
> >
> > verboseFatal("\n\nA Simple Solution ?\n\n")
Okay, just noticed the text "A Simple Solution ?", but it was way above the
error message (even above a horizontal rule), and I think most users
wouldn't have noticed it.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Sun, 21 Oct 2001 17:15:21 +0200, Thorsten Froehlich wrote:
>In article <3bd2c73b@news.povray.org> , Warp <war### [at] tag povray org> wrote:
>
>> IMHO there's no need to "camouflage" an #error command to look like a
>> POV-Ray error. Make it as different as you need from internal errors;
>
>Ah, finally an interesting suggestion. This sounds like something that is
>possible to do easily and still avoids the problem of users taking the
>output as a POV-Ray error message.
>
>What do other people think?
I think it's a good idea. I certainly always assumed that #error would
print what I asked it to before aborting; if it has to put little flashy
warning signs around the error, that's okay, but it should definitely do
what it looks like it does.
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
in news:3BD33830.7DF64ED6@free.fr Adrien Beau wrote:
> Anyway, I hope ingo is still reading this one,
He does and waits until it comes to a conclusion: will Thorsten make
the proposed changes, it sounds ggod, and what should be changed
exactly in the doc.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |