I was wary of posting this to p.programming as although it is to do with 
POV-Ray the program it's something that may already exist that I've missed.

I have two files open File1 and File2 I render them both in that order, I 
switch to edit File1 and hit show and of course the File2 image appears, 
is there any way that POV-Ray can retain a memory that File1 has been 
rendered and display *that* image as opposed to the last one. I wouldn't 
expect it to last beyond the session, but a temporary memory would be nice 
IMHO instead of having to open an external imager to see the image or 
re-render.

I'm well prepared to be slapped down on this if the implementation is 
horrendous or if it's some switch I've missed, but it was just a thought.

--
Phil

-- 
All thoughts and comments are my own unless otherwise stated and I am 
happy to be proven wrong.

Post a reply to this message

Program ended abnormally on 12/03/2004 08:00, Due to a catastrophic Phil Cook error:

> I was wary of posting this to p.programming as although it is to do with 
> POV-Ray the program it's something that may already exist that I've missed.

p.programming is for discussing the actual source code.  Feature requests should 
go here.

> 
> I have two files open File1 and File2 I render them both in that order, 
> I switch to edit File1 and hit show and of course the File2 image 
> appears, is there any way that POV-Ray can retain a memory that File1 
> has been rendered and display *that* image as opposed to the last one. I 
> wouldn't expect it to last beyond the session, but a temporary memory 
> would be nice IMHO instead of having to open an external imager to see 
> the image or re-render.
> 
> I'm well prepared to be slapped down on this if the implementation is 
> horrendous or if it's some switch I've missed, but it was just a thought.
> 

No it isn't a switch you've missed.  The "show" button will only display the 
last image you've rendered.

I agree with you that having a more versatile "show" button (or having a menu 
item that allowed to display recently rendered images) could be a nice addition 
that wouldn't be too hard too implement, but having an image viewing app loaded 
on your pc alongside POV isn't too hard for the user to implement, either. ;-)


-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   videotron.ca  */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message

On Fri, 12 Mar 2004 13:00:26 -0000, Phil Cook
<phi### [at] nospamdeckingdealscouk> wrote:

>I'm well prepared to be slapped down on this if the implementation is 
>horrendous or if it's some switch I've missed, but it was just a thought.

Start two instances of POV-Ray and edit one file in each of them. You
may have to uncheck the "Keep single instance" option if it is
checked.


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

On Fri, 12 Mar 2004 08:00:02 -0500, Francois Labreque 
<fla### [at] videotronca> wrote:

> Program ended abnormally on 12/03/2004 08:00, Due to a catastrophic Phil 
> Cook error:
>
>> I was wary of posting this to p.programming as although it is to do 
>> with POV-Ray the program it's something that may already exist that 
>> I've missed.
>
> p.programming is for discussing the actual source code.  Feature 
> requests should go here.

Good I was worried I'd offend someone.

>> I have two files open File1 and File2 I render them both in that order, 
>> I switch to edit File1 and hit show and of course the File2 image 
>> appears, is there any way that POV-Ray can retain a memory that File1 
>> has been rendered and display *that* image as opposed to the last one. 
>> I wouldn't expect it to last beyond the session, but a temporary memory 
>> would be nice IMHO instead of having to open an external imager to see 
>> the image or re-render.
>>
>> I'm well prepared to be slapped down on this if the implementation is 
>> horrendous or if it's some switch I've missed, but it was just a 
>> thought.
>>
>
> No it isn't a switch you've missed.  The "show" button will only display 
> the last image you've rendered.

Oh goodie, not me being dense as usual then,

> I agree with you that having a more versatile "show" button (or having a 
> menu item that allowed to display recently rendered images) could be a 
> nice addition that wouldn't be too hard too implement,

It's just something I thought of as I wanted to show someone a render I'd 
just done, but had one in-between which meant opening up an extra program.

> but having an image viewing app loaded on your pc alongside POV isn't 
> too hard for the user to implement, either. ;-)

Umm, but that's a little similiar to the argument being held over 
JPEG2000, why should someone have to open an external viewer when the 
program you're using supports inline viewing. IMO it's not a difficulty 
just err... inelegant :)

--
Phil

-- 
All thoughts and comments are my own unless otherwise stated and I am 
happy to be proven wrong.

Post a reply to this message

On Fri, 12 Mar 2004 16:06:12 +0200, Peter Popov <pet### [at] vipbg> wrote:

> On Fri, 12 Mar 2004 13:00:26 -0000, Phil Cook
> <phi### [at] nospamdeckingdealscouk> wrote:
>
>> I'm well prepared to be slapped down on this if the implementation is
>> horrendous or if it's some switch I've missed, but it was just a 
>> thought.
>
> Start two instances of POV-Ray and edit one file in each of them. You
> may have to uncheck the "Keep single instance" option if it is
> checked.

