This question seems to be too obvious, but I've searched the docs, faqs,
etc. high and low for *any* reference to it at all, and come up with
nothing.

I've been using POVWin 3.0x for a long time now, and only recently
started playing with 3.1e.  It appears that POVWin will no longer parse
the "current working" file in the editor without saving it first.  This
was a very nice feature in 3.0x.  Is this just the way it works now (due
to some major code rewrites or something), or is there a way to change
this?  I can see that it automatically saves it before rendering, but
what if I don't want to commit changes to disk?  (Yeah, I know there's
UNDO, but...)

I also *really* miss the right-mouse-button option "start/stop
rendering".

Looks like I'd better not blow away the 3.02 install yet..........

Post a reply to this message

Ted A wrote:
> 
> I've been using POVWin 3.0x for a long time now, and only recently
> started playing with 3.1e.  It appears that POVWin will no longer parse
> the "current working" file in the editor without saving it first.  This
> was a very nice feature in 3.0x.  Is this just the way it works now (due
> to some major code rewrites or something), or is there a way to change
> this?  I can see that it automatically saves it before rendering, but
> what if I don't want to commit changes to disk? 

   Between the power that blinks out for 1-2 seconds every so often and
the stupid cat that just has to play with the keyboard when I go to the
other room, having a program that saves a file before is a great option,
not even to get into windows crashing. If you don't want to write over
your old file just rename it junk.pov or temp.pov and then rename it
with the proper name when you are ready to save it.

Post a reply to this message

If you do this, bear in mind that there is a bug in save As, it saves BOTH
files(the new and the old) when saving.


Steve wrote:
> 
> Ted A wrote:
> >
> > I've been using POVWin 3.0x for a long time now, and only recently
> > started playing with 3.1e.  It appears that POVWin will no longer parse
> > the "current working" file in the editor without saving it first.  This
> > was a very nice feature in 3.0x.  Is this just the way it works now (due
> > to some major code rewrites or something), or is there a way to change
> > this?  I can see that it automatically saves it before rendering, but
> > what if I don't want to commit changes to disk?
> 
>    Between the power that blinks out for 1-2 seconds every so often and
> the stupid cat that just has to play with the keyboard when I go to the
> other room, having a program that saves a file before is a great option,
> not even to get into windows crashing. If you don't want to write over
> your old file just rename it junk.pov or temp.pov and then rename it
> with the proper name when you are ready to save it.

-- 
//Spider
        [ spi### [at] bahnhofse ]-[ http://www.bahnhof.se/~spider/ ]
What I can do and what I could do, I just don't know anymore
                "Marian"
        By: "Sisters Of Mercy"

Post a reply to this message

I don't appear to have any *.bak files with the same time stamp as the
*.pov here. Probably because I then do Save immediately thereafter.
Guess I've seldom used the Save as...
Good to know about this, thanks for clueing us in on that.


Spider wrote:
> 
> If you do this, bear in mind that there is a bug in save As, it saves BOTH
> files(the new and the old) when saving.
> 
> Steve wrote:
> >
> > Ted A wrote:
> > >
> > > I've been using POVWin 3.0x for a long time now, and only recently
> > > started playing with 3.1e.  It appears that POVWin will no longer parse
> > > the "current working" file in the editor without saving it first.  This
> > > was a very nice feature in 3.0x.  Is this just the way it works now (due
> > > to some major code rewrites or something), or is there a way to change
> > > this?  I can see that it automatically saves it before rendering, but
> > > what if I don't want to commit changes to disk?
> >
> >    Between the power that blinks out for 1-2 seconds every so often and
> > the stupid cat that just has to play with the keyboard when I go to the
> > other room, having a program that saves a file before is a great option,
> > not even to get into windows crashing. If you don't want to write over
> > your old file just rename it junk.pov or temp.pov and then rename it
> > with the proper name when you are ready to save it.
> 
> --
> //Spider
>         [ spi### [at] bahnhofse ]-[ http://www.bahnhof.se/~spider/ ]
> What I can do and what I could do, I just don't know anymore
>                 "Marian"
>         By: "Sisters Of Mercy"

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto:inv### [at] aolcom?Subject=PoV-News

Post a reply to this message

> Spider wrote:
> >
> > If you do this, bear in mind that there is a bug in save As, it saves BOTH
> > files(the new and the old) when saving.

Oh great, that's useful!!!


Bob Hughes wrote:
> 
> I don't appear to have any *.bak files with the same time stamp as the
> *.pov here. Probably because I then do Save immediately thereafter.
> Guess I've seldom used the Save as...
> Good to know about this, thanks for clueing us in on that.

Yeah, thanks Spider.  Sounds like I'll be blowing away 3.1e and going
back to 3.02.  Anyway, my main reason for "upgrading" was to check out
Media, but I'm not real impressed with this either.  Admittedly Halos
are a pain in the butt, but they seem to be a lot faster (to me
anyway).  Maybe Media will be more optimized in the "final"
release!?!?!?!


ps (to the POV team) I know it sounds like I'm griping, but keep up the
good work anyway!


----------------------------------------------
"Since just about everything on my Windows NT Workstation computer got
inexplicably 
wiped out yesterday, for the third time in as many months, I would say
BillGatus 
of Borg has us adequately prepared for Y2K by simply acclimatizing us to
the concept 
by wiping us out on a monthly, rather than millennial, basis. We'll
hardly notice."

            - Jack Ricard, December 98 Boardwatch

Post a reply to this message