[Extendflash] getCustomStroke() - Seems like serious bug

[Jarrad Hope]

Yeh this is definatly broken,
just talked to ibis, perhaps a workaround
until macromedia fix this is

setting the fill then using
using swapStrokeandFill();

then setting the fill back to what it was originally??


On Fri, 07 Oct 2005 11:34:45 +0800, Ibis Fernandez  
<ibis at cinestarfilmworks.com> wrote:

> Can some please verify that this is in fact a bug and that I’m not just
> going crazy trying to fix something that is the result of a bug in flash  
> as
> opposed to something in my code.
> Basically, in one of my extensions there is a series of functions that  
> send
> color data to the color chip of the stroke. In flash 8 this no longer  
> works.
> At first I though this was due to some of the changes such as the  
> additional
> properties that have been added to the stroke object but…. And here is  
> the
> big “BUTT” after going over and over the manual, and the messing with it  
> for
> hours I just cant seem to get it to work the way its supposed to…
> Here’s the basic function:
> var stroke = fl.getDocumentDOM().getCustomStroke();
> stroke.style= "solid";
> stroke.color = "#CCCCCC";
> fl.getDocumentDOM().setCustomStroke(stroke);
> Try it, you’ll see that rather than changing the color to #cccccc it
> actually changes to a shade of black with like 1% alpha… The wacky thing  
> is
> that if you click the stroke chip and look at the pull out color picker,  
> the
> little field reads “#CCCCC” yet displays the black color. If you look at  
> the
> color mixer panel, the hex color reads “#90DE59” (how the heck did that
> happened?). It also seems to change the stroke size to 6.6 for some crazy
> reason.
> Hopefully one of you can confirm that this is a bug, or hopefully  
> suggest a
> work around to use.
> Thanks.
>