Skip to main content
Participating Frequently
October 8, 2008
Question

using the SDK trunk

  • October 8, 2008
  • 4 replies
  • 1444 views
Hi all,<br /><br />I was trying build a large project off of trunk, and I've run into a<br />few problems. I wanted to check out some of the compiler performance<br />improvements, but it's not critical that I run things off of trunk.<br />(I'll probably try to move a few to the Flex 3 branch instead.) But I<br />wanted to let you know about the issues I had, and see which ones of<br />them I should create bugs on.<br /><br />1. The first error I ran into when compiling was this:<br /><br /> [java] C:\perforce\trunk\ActionBar.mxml(109): Error: Access of<br />undefined property disabledIcon.<br /> [java]<br /> [java] disabledIcon="{itemRepeater.currentItem.disabledIcon}"<br /> [java]<br /> [java] C:\perforce\trunk\ActionBar.mxml(110): Error: Access of<br />undefined property overIcon.<br /> [java]<br /> [java] overIcon="{itemRepeater.currentItem.overIcon}"<br /> [java]<br /><br />I assume that currentItem was made non-dynamic, but I didn't look into<br />it. I just commented out the references to keep compiling.<br /><br />2. The second thing I ran into was the change of<br />"flex2.tools.Compiler" to "flex2.tools.Mxmlc". I can understand that<br />Mxmlc is clearer, but there's a lot of people who have the old name in<br />Ant files.<br /><br />3. The next compilation error:<br /><br /> [java] C:\perforce\trunk\LoginPanel.mxml(392): Error: Data<br />binding expressions not supported with attributes processed at compile<br />time.<br /> [java]<br /> [java] <mx:State name="{LOGIN_ERROR_STATE}"><br /> [java]<br /><br />We were using a const as a State name, which doesn't seem to be<br />allowed anymore. I put in the regular name, and everything compiled<br />fine at that point.<br /><br />4. When I then tried to compile in Flex Builder, I got the warnings<br />below. I assume this is because of a bad playglobal.swc reference?<br />Also, note that no line numbers are given. It drives me crazy when<br />Flex Builder does that. :)<br /><br />Description Resource Path Location Type<br />1046: Type was not found or was not a compile-time constant:<br />Matrix3D. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br /><br />Thanks, Brian
This topic has been closed for replies.

4 replies

