BobH wrote:
> To get back into AppData\Roaming\POV-Ray\v3.6\Scenes I must first change 
> the "view hidden files" setting outside of POV to see it in the open 
> file dialog.

Oh, that's what I was talking about. The option to get to "view hidden 
files" is hitting ALT in Explorer. They hid the "normal" menu bar.

I agree that putting the user's data files under AppData seems like the 
wrong place. If you can use it with other programs (e.g., text editors), it 
should probably go under "My Documents" somewhere.

> Hope I'm making sense.

Yes.

-- 
   Darren New, San Diego CA, USA (PST)
   There's no CD like OCD, there's no CD I knoooow!

Post a reply to this message

Ken wrote:
> The install went smoothly on Vista 64 but it intalled the 32 bit version 
> rather than the 64 bit version. I presum the 64 bit compile will be made 
> available in a different dowload package once you have time to put it 
> together?

Hi Ken,

Yes, the version of InstallShield I've got doesn't allow me to make dual 32
and 64-bit installers. I'll make the 64-bit one available once the 32 is
settled.

regards,

-- Chris

Post a reply to this message

BobH wrote:
> Looks good! The install asked me to uninstall the previous one so that 
> answers a question I was wondering as to whether or not a backup was 
> possible same as earlier 3.6 installs. Guessing the idea is clean installs 
> only...?

This isn't really under my control, it's a Windows Installer thing, so yes
- clean installs only. It's also why I use a different install path (even
on Windows XP); there's no way for me to tell Windows Installer to backup
the old files, especially files that weren't installed by it (as 3.61c did
not use WI).

> Got to say it... program and scene file location is bothersome to me.

I don't like it either. I feel uncomfortable having everything in the one
place (which is why I fixed it in 3.7). However the code refers to the
install path in many places and since the codebase is now so different
between v3.6 and v3.7 I'd basically have to do all the changes over again.

But thinking of it, I really think you're right. I might just have to go in
and do it.

> wants to go elsewhere and the hidden scenes location is lost. I presume this 
> is in part due to the install finding the file open location where 3.6.1c 
> was last at.

This would be due to the shared registry settings.

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1b930d$1@news.povray.org...
> BobH wrote:
>
>> Got to say it... program and scene file location is bothersome to me.
>
> I don't like it either. I feel uncomfortable having everything in the one
> place (which is why I fixed it in 3.7). However the code refers to the
> install path in many places and since the codebase is now so different
> between v3.6 and v3.7 I'd basically have to do all the changes over again.
>
> But thinking of it, I really think you're right. I might just have to go 
> in
> and do it.

Which is why I didn't want to make you feel pressured to do that just for my 
own sake. I'm sure you would rather consider this new 3.6 version finished.

The way it's an update to 3.6 I know most people will find all this to be a 
problem, too, when they try to go from the old to new. I thought it might 
not matter if no previous file were already left open in 3.6.1c when last 
used. What I really didn't expect (but probably should have) was 3.6.2 
finding one elsewhere even when no open files were left in editor, by going 
into File|Open.

For me, not so much a problem if the file view settings had not locked me 
out. That made me believe it was causing trouble for either Windows, or POV 
itself had difficulty interfacing with the file system, or whatever other 
reason unknown to me. I've only kept everything as administrator status, no 
other user account exists.

Bob

Post a reply to this message

Chris Cason wrote:
> Folks,
> 
> I've generated a v3.62 RC1 POVWIN and new installer. I'd appreciate it if
> some of you could test it as the installer in particular is a re-write.
> 
>   http://www.povray.org/temp/POVWin-v3.62-RC1.msi
> 
> Note: on Vista systems, the files will be installed by default to your
> local profile. On XP and earlier, the default remains Program Files.

I've updated this to RC2, which includes splitting the binaries and text
files dirs.

    http://www.povray.org/temp/POVWin-v3.62-RC2.msi

Scenes, INI files, etc, will be installed to "My Documents\POV-Ray\v3.6"
(or the equivalent).

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a1bcd68$1@news.povray.org...
>
> I've updated this to RC2, which includes splitting the binaries and text
> files dirs.
>
>    http://www.povray.org/temp/POVWin-v3.62-RC2.msi
>
> Scenes, INI files, etc, will be installed to "My Documents\POV-Ray\v3.6"
> (or the equivalent).

Wow, that was fast! A tremendous thank you from me to you. So much better 
this way.

Guess I'm going to be removing 3.6.1c after I check this new one awhile, 
MegaPOV, etc.

Hmmm. Some tidying up to do in that first install location, the uninstall 
left renders in there because I didn't change from default file output.  : )

Bob

Post a reply to this message

"BobH" <omniverse*charter!net> wrote in message 
news:4a1c0e57@news.povray.org...
>
> Guess I'm going to be removing 3.6.1c after I check this new one awhile, 
> MegaPOV, etc.

Trouble with library paths using megapov, needed to move its includes into 
the v3.6\includes. Seems peculiar that it didn't want to use the 
Library_Path= I added for its own location(s).
So to anyone else doing megapov+v3.6.2, put the files into the v3.6 
locations (unless you have success any other way first). I just didn't want 
to mix them but this was the only way.

Post a reply to this message

Another pass at a hopefully final 32-bit binary and installer:

  http://www.povray.org/temp/POVWin-v3.62.msi

The only significant difference between this and RC2 is that libpng has
been updated to the latest available.

-- Chris

Post a reply to this message

Ken wrote:
t smoothly on Vista 64 but it intalled the 32 bit version
> rather than the 64 bit version. I presum the 64 bit compile will be made 
> available in a different dowload package once you have time to put it 
> together?

Hi Ken,

Please give this a try:

  http://www.povray.org/temp/POVWin-v3.62-64bit.msi

-- Chris

Post a reply to this message

"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in 
message news:4a2252f6@news.povray.org...
> Ken wrote:
> t smoothly on Vista 64 but it intalled the 32 bit version
>> rather than the 64 bit version. I presum the 64 bit compile will be made
>> available in a different dowload package once you have time to put it
>> together?
>
> Hi Ken,
>
> Please give this a try:
>
>  http://www.povray.org/temp/POVWin-v3.62-64bit.msi
>
> -- Chris

Worked just peachy, Chris. The install was clean and the renderer appears to 
be fully functional.
I'll beat up on it for a while but the few scenes I've rendered so far look 
good.

Ken

Post a reply to this message