«
»
05 10 2007

Move indeterminate

Posted by: Doug, in Flex, Flex SDK, Moxie

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:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
<mx:ProgressBar indeterminate="true"/>
</mx:Application>

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.

This entry was posted on Friday, October 5th, 2007 at 11:56 am and is filed under Flex, Flex SDK, Moxie. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
del.icio.us:Move indeterminate digg:Move indeterminate spurl:Move indeterminate wists:Move indeterminate simpy:Move indeterminate newsvine:Move indeterminate blinklist:Move indeterminate furl:Move indeterminate reddit:Move indeterminate fark:Move indeterminate blogmarks:Move indeterminate Y!:Move indeterminate smarking:Move indeterminate magnolia:Move indeterminate segnalo:Move indeterminate gifttagging:Move indeterminate

8 Responses to “Move indeterminate”

  1. Mitch says:
    October 5th, 2007 at 12:46 pm

    The one that got me was having an empty switch statement

    switch
    {
    }

    Woohoo. Internal error.
    That was fun to find.

  2. nicolas says:
    October 5th, 2007 at 1:18 pm

    yeah, upgrading ti beta 3 hasn’t been the most pleasant experience. Porting large css files is quite a bummer.

  3. polyGeek says:
    October 5th, 2007 at 1:51 pm

    Wow, the Framework developers use trace statements? Now I don’t feel like a total dunce. :-)

  4. Ben Throop says:
    November 13th, 2007 at 7:28 am

    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.

  5. Taylor says:
    November 13th, 2007 at 6:53 pm

    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…)

  6. Rostislav Siryk says:
    November 30th, 2007 at 6:48 am

    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 ;-)

  7. Rostislav Siryk says:
    November 30th, 2007 at 8:39 am

    A little addition to my prev comment: while this works, it makes the FB to slow down a bit during compile / search etc.

  8. Rostislav Siryk says:
    December 1st, 2007 at 10:52 am

    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.

Leave a Reply