Participating Frequently
October 8, 2008
Hi Matt, I'll file 1) and 3) as bugs then. Given the different syntax<br />of the Ant tasks, at least in Flex 3, I don't see a lot of people<br />switching over to the Ant tasks immediately. So it'd be nice to have<br />a Compiler class which simply calls the Mxmlc class, but it's<br />obviously not a big deal. Thanks, Brian<br /><br />On Wed, Oct 8, 2008 at 2:03 PM, Matt Chotin <member@adobeforums.com> wrote:<br />> A new message was posted by Matt Chotin in<br />><br />> Developers --<br />> using the SDK trunk<br />><br />> If (1) and (3) worked in SDK3 they should be filed as bugs. We've been making some changes in the binding code and may have broken stuff.<br />><br />> We're hoping that the Ant tasks themselves should be sufficient moving forward and folks won't have to write Java code that references the compiler directly. So I'm hoping that folks who are end-users won't care about the actual compiler class name?<br />><br />> Matt<br />><br />>
matt_chotin
Inspiring
October 8, 2008
If (1) and (3) worked in SDK3 they should be filed as bugs. We've been making some changes in the binding code and may have broken stuff.<br /><br />We're hoping that the Ant tasks themselves should be sufficient moving forward and folks won't have to write Java code that references the compiler directly. So I'm hoping that folks who are end-users won't care about the actual compiler class name?<br /><br />Matt<br /><br /><br />On 10/8/08 8:26 AM, "Brian Deitte" <member@adobeforums.com> wrote:<br /><br />A new discussion was started by Brian Deitte in<br /><br />Developers --<br /> using the SDK trunk<br /><br />Hi all,<br /><br />I was trying build a large project off of trunk, and I've run into a<br />few problems. I wanted to check out some of the compiler performance<br />improvements, but it's not critical that I run things off of trunk.<br />(I'll probably try to move a few to the Flex 3 branch instead.) But I<br />wanted to let you know about the issues I had, and see which ones of<br />them I should create bugs on.<br /><br />1. The first error I ran into when compiling was this:<br /><br /> [java] C:\perforce\trunk\ActionBar.mxml(109): Error: Access of<br />undefined property disabledIcon.<br /> [java]<br /> [java] disabledIcon="{itemRepeater.currentItem.disabledIcon}"<br /> [java]<br /> [java] C:\perforce\trunk\ActionBar.mxml(110): Error: Access of<br />undefined property overIcon.<br /> [java]<br /> [java] overIcon="{itemRepeater.currentItem.overIcon}"<br /> [java]<br /><br />I assume that currentItem was made non-dynamic, but I didn't look into<br />it. I just commented out the references to keep compiling.<br /><br />2. The second thing I ran into was the change of<br />"flex2.tools.Compiler" to "flex2.tools.Mxmlc". I can understand that<br />Mxmlc is clearer, but there's a lot of people who have the old name in<br />Ant files.<br /><br />3. The next compilation error:<br /><br /> [java] C:\perforce\trunk\LoginPanel.mxml(392): Error: Data<br />binding expressions not supported with attributes processed at compile<br />time.<br /> [java]<br /> [java] <mx:State name="{LOGIN_ERROR_STATE}"><br /> [java]<br /><br />We were using a const as a State name, which doesn't seem to be<br />allowed anymore. I put in the regular name, and everything compiled<br />fine at that point.<br /><br />4. When I then tried to compile in Flex Builder, I got the warnings<br />below. I assume this is because of a bad playglobal.swc reference?<br />Also, note that no line numbers are given. It drives me crazy when<br />Flex Builder does that. :)<br /><br />Description Resource Path Location Type<br />1046: Type was not found or was not a compile-time constant:<br />Matrix3D. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br />1046: Type was not found or was not a compile-time constant:<br />PerspectiveProjection. mediamanager Unknown Flex Problem<br /><br />Thanks, Brian<br /><br />________________________________<br />View/reply at using the SDK trunk <a href=http://www.adobeforums.com/webx?13@@.59b6b115><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6b115!folder=.3c060fa3> form to cancel your email subscription.
Participating Frequently
October 8, 2008
That did fix 4) for me. Thanks, Brian<br /><br />On Wed, Oct 8, 2008 at 1:20 PM, Haykel Ben Jemia <member@adobeforums.com> wrote:<br />> A new message was posted by Haykel Ben Jemia in<br />><br />> Developers --<br />> using the SDK trunk<br />><br />> I only know the answer for point 4: It has to do with the required flash<br />> player version, it has to be set to 10.0.0. For applications, you set it in<br />> the "Flex Compiler" page of the project properties, for libraries you have<br />> to edit the .actionScriptProperties file and set htmlPlayerVersion="10.0.0".<br />><br />> On Wed, Oct 8, 2008 at 5:26 PM, Brian Deitte <member@adobeforums.com> wrote:<br />>><br />>> A new discussion was started by Brian Deitte in<br />>><br />>> Developers --<br />>> using the SDK trunk<br />>><br />>> Hi all,<br />>><br />>> I was trying build a large project off of trunk, and I've run into a<br />>> few problems. I wanted to check out some of the compiler performance<br />>> improvements, but it's not critical that I run things off of trunk.<br />>> (I'll probably try to move a few to the Flex 3 branch instead.) But I<br />>> wanted to let you know about the issues I had, and see which ones of<br />>> them I should create bugs on.<br />>><br />>> 1. The first error I ran into when compiling was this:<br />>><br />>> [java] C:\perforce\trunk\ActionBar.mxml(109): Error: Access of<br />>> undefined property disabledIcon.<br />>> [java]<br />>> [java] disabledIcon="{itemRepeater.currentItem.disabledIcon}"<br />>> [java]<br />>> [java] C:\perforce\trunk\ActionBar.mxml(110): Error: Access of<br />>> undefined property overIcon.<br />>> [java]<br />>> [java] overIcon="{itemRepeater.currentItem.overIcon}"<br />>> [java]<br />>><br />>> I assume that currentItem was made non-dynamic, but I didn't look into<br />>> it. I just commented out the references to keep compiling.<br />>><br />>> 2. The second thing I ran into was the change of<br />>> "flex2.tools.Compiler" to "flex2.tools.Mxmlc". I can understand that<br />>> Mxmlc is clearer, but there's a lot of people who have the old name in<br />>> Ant files.<br />>><br />>> 3. The next compilation error:<br />>><br />>> [java] C:\perforce\trunk\LoginPanel.mxml(392): Error: Data<br />>> binding expressions not supported with attributes processed at compile<br />>> time.<br />>> [java]<br />>> [java] <mx:State name="{LOGIN_ERROR_STATE}"><br />>> [java]<br />>><br />>> We were using a const as a State name, which doesn't seem to be<br />>> allowed anymore. I put in the regular name, and everything compiled<br />>> fine at that point.<br />>><br />>> 4. When I then tried to compile in Flex Builder, I got the warnings<br />>> below. I assume this is because of a bad playglobal.swc reference?<br />>> Also, note that no line numbers are given. It drives me crazy when<br />>> Flex Builder does that. :)<br />>><br />>> Description Resource Path Location Type<br />>> 1046: Type was not found or was not a compile-time constant:<br />>> Matrix3D. mediamanager Unknown Flex Problem<br />>> 1046: Type was not found or was not a compile-time constant:<br />>> PerspectiveProjection. mediamanager Unknown Flex Problem<br />>> 1046: Type was not found or was not a compile-time constant:<br />>> PerspectiveProjection. mediamanager Unknown Flex Problem<br />>> 1046: Type was not found or was not a compile-time constant:<br />>> PerspectiveProjection. mediamanager Unknown Flex Problem<br />>><br />>> Thanks, Brian<br />>><br />>> ________________________________<br />>> View/reply at using the SDK trunk<br />>> Replies by email are OK.<br />>> Use the unsubscribe form to cancel your email subscription.<br />>><br />><br />><br />><br />> --<br />> Haykel Ben Jemia<br />><br />> Allmas<br />> Web & RIA Development<br />> http://www.allmas-tn.com<br />><br />><br />><br />><br />> ________________________________<br />> View/reply at using the SDK trunk<br />> Replies by email are OK.<br />> Use the unsubscribe form to cancel your email subscription.<br />><br />>
Known Participant
October 8, 2008
I only know the answer for point 4: It has to do with the required flash player version, it has to be set to 10.0.0. For applications, you set it in the "Flex Compiler" page of the project properties, for libraries you have to edit the .actionScriptProperties file and set htmlPlayerVersion="10.0.0".


