Good point. That would work, but I think I would no longer be able to
deal with the background color using getStyle('backgroundColor') from
my custom component (it wouldn't exist). Essentially I'd have to set
a backgroundColor class variable from setStyle(). Not terrible. Any
better ideas?
--- In [email protected], "Pan Troglodytes"
<[EMAIL PROTECTED]> wrote:
>
> This might be kind of a hack, but you could override setStyle, catch the
> backgroundcolor style being set and not call the super for it.
>
> On Tue, Sep 16, 2008 at 9:52 AM, aaronius9er9er <[EMAIL PROTECTED]>wrote:
>
> > Hi all,
> >
> > I'm creating a custom component which extends Container. I would like
> > to use the backgroundColor style to style certain parts of the custom
> > component. I don't have any problem getting access to the style and
> > doing what I want with it within my component, but the parent
> > Container class uses the style as well and paints the background of
> > the whole component (from the very top-left to the very top-right).
> >
> > I there an easy way to say...hey parent, don't use the backgroundColor
> > style or use NaN instead of what the developer actually set?
> >
> > Thanks!
> >
> >
> >
>
>
>
> --
> Jason
>
