There may be some unfinished work in making the boxmodel support independent
borders. I seem to recall there is a mismatch between the kernel support and
boxmodel implementation.
On 2011-09-21, at 09:24, Rami Ojares / AMG wrote:
> I also tried notation
> $once{['pink', 'maroon', 'lime', 'navy']}
> but that gave me the error
> boxmodel.lzx≈332: TypeError: Error #1034
>
> - rami
>
> On 09/21/2011 07:18 PM, Rami Ojares / AMG wrote:
>> Tucker to the rescue!
>> I tried your notation and it works.
>> Reminds me of the highfalutin discussions I had with you
>> on types and their possible representations. :-)
>> Thanks alot.
>>
>> - rami
>>
>> On 09/21/2011 06:39 PM, P T Withington wrote:
>>> This may be due to insufficient precision in the API documentation.
>>>
>>> The new attributes that are settable by CSS have much more strict immediate
>>> representations. In this particular case, I expect the immediate value of
>>> bordercolor is required to be an array or colors, something like:
>>>
>>> bordercolor="$once{['pink']}"
>>>
>>> (I think you can specify up to 4 colors, for top, right, bottom, left
>>> border.)
>>>
>>> You could try setting the color using a style. If that works, then I
>>> believe my explanation. I don't have time right now to check the source,
>>> sorry.
>>>
>>> On 2011-09-21, at 08:09, Rami Ojares / AMG wrote:
>>>
>>>> Hi,
>>>>
>>>> I noticed that setting the bordercolor attribute in the boxmodel
>>>> makes the border transparent. If I don't set it, it is black as expected.
>>>>
>>>> Try the following for example:
>>>>
>>>> <canvas proxied="false" allowfullscreen="true" framerate="20"
>>>> bgcolor="green">
>>>> <view with="boxmodel" height="50" width="50" bordertopwidth="3"
>>>> bgcolor="red" bordercolor="pink"/>
>>>> </canvas>
>>>>
>>>> The top border is transparent although it should be pink.
>>>>
>>>> - rami
>>
>