Ah which would explain why I couldn't get two working at the same time, 
admittedly I was a little concerned over opening multiple instances, I 
should have remembered how robust POV-ray is :) Oh good that allows me to 
render multiple images simultaneously, <sigh> still seems a little 
inelegant to me having a program that can hold multiple files and then 
opening a separate instance of it, oh well at least I know a way round it 
now, thank you.

--
Phil

-- 
All thoughts and comments are my own unless otherwise stated and I am 
happy to be proven wrong.

Post a reply to this message

In article <opr4q2e0eqp4ukzs@news.povray.org> , Phil Cook 
<phi### [at] nospamdeckingdealscouk>  wrote:

> I was wary of posting this to p.programming as although it is to do with
> POV-Ray the program it's something that may already exist that I've missed.
>
> I have two files open File1 and File2 I render them both in that order, I
> switch to edit File1 and hit show and of course the File2 image appears,
> is there any way that POV-Ray can retain a memory that File1 has been
> rendered and display *that* image as opposed to the last one. I wouldn't
> expect it to last beyond the session, but a temporary memory would be nice
> IMHO instead of having to open an external imager to see the image or
> re-render.
>
> I'm well prepared to be slapped down on this if the implementation is
> horrendous or if it's some switch I've missed, but it was just a thought.

The Mac version displays as many images as you want, so which version are
you talking about?  Windows or Linux or another one?

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Fri, 12 Mar 2004 17:06:21 +0100, Thorsten Froehlich <tho### [at] trfde> 
wrote:

> In article <opr4q2e0eqp4ukzs@news.povray.org> , Phil Cook
> <phi### [at] nospamdeckingdealscouk>  wrote:
>
<snip>
>> I have two files open File1 and File2 I render them both in that order, 
>> I
>> switch to edit File1 and hit show and of course the File2 image appears,
>> is there any way that POV-Ray can retain a memory that File1 has been
>> rendered and display *that* image as opposed to the last one. I wouldn't
>> expect it to last beyond the session, but a temporary memory would be 
>> nice
>> IMHO instead of having to open an external imager to see the image or
>> re-render.
>>
>> I'm well prepared to be slapped down on this if the implementation is
>> horrendous or if it's some switch I've missed, but it was just a 
>> thought.
>
> The Mac version displays as many images as you want, so which version are
> you talking about?  Windows or Linux or another one?

Oops sorry my bad, Windows, v3.5. 'Show' only displays the last rendered 
file regardless of which file you're currently editing, multiple instances 
of POV-ray show the last render as per each instance.

--
Phil

-- 
All thoughts and comments are my own unless otherwise stated and I am 
happy to be proven wrong.

Post a reply to this message

"Phil Cook" <phi### [at] nospamdeckingdealscouk> wrote in message
news:opr4rbw8byp4ukzs@news.povray.org...
> Oops sorry my bad, Windows, v3.5. 'Show' only displays the last rendered
> file regardless of which file you're currently editing, multiple instances
> of POV-ray show the last render as per each instance.

To be more specific, 'show' doesn't actually display a rendered 'file'; it
re-displays the pixel data that is still stored in memory after the display
window was closed.

It does not read a file from disk, as you seem to think. POV-Ray is not an
image viewer, nor is it meant to be (as there are other programs that do
that quite well).

-- Chris

Post a reply to this message

On Sat, 13 Mar 2004 21:55:01 +1100, Chris Cason 
<new### [at] deletethispovrayorg> wrote:

>
> "Phil Cook" <phi### [at] nospamdeckingdealscouk> wrote in message 
> news:opr4rbw8byp4ukzs@news.povray.org...
>> Oops sorry my bad, Windows, v3.5. 'Show' only displays the last rendered
>> file regardless of which file you're currently editing, multiple 
>> instances
>> of POV-ray show the last render as per each instance.
>
> To be more specific, 'show' doesn't actually display a rendered 'file'; 
> it
> re-displays the pixel data that is still stored in memory after the 
> display
> window was closed.
>
> It does not read a file from disk, as you seem to think. POV-Ray is not 
> an
> image viewer, nor is it meant to be (as there are other programs that do
> that quite well).

Actually I thought that might be the case and was prepared for someone to 
give that as a reason why 'Show' didn't work in that way; but as the 
compression algorithms to output to certain formats are obviously present 
I thought it might be a possibility that the full codecs was implemented 
and that it *may* be made to work in that way and that I had just missed a 
switch somewhere: obviously not.

--
Phil

-- 
All thoughts and comments are my own unless otherwise stated and I am 
happy to be proven wrong.

Post a reply to this message

Reading your post, I'd like to take this moment to say I'd appreciate a
"Show" button that would remember at least the last 3 or 4 images rendered.
The user could set this as an option to the windows executable (on other
platforms ymmv) choosing how far back the memory should go.

As a side note, has there been any attempt to write a GUI for POV that is
cross platform, or do most people who just give in and use emacs? :)

-- 
...Chambers
http://www.geocities.com/bdchambers79

Post a reply to this message