 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I posted this a few years a go, but recently did a few tweaks to fixed
compatibility issue with the original version.
Mike
Post a reply to this message
Attachments:
Download 'screen.inc.txt' (8 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/3/2016 9:31 PM, Mike Horvath wrote:
> I posted this a few years a go, but recently did a few tweaks to fixed
> compatibility issue with the original version.
>
> Mike
Forgot to add a test scene.
Mike
Post a reply to this message
Attachments:
Download 'axonometric_projection_comparison.pov.txt' (10 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/03/2016 09:31 PM, Mike Horvath wrote:
> I posted this a few years a go, but recently did a few tweaks to fixed
> compatibility issue with the original version.
There is no license statement with your file. It is evident that you
based your modifications on a pre-3.7 version of the file, and as such,
it would bear the license of that version of POV-Ray, but there is no
indication of that to the user.
You should be aware that there was a change to macro Screen_Object in
version 3.7. If you are considering this change, note that it will
cause a parse error in versions 3.5 and 3.6.*.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I updated the script slightly. There is now also the license, and I
incorporated the official changes to the Screen_Object macro.
Mike
Post a reply to this message
Attachments:
Download 'screen.inc.txt' (8 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 08/30/2018 09:32 PM, Mike Horvath wrote:
> I updated the script slightly. There is now also the license, and I
> incorporated the official changes to the Screen_Object macro.
>
>
> Mike
Why does it save and restore the version, but not change it?
--
dik
Rendered 1024 of 921600 pixels (0%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/30/2018 9:36 PM, dick balaska wrote:
> On 08/30/2018 09:32 PM, Mike Horvath wrote:
>> I updated the script slightly. There is now also the license, and I
>> incorporated the official changes to the Screen_Object macro.
>>
>>
>> Mike
>
> Why does it save and restore the version, but not change it?
>
I forgot about that. What should I do instead?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 08/30/2018 10:38 PM, Mike Horvath wrote:
> On 8/30/2018 9:36 PM, dick balaska wrote:
>> On 08/30/2018 09:32 PM, Mike Horvath wrote:
>>> I updated the script slightly. There is now also the license, and I
>>> incorporated the official changes to the Screen_Object macro.
>>>
>>
>> Why does it save and restore the version, but not change it?
>>
>
> I forgot about that. What should I do instead?
>
I would just delete those two lines, they are unnecessary.
--
dik
Rendered 1024 of 921600 pixels (0%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/30/2018 10:58 PM, dick balaska wrote:
> On 08/30/2018 10:38 PM, Mike Horvath wrote:
>> On 8/30/2018 9:36 PM, dick balaska wrote:
>>> On 08/30/2018 09:32 PM, Mike Horvath wrote:
>>>> I updated the script slightly. There is now also the license, and I
>>>> incorporated the official changes to the Screen_Object macro.
>>>>
>>>
>>> Why does it save and restore the version, but not change it?
>>>
>>
>> I forgot about that. What should I do instead?
>>
>
> I would just delete those two lines, they are unnecessary.
>
>
Okay. Unfortunately, the file has never had any version numbers, so all
the different versions floating around (I'm not the only one) are hard
to keep straight.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Another update, with more of Dick's tips.
Mike
Post a reply to this message
Attachments:
Download 'screen.inc.txt' (8 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.08.2018 um 04:58 schrieb dick balaska:
> On 08/30/2018 10:38 PM, Mike Horvath wrote:
>> On 8/30/2018 9:36 PM, dick balaska wrote:
>>> On 08/30/2018 09:32 PM, Mike Horvath wrote:
>>>> I updated the script slightly. There is now also the license, and I
>>>> incorporated the official changes to the Screen_Object macro.
>>>>
>>>
>>> Why does it save and restore the version, but not change it?
>>>
>>
>> I forgot about that. What should I do instead?
>>
>
> I would just delete those two lines, they are unnecessary.
A smarter approach would be to leave them in, and add a `#version 3.7`
(or some such) indicating the minimum version of POV-Ray known to work
with the include file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
