 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 9:20 AM, Jim Holsenback wrote:
> On 1/11/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
also stumbled upon a windows docs issue as well ...
in 3.2.4.1 output file type towards the bottom in the paragraph that
starts as: The Radiance Synthetic Imaging System ... there are two
external links: Radiance and OpenEXR. the Radiance link opens up the
web page inside the windows help viewer, the OpenEXR link opens up the
web age in default web /browser/ OpenEXR also appears as >>OpenEXR
also have a look from 2.5.6 --> to the bottom of that page there is a
mix of external links that exhibit the same behavior ... links that are
preceded by >> open up the web page in default web browser and the links
/without/ >> open web page inside the windows help viewer.
looked on the wiki and /all/ links markup are consistent and the nix
docs look fine (no >> anywhere) so i'm guessing it's regex issue in the
post processing that creates the doze docs
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 10:28 AM, Jim Holsenback wrote:
> also have a look from 2.5.6 --> to the bottom of that page there
make that from 2.5.1
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/01/2017 2:50 PM, clipka wrote:
...
>> Hm... I'll have to check with Chris whether he also used Visual Studio
>> 2010 for the beta editor DLLs. (The beta does need its own version of
>> the DLLs to not interfere with an existing installation of 3.7.0 proper.
>> Other than that they should be interchangeable, though the beta DLLs
>> also contain some bugfixes.)
>
> Chris just informed me that the editor DLLs have been built with Visual
> Studio 2015, so they may or may not work on XP. Please do let us know
> how you're faring.
>
On WinVista home premium sp2 64-bit
All three POV-Ray application files run fine, no problems noted.
pvengine, pvengine-sse2, pvengine64(default).
On WinXP sp3 32-bit
pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
problems opening a file tab.
From windows_explorer, click-hold-drag drop on editor works, new tab is
opened.
Menu/File/recently used list, select, new tab is opened.
Open icon, select file - open, no new tab is opened.
Menu/File/Open, select file - open, no new tab is opened.
Still working through some combinations.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 17:28 schrieb StephenS:
> On 13/01/2017 2:50 PM, clipka wrote:
> ....
>>> Hm... I'll have to check with Chris whether he also used Visual Studio
>>> 2010 for the beta editor DLLs. (The beta does need its own version of
>>> the DLLs to not interfere with an existing installation of 3.7.0 proper.
>>> Other than that they should be interchangeable, though the beta DLLs
>>> also contain some bugfixes.)
>>
>> Chris just informed me that the editor DLLs have been built with Visual
>> Studio 2015, so they may or may not work on XP. Please do let us know
>> how you're faring.
>>
> On WinVista home premium sp2 64-bit
> All three POV-Ray application files run fine, no problems noted.
> pvengine, pvengine-sse2, pvengine64(default).
>
> On WinXP sp3 32-bit
> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
> problems opening a file tab.
>
> From windows_explorer, click-hold-drag drop on editor works, new tab is
> opened.
> Menu/File/recently used list, select, new tab is opened.
> Open icon, select file - open, no new tab is opened.
> Menu/File/Open, select file - open, no new tab is opened.
>
> Still working through some combinations.
Don't bother -- it doesn't work properly on XP, that's all we need to
know for now. This is (in all likelyhood) not a matter of identifying
and fixing problematic source code, but of choosing the right build
settings (or even the right compiler version).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 15:20 schrieb Jim Holsenback:
> On 1/11/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
>>
>> Happy testing!
>>
> well since i'm not a doze user perhaps it's just me but ... this release
> seems to be having trouble honoring the Display = On option in the
> master povray.ini file as well as having it in a povray.ini file in the
> directory that the povray sdl file resides. In order to get a render
> display i have to add +d in toolbar command line. btw: it (beta) is
> reading all the other options (library path) options that i have in the
> master povray.ini file
Just to avoid confusion: I understand that you're not /normally/ a
Windows user, but are reporting your results of testing POV-Ray for
Windows - is that correct?
Are you testing on a genuine Windows machine, a virtual machine, or an
emulator (e.g. Wine)?
Also, which binary are you using - 32 bit, 32 bit SSE2, or 64 bit?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 1:42 PM, clipka wrote:
> Am 14.01.2017 um 15:20 schrieb Jim Holsenback:
>> On 1/11/2017 12:59 AM, clipka wrote:
>>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>>> Source code and Windows binaries are available on GitHub:
>>>
>>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>>
>>> (beta.1 was an internal release only.)
>>>
>>> The beta version is designed to install in its own dedicated directory,
>>> and live happily alongside an existing 3.7 installation.
>>>
>>> Happy testing!
>>>
>> well since i'm not a doze user perhaps it's just me but ... this release
>> seems to be having trouble honoring the Display = On option in the
>> master povray.ini file as well as having it in a povray.ini file in the
>> directory that the povray sdl file resides. In order to get a render
>> display i have to add +d in toolbar command line. btw: it (beta) is
>> reading all the other options (library path) options that i have in the
>> master povray.ini file
adding that i installed beta down an alternate path (in my documents)
the 3.7 distribution lives in program files
>
> Just to avoid confusion: I understand that you're not /normally/ a
> Windows user, but are reporting your results of testing POV-Ray for
> Windows - is that correct?
you would be correct
>
> Are you testing on a genuine Windows machine, a virtual machine, or an
> emulator (e.g. Wine)?
the first one flavored windows 7 pro
>
> Also, which binary are you using - 32 bit, 32 bit SSE2, or 64 bit?
>
the later
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 16:28 schrieb Jim Holsenback:
> On 1/14/2017 9:20 AM, Jim Holsenback wrote:
>> On 1/11/2017 12:59 AM, clipka wrote:
>>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>>> Source code and Windows binaries are available on GitHub:
>>>
>>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>>
>>> (beta.1 was an internal release only.)
>>>
>>> The beta version is designed to install in its own dedicated directory,
>>> and live happily alongside an existing 3.7 installation.
>
> also stumbled upon a windows docs issue as well ...
>
> in 3.2.4.1 output file type towards the bottom in the paragraph that
> starts as: The Radiance Synthetic Imaging System ... there are two
> external links: Radiance and OpenEXR. the Radiance link opens up the
> web page inside the windows help viewer, the OpenEXR link opens up the
> web age in default web /browser/ OpenEXR also appears as >>OpenEXR
I can confirm that; more precisely, it's "»OpenEXR", where "»" is the
Unicode/ISO-Latin-1 character U+00BB, "RIGHT-POINTING DOUBLE ANGLE
QUOTATION MARK".
> also have a look from 2.5.6 --> to the bottom of that page there is a
> mix of external links that exhibit the same behavior ... links that are
> preceded by >> open up the web page in default web browser and the links
> /without/ >> open web page inside the windows help viewer.
>
> looked on the wiki and /all/ links markup are consistent and the nix
> docs look fine (no >> anywhere) so i'm guessing it's regex issue in the
> post processing that creates the doze docs
I can confirm that this is indeed created during post-processing for the
Windows HTML Help. From what I glean from the conversion script this is
intended to mark external links, but from the results I conclude that it
indeed fails to catch all instances.
From what I see, there are two cases in which the algorithm fails:
- Non-HTTP external links (e.g. "https://whatever").
- External links followed by more links (external or internal) on the
same HTML source line.
Looks like I can amend the script to catch those as well. If you
discover any instances that don't fall in either category, feel free to
holler out loud.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 17:28 schrieb StephenS:
> On WinXP sp3 32-bit
> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
> problems opening a file tab.
Stephen, can you please try this experimental version of the editor
DLLs, and let us know whether it solves the XP issues:
www.povray.org/temp/povwin-3.7-beta-editor.exe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 15/01/2017 12:55 AM, clipka wrote:
> Am 14.01.2017 um 17:28 schrieb StephenS:
>
>> On WinXP sp3 32-bit
>> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
>> problems opening a file tab.
>
> Stephen, can you please try this experimental version of the editor
> DLLs, and let us know whether it solves the XP issues:
>
> www.povray.org/temp/povwin-3.7-beta-editor.exe
>
Same problems.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 15/01/2017 22:31, StephenS wrote:
> On 15/01/2017 12:55 AM, clipka wrote:
>> Am 14.01.2017 um 17:28 schrieb StephenS:
>>
>>> On WinXP sp3 32-bit
>>> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
>>> problems opening a file tab.
>>
>> Stephen, can you please try this experimental version of the editor
>> DLLs, and let us know whether it solves the XP issues:
>>
>> www.povray.org/temp/povwin-3.7-beta-editor.exe
>>
> Same problems.
Can you try dropping in, one by one, the editor DLL's from the 3.7.0
distribution (just copy & paste from the 3.7 bin directory) and find
out if/when the problem goes away? If so, changing which DLL fixed it?
Note: the 3.7.0 DLL's will pick up your 3.7.0 editor configuration,
this is to be expected.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
