 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <kua### [at] videotron ca> wrote:
>
> Maybe you got a broken download.
Well, this seemed to be after trying the 3.8 alpha v499 and I'm not going to try
that again yet. I don't think it began with the first alpha.
Something probably going on with the Windows Registry entries, even before that,
due to my installing so many versions of POV-Ray. Somehow able to run the
different version okay, except v3.5 and maybe MegaPOV. I considered them shelved
for the time being until I could find a fix (MegaPOV renders okay again, too,
while v3.5 remains uninstalled).
To recap on that again, as Clipka said, there should be a POV-Ray.Scene key in
the HKCR section (not just within the .pov key), and all I have in HKCR is .pov
and povfile which is a result of version 3.6 installation (or so it seems).
Strange to me that version 3.7.0.0 is okay this way after the restore point from
last week. But then, nothing was wrong until 3.8 alpha.
And now I've found a key in the registry that contains both povfile and
POV-Ray.Scene, yet both have _.pov appended to them at:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts
Another mention of those without the _.pov at:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pov\OpenWithProgids
Needless to say I'm good at making a mess of things even without potential
program bugs!
I'm considering going the route of uninstalling 3.6, 3.7.1-beta9, 3.7.1-rc and
3.7.0.0 (because I put it into renamed folder 3.70) then just installing 3.7.0.0
again.
Does any of this help explain what might have happened?
Could pvengine64.exe of 3.8 alpha alone do anything to cause this?
Or would the editor need a reinstall simply from putting 3.8 alpha in? Makes no
sense to me anyway.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.09.2017 um 06:34 schrieb omniverse:
> To recap on that again, as Clipka said, there should be a POV-Ray.Scene key in
> the HKCR section (not just within the .pov key), and all I have in HKCR is .pov
> and povfile which is a result of version 3.6 installation (or so it seems).
There's nothing wrong with that: POV-Ray 3.6 and earlier registered the
`.pov` file type as `povfile`, while POV-Ray 3.7 and later renamed that
to `POV-Ray.Scene`. Different monikers, same mechanism.
> Does any of this help explain what might have happened?
>
> Could pvengine64.exe of 3.8 alpha alone do anything to cause this?
> Or would the editor need a reinstall simply from putting 3.8 alpha in? Makes no
> sense to me anyway.
Makes no sense to me either.
If you run into the issue again, please let us know.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 29.09.2017 um 06:34 schrieb omniverse:
>
> There's nothing wrong with that: POV-Ray 3.6 and earlier registered the
> `.pov` file type as `povfile`, while POV-Ray 3.7 and later renamed that
> to `POV-Ray.Scene`. Different monikers, same mechanism.
Okay, thanks again.
I delayed a while with the uninstall/reinstall of 3.7.0 so I'm just now getting
a look at the Windows Registry.
POV-Ray.Scene is there after that, listed right after povfile. No problems with
file open or save (as). Apparently that's what happened, lost the POV-Ray.Scene
somehow.
Just got me curious about Windows 10 possibly juggling the pov file associations
around to allow the different versions to work together.
If happens again, easily fixed by exporting that POV-Ray.Scene key now and
importing it back into the Registry. If there ever is a next time.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 9/21/2017 3:10 PM, clipka wrote:
> Be advised that this binary-only release wants to reside in an existing
> v3.7.x installation.
nix is working oh-key-dokey fine however doze has an issue ... binary in
v3.7.1 install directory but help buttons for POV-Win and Scene aren't
working
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.10.2017 um 02:07 schrieb Jim Holsenback:
> On 9/21/2017 3:10 PM, clipka wrote:
>> Be advised that this binary-only release wants to reside in an existing
>> v3.7.x installation.
>
> nix is working oh-key-dokey fine however doze has an issue ... binary in
> v3.7.1 install directory but help buttons for POV-Win and Scene aren't
> working
Yes, that's a known issue: v3.8 can't load the v3.7 help file.
To work around this, download the help file directly from the
`release/v3.8.0` branch, and copy it into the v3.7 install's `help`
directory.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/1/2017 4:13 AM, clipka wrote:
> Am 01.10.2017 um 02:07 schrieb Jim Holsenback:
>> On 9/21/2017 3:10 PM, clipka wrote:
>>> Be advised that this binary-only release wants to reside in an existing
>>> v3.7.x installation.
>>
>> nix is working oh-key-dokey fine however doze has an issue ... binary in
>> v3.7.1 install directory but help buttons for POV-Win and Scene aren't
>> working
>
> Yes, that's a known issue: v3.8 can't load the v3.7 help file.
>
> To work around this, download the help file directly from the
> `release/v3.8.0` branch, and copy it into the v3.7 install's `help`
> directory.
>
copied as is and when that didn't work went through several renaming
incantations with no joy
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.10.2017 um 11:20 schrieb Jim Holsenback:
> On 10/1/2017 4:13 AM, clipka wrote:
>> Am 01.10.2017 um 02:07 schrieb Jim Holsenback:
>>> On 9/21/2017 3:10 PM, clipka wrote:
>>>> Be advised that this binary-only release wants to reside in an existing
>>>> v3.7.x installation.
>>>
>>> nix is working oh-key-dokey fine however doze has an issue ... binary in
>>> v3.7.1 install directory but help buttons for POV-Win and Scene aren't
>>> working
>>
>> Yes, that's a known issue: v3.8 can't load the v3.7 help file.
>>
>> To work around this, download the help file directly from the
>> `release/v3.8.0` branch, and copy it into the v3.7 install's `help`
>> directory.
>>
>
> copied as is and when that didn't work went through several renaming
> incantations with no joy
Presuming your v3.7 installation and the v3.8.0-alpha binary reside in
`C:\Program Files\POV-Ray\v3.7`, then the v3.8 help file
(`distribution\platform-specific\windows\Help\povray.chm` in the repo)
should work fine when dropped in as `C:\Program
Files\POV-Ray\v3.7\help\povray.chm`.
Note that v3.8.0-alpha always looks for its help file in your v3.7
(release proper, i.e. v3.7.0, or RC, i.e. v3.7.1-rc.1) installation
directory tree, regardless of where you place the v3.8.0-alpha binary.
Most notably, if you accidently placed the v3.8.0-alpha binary in a
v3.7-beta installation (e.g. v3.7.1-beta.9), it will still try to load
the help file from wherever your v3.7 proper installation resides.
Also note that the help file must be named `povray.chm` (as in the
`release/v3.8.0` branch), /not/ `povray37.chm` (as still in the master
branch, IIRC).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/2/2017 8:31 AM, clipka wrote:
> Presuming your v3.7 installation and the v3.8.0-alpha binary reside in
> `C:\Program Files\POV-Ray\v3.7`, then the v3.8 help file
> (`distribution\platform-specific\windows\Help\povray.chm` in the repo)
> should work fine when dropped in as `C:\Program
> Files\POV-Ray\v3.7\help\povray.chm`.
>
> Note that v3.8.0-alpha always looks for its help file in your v3.7
> (release proper, i.e. v3.7.0, or RC, i.e. v3.7.1-rc.1) installation
> directory tree, regardless of where you place the v3.8.0-alpha binary.
> Most notably, if you accidently placed the v3.8.0-alpha binary in a
> v3.7-beta installation (e.g. v3.7.1-beta.9), it will still try to load
> the help file from wherever your v3.7 proper installation resides.
>
> Also note that the help file must be named `povray.chm` (as in the
> `release/v3.8.0` branch), /not/ `povray37.chm` (as still in the master
> branch, IIRC).
well i uninstalled 3.7.1 beta and put the pvengine64 into my remaining
3.7.0 bin directory and povray.chm into help directory. now the help
buttons work but all i get is the left pane and none of the links are
clickable ... not that big of an issue for /me/ because i prefer the
html version
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 04.10.2017 um 14:20 schrieb Jim Holsenback:
> well i uninstalled 3.7.1 beta and put the pvengine64 into my remaining
> 3.7.0 bin directory and povray.chm into help directory. now the help
> buttons work but all i get is the left pane and none of the links are
> clickable ... not that big of an issue for /me/ because i prefer the
> html version
Now that's odd... can anyone confirm?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 04.10.2017 um 14:20 schrieb Jim Holsenback:
>
> > well i uninstalled 3.7.1 beta and put the pvengine64 into my remaining
> > 3.7.0 bin directory and povray.chm into help directory. now the help
> > buttons work but all i get is the left pane and none of the links are
> > clickable ... not that big of an issue for /me/ because i prefer the
> > html version
>
> Now that's odd... can anyone confirm?
Same thing here. Before I was going to say anything I was trying a few things to
see if I could get it to work, such as trying to default to Internet Explorer
rather than Windows 10 Edge.
I used the direct link to the Help file you provided, although I had gotten that
file from github before that and it was the same way but there were two
different byte sizes for the files.
Install directory is actually 3.7.0, not just 3.7 so I can only wonder if that
has anything to do with this.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
