|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Recently, in another Object Collection module, I deprecated a global parameter
that should have been applied as needed to each object, i.e., a macro argument.
For this update, I introduce a global parameter. Always a judgment call.
In Caption 1.0.1 and earlier, a caption with descenders and a caption without
descenders will not center on the same baseline. A global parameter seemed
right in this case for maintaining consistency between macro calls. Of course,
the same result can be achieved by passing the same value in every macro call,
but at what point does adding yet another argument make sticking to a principle
more unwieldy that it's worth?
In Caption version 1.1:
- The top padding may differ from the bottom padding.
- There is an option to pad around the font metrics rather than the
text itself.
- A texture may be obtained without being attached to an object.
http://lib.povray.org/searchcollection/index2.php?objectName=Caption&contributorTag=Cousin%20Ricky
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> In Caption 1.0.1 and earlier, a caption with descenders and a caption without
> descenders will not center on the same baseline. A global parameter seemed
> right in this case for maintaining consistency between macro calls. Of course,
> the same result can be achieved by passing the same value in every macro call,
> but at what point does adding yet another argument make sticking to a principle
> more unwieldy that it's worth?
Agreed. My high school English teacher said, "You have to learn what the rules
are before you can break them." I think that was great advice.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 5/7/2016 8:53 PM, Cousin Ricky wrote:
> Recently, in another Object Collection module, I deprecated a global parameter
> that should have been applied as needed to each object, i.e., a macro argument.
> For this update, I introduce a global parameter. Always a judgment call.
>
> In Caption 1.0.1 and earlier, a caption with descenders and a caption without
> descenders will not center on the same baseline. A global parameter seemed
> right in this case for maintaining consistency between macro calls. Of course,
> the same result can be achieved by passing the same value in every macro call,
> but at what point does adding yet another argument make sticking to a principle
> more unwieldy that it's worth?
>
> In Caption version 1.1:
> - The top padding may differ from the bottom padding.
> - There is an option to pad around the font metrics rather than the
> text itself.
> - A texture may be obtained without being attached to an object.
>
>
http://lib.povray.org/searchcollection/index2.php?objectName=Caption&contributorTag=Cousin%20Ricky
>
>
>
Does your caption script work when using focal blur?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/14/2016 12:42 AM, Mike Horvath wrote:
> Does your caption script work when using focal blur?
The caption objects are part of the scene, so as such, they are affected
by focal blur in the same way as other objects. If the captions are in
the focal plane, they will not be blurred.
If you are using screen.inc to place the captions (as in the example
scene), then you can't use focal blur anyway, unless you perform even
more surgery on screen.inc. But if you do make such a change, be
prepared for a Screen_Object() to place a lot of blurry objects.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|