"Kyle" <no### [at] spamok> schreef in bericht news:4947ae46$1@news.povray.org...
>
> I just installed version 3.6.1c, and the result is the same as in version 
> 3.6.1a, the text shows up right after the "Peak memory used" message.
>
> Just to reiterate, this is not the case in version 3.7, beta 29.

Ah! ok! I just have been blind to the "Peak memory used" note from your 
post. Obviously I have been thinking of something else  :-)

The point is that I use the #debug statement quite a lot in my scenes to 
check the parsing procedure or the output of some parameters during testing. 
As such, I need the message to be written right away, and I had not noticed 
the writing of it at thre end of the render. Sorry for the confusion.

Thomas

Post a reply to this message

Thomas de Groot wrote:
> The point is that I use the #debug statement quite a lot in my scenes to
> check the parsing procedure or the output of some parameters during
> testing. As such, I need the message to be written right away, and I had
> not noticed the writing of it at thre end of the render. Sorry for the
> confusion.

Just make sure you print a newline at the end.

Post a reply to this message

It should be easy enough for POV to output a final newline at the end of
all messages just to clean up things like this.

...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

Chambers wrote:
> It should be easy enough for POV to output a final newline at the end of
> all messages just to clean up things like this.

Except that you frequently do not want automatic newlines: They prevent 
assembly of longer outputs using multiple debug statements.

	Thorsten

Post a reply to this message

"Nicolas Alvarez" <nic### [at] gmailcom> schreef in bericht 
news:494826b5@news.povray.org...
> Thomas de Groot wrote:
>> The point is that I use the #debug statement quite a lot in my scenes to
>> check the parsing procedure or the output of some parameters during
>> testing. As such, I need the message to be written right away, and I had
>> not noticed the writing of it at thre end of the render. Sorry for the
>> confusion.
>
> Just make sure you print a newline at the end.

Yes, that is exactly what I found out. I came across the problem when I 
wanted to show a message about the start and then the end of a particular 
parsing block, and both written on the same line. But both messages only 
appeared together at the end of the block.

Thomas

Post a reply to this message

I'd suggest simply outputting whatever remains in the #debug message 
buffer upon completion of the scene.  Doing so would match the 
functionality that's in version 3.6.

Post a reply to this message

Kyle wrote:
> I'd suggest simply outputting whatever remains in the #debug message 
> buffer upon completion of the scene.  Doing so would match the 
> functionality that's in version 3.6.

That is already what 3.7 is supposed to do. I was not making the point that 
the 3.7 behavior is intentional, just that a change to always output a 
newline automatically is not desirable.

	Thorsten

Post a reply to this message

> -----Original Message-----
> From: Thorsten Froehlich [mailto:tho### [at] trfde]
> Chambers wrote:
> > It should be easy enough for POV to output a final newline at the
end
> of
> > all messages just to clean up things like this.
> 
> Except that you frequently do not want automatic newlines: They
prevent
> assembly of longer outputs using multiple debug statements.

Read my message again:

"a final newline at the end of all messages"

If it makes it any clearer, you can say "a newline after all output
streams have been printed."  Or, to put it another way, after parsing
you flush the output stream buffers and then print a newline.

...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

> Or, to put it another way, after parsing
> you flush the output stream buffers and then print a newline.

	Yes, in case this is not yet the intended behavior in 3.7, I'd support
the idea that the debug buffer be forcefully flushed before the render starts
and not only at the end of the povray run.

	- NC

Post a reply to this message

Kyle wrote:
> I'd suggest simply outputting whatever remains in the #debug message 
> buffer upon completion of the scene.  Doing so would match the 
> functionality that's in version 3.6.

Anyone have time to contribute a patch to do this?

-- Chris

Post a reply to this message