 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here is another thing I noticed while doing some render-around
(balcony.pov) using -d ...
Having nothing else to watch, this came to my sight:
==== [Rendering...] ========================================================
Rendered 10240 of 1080000 pixels (0%)9%)
If you think it's worth the effort, I think this one should be easy to
fix ;)
--
Thorsten aka ThH
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.02.2016 um 16:09 schrieb ThH:
> Here is another thing I noticed while doing some render-around
> (balcony.pov) using -d ...
>
> Having nothing else to watch, this came to my sight:
>
> ==== [Rendering...]
> ========================================================
> Rendered 10240 of 1080000 pixels (0%)9%)
>
> If you think it's worth the effort, I think this one should be easy to
> fix ;)
Actually, no -- it's not.
Well, it's trivial to add a kludge for it, but a real good clean fix is
an entirely different matter.
Did I ever mention that I hate kludges? ;)
P.S: I really appreciate you rendering all those sample scenes; and as
strange as it may sound, I hope you'll find some more bugs. You know --
some of those I've smuggled into 3.7.1.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.02.2016 um 18:18 schrieb clipka:
> Actually, no -- it's not.
>
> Well, it's trivial to add a kludge for it, but a real good clean fix is
> an entirely different matter.
>
> Did I ever mention that I hate kludges? ;)
So it seems, that - ages ago, Pascal-time so to say - I used a kludge to
make an identical problem disappear in one of my progs...
And I will find out, what a kludge is ;)
> P.S: I really appreciate you rendering all those sample scenes; and as
> strange as it may sound, I hope you'll find some more bugs. You know --
> some of those I've smuggled into 3.7.1.
Thank you clipka. My pleasure :))
Your hope won't be disappointed... Think I found another small one.
This time I think I'm right by calling it small ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ThH <no.spam@address> wrote:
> Am 29.02.2016 um 18:18 schrieb clipka:
>
> > Actually, no -- it's not.
> >
> > Well, it's trivial to add a kludge for it, but a real good clean fix is
> > an entirely different matter.
> >
> > Did I ever mention that I hate kludges? ;)
>
> So it seems, that - ages ago, Pascal-time so to say - I used a kludge to
> make an identical problem disappear in one of my progs...
It is easy to fix if you print spaces over a line up to the whole length minus
one. After all the problem is not that POV prints the wrong data, but rather
that shells act like terminals up to this day, and thus store ever character
where it used to be. And the POV Unix frontend just prints all progress messages
in one line.
To do get the line width cleanly in Unix, you need to use Posix calls, but even
then it is not trivial because as far as Google search results show on the first
few pages, this does not always seem to work properly even in Linux.
The alternative would be to add a linefeed for every change of progress
reporting. This might require keeping a proper state of the progress kind in the
frontend, but all information to do so should be passed to the frontend already.
Thorsten
PS: The kludge would be to print about 10 spaces following any progress message.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.02.2016 um 19:05 schrieb Thorsten Froehlich:
> It is easy to fix if you print spaces over a line up to the whole length minus
> one. After all the problem is not that POV prints the wrong data, but rather
> that shells act like terminals up to this day, and thus store ever character
> where it used to be. And the POV Unix frontend just prints all progress messages
> in one line.
>
> To do get the line width cleanly in Unix, you need to use Posix calls, but even
> then it is not trivial because as far as Google search results show on the first
> few pages, this does not always seem to work properly even in Linux.
>
> The alternative would be to add a linefeed for every change of progress
> reporting. This might require keeping a proper state of the progress kind in the
> frontend, but all information to do so should be passed to the frontend already.
>
> Thorsten
Thank you Thorsten.
The "hack" worked in the old days though.
Lucky me I'm only using POV-Ray's SDL today ;)
> PS: The kludge would be to print about 10 spaces following any progress message.
Source: https://en.wikipedia.org/wiki/Kludge
A kludge ... is a workaround or quick-and-dirty solution that is clumsy,
inelegant, inefficient, difficult to extend and hard to maintain ...
(Ducks) It really worked in the old days ;))
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
:-D
On 29.02.2016 12:18, clipka wrote:
> ... and as strange as it may sound, I hope you'll find some more bugs...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
