Flex/Flash/Actionscript

Move indeterminate

Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate
Move indeterminate

A little jab at the Flex 3 SDK team. This is about a bug in the Flex 2 Beta 2 release. Looks like someone forgot to remove a trace statement. Woops.

If you want to get overwhelmed with “Move indeterminate” trace statements then debug this app in the latest Flex Builder:





 

This bug has been fixed, although not scheduled to be rolled out until next beta. I assume you can grab a nightly build and install a newer version of the SDK if you want to make these trace statements go away.

I’ll be bitching more fairly soon about some other pain points when upgrading an app from Flex 3 Beta 1 to Flex 3 Beta 2.

Related:

  • I want to start off with a quick recap of the current status of the bug I wrote about a few days ago. The Flex 3 Panel bug that resulted in the content of a Panel overlapping the title bar of the Panel has been fixed. The fix will be…
    Tags: flex, sdk
  • UPDATE: Well shit, turns out that posting the source of the almost-open-source-but-not-quite-yet Flex SDK is a no-no for now. I assume once the Flex 3 SDK officially goes open source this will be OK, but for now I've been asked by Adobe to take it down. As you say master.…
    Tags: sdk, flex
  • Tags: moxie, flex
Standard

8 thoughts on “Move indeterminate

  1. Are you guys taking the nightly SDK builds? I have run into a few off the wall bugs that seems to get fixed, but it seems like it might introduce even more randomness.

  2. UNIX to the rescue!

    ant run 2>&1 | grep -v “Move indeterminate”

    (Assumes you’re using ant to automate repetitive tasks. If not, just replace “ant run” with whatever you use to run your app…)

  3. There’s one more approach to get rid of “Move indeterminate” and other malevolent things like orphaned trace statements.

    – Add Flex SDK source to your project: Project Properties > Flex Build Path > Add Folder > C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\frameworks\projects\framework\src
    – Find in Files (Ctrl+Shift+F) > Move indeterminate.
    – Edit the wrong string in the source (in this case, line #1631 in the ProgressBar.as), save file and now it’s working fine.

    Doug, you’re the best. (the words I used to say in Russian too many times; now it’s the time to say it in English 😉

  4. Finally, you can then rebuild the framework.swc (to get rid of slowdown after including full framework source into your app’s source directories), but in Flex 3 Beta I could rebuild it with nearly 3 hours of magic passes. But succeeded at the end.

Comments are closed.