On Wed, Oct 8, 2008 at 5:26 PM, Brian Deitte < member@adobeforums.com> wrote:

A new discussion was started by Brian Deitte in



Developers --

  using the SDK trunk



Hi all,

I was trying build a large project off of trunk, and I've run into a

few problems. I wanted to check out some of the compiler performance

improvements, but it's not critical that I run things off of trunk.

(I'll probably try to move a few to the Flex 3 branch instead.) But I

wanted to let you know about the issues I had, and see which ones of

them I should create bugs on.

1. The first error I ran into when compiling was this:

[java] C:\perforce\trunk\ActionBar.mxml(109): Error: Access of

undefined property disabledIcon.

    [java]

    [java] disabledIcon="{itemRepeater.currentItem.disabledIcon}"

    [java]

    [java] C:\perforce\trunk\ActionBar.mxml(110): Error: Access of

undefined property overIcon.

    [java]

    [java] overIcon="{itemRepeater.currentItem.overIcon}"

    [java]

I assume that currentItem was made non-dynamic, but I didn't look into

it. I just commented out the references to keep compiling.

2. The second thing I ran into was the change of

"flex2.tools.Compiler" to "flex2.tools.Mxmlc". I can understand that

Mxmlc is clearer, but there's a lot of people who have the old name in

Ant files.

3. The next compilation error:

[java] C:\perforce\trunk\LoginPanel.mxml(392): Error: Data

binding expressions not supported with attributes processed at compile

time.

    [java]

    [java] <mx:State name="{LOGIN_ERROR_STATE}">

    [java]

We were using a const as a State name, which doesn't seem to be

allowed anymore. I put in the regular name, and everything compiled

fine at that point.

4. When I then tried to compile in Flex Builder, I got the warnings

below. I assume this is because of a bad playglobal.swc reference?

Also, note that no line numbers are given. It drives me crazy when

Flex Builder does that. :)

Description Resource Path Location Type

1046: Type was not found or was not a compile-time constant:

Matrix3D. mediamanager Unknown Flex Problem

1046: Type was not found or was not a compile-time constant:

PerspectiveProjection. mediamanager Unknown Flex Problem

1046: Type was not found or was not a compile-time constant:

PerspectiveProjection. mediamanager Unknown Flex Problem

1046: Type was not found or was not a compile-time constant:

PerspectiveProjection. mediamanager Unknown Flex Problem

Thanks, Brian





View/reply at using the SDK trunk

Replies by email are OK.

Use the unsubscribe form to cancel your email subscription.





--
Haykel Ben Jemia

Allmas
Web & RIA Development
http://www.allmas-tn.com