Cyrill Zadra created FLEX-33458:
---
Summary: Spark ColorPicker
Key: FLEX-33458
URL: https://issues.apache.org/jira/browse/FLEX-33458
Project: Apache Flex
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/FLEX-33458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-33458:
Description: Make Spark ColorPicker component in experimental project
release ready. (was: Make
Makes sense to me.
As far as #1 goes: I added the following two functions to the main component. I
think that makes the most sense. Putting it into a utility class would require
passing in the colorField and labelField values:
public function getColorValue(color:*):uint
public function getColorN
Harbs,
I'm personally not a fan of sending untyped data back and forth
-- especially if it is at all possible to avoid it. What are your thoughts
on sending back a color:uint and colorObject:Object as separate items
within the event?
-Nick
On Fri, Mar 1, 2013 at 10:01 AM, Harbs wrote:
> I've
I've expanded the Bogdan ColorPicker to accept a dataProvider including color
objects similar to the way the mx ColorPicker worked.
I have a few things that I could use input on:
1) Both the skin and the component have functions to compute the color
depending on whether it's a uint or object. A
