flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34732) borderColor
Date Thu, 12 Feb 2015 20:47:11 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318953#comment-14318953
] 

Jim Brown commented on FLEX-34732:
----------------------------------

I also see this problem on SDK 4.14.0 with an existing mobile project. This mobile project
works fine with 4.13 and all earlier SDKs.

The messages in Flex Builder 4.7 do not include a valid Path. They only have a line number
which does not correspond to any of the usages in the source files. This would suggest the
error is happening in the framework. 
Is there any way to get Flex Builder to show me the source causing the warning?

The style 'borderColor' is only supported by type 'spark.components.TextArea' with the theme(s)
'spark'.
ine 1166	Flex Problem
The style 'borderColor' is only supported by type 'spark.components.TextInput' with the theme(s)
'spark'.	
line 1148	Flex Problem
Each warning shows up 2 times.

I have a total of six usages of borderColor, all in <s:List ...> controls.


> borderColor
> -----------
>
>                 Key: FLEX-34732
>                 URL: https://issues.apache.org/jira/browse/FLEX-34732
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Mobile
>    Affects Versions: Apache Flex 4.14.0
>         Environment: ios - iphone 5 up
>            Reporter: shawn0liou
>            Priority: Trivial
>
> Encountered errors or warnings while building project index.mxml.
> The style 'borderColor' is only supported by type 'spark.components.TextArea' with theme(s)
'spark'
> The style 'borderColor' is only supported by type 'spark.components.TextInput' with theme(s)
'spark'
> =====================================
> problem  in 4.14.0
> 4.13.0 no problem



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message