This is usually caused by a bug in the application (infinite loop, etc.).
Try turning off the preloader (set usePreloader=false on the Application
tag) and seeing what happens.
Jason
-Original Message-
From: Chris Phillips [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 29, 2005 3:17 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Refactored App, now: Initializing... THEN NO
THING...
BTW, I've done this with certain combinations of tags/containers. Just
goes to 100 and then sit's there stuck at 100 and not doing anything.
On Wed, 26 Jan 2005 11:50:51 -0500, Roger Gonzalez
[EMAIL PROTECTED] wrote:
Some things to try (I personally don't believe that it is the 32k issue):
- Toggle optimization
- Toggle the SWO cache
- Double check any static dependencies
- Turn on the compile report and check class deps
- Connect with the debugger to see where it is wedged.
When the progress bar finishes the initializing phase, does the dialog
disappear or does it hang at 100%? (It is waiting for the app to kill
it,
so its an interesting data point to see if it continues and wedges
elsewhere
or isn't getting removed.)
-Roger
Roger Gonzalez
mailto:[EMAIL PROTECTED]
-Original Message-
From: extensive_systems [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 9:35 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Refactored App, now:
Initializing... THEN NOTHING...
Ok, adding ?debug=true, refactoring again to make code smaller or
larger to get under/over (as per suggestions) a '32K Limit' does not
solve this tedious issue.
I find that (to cite one example of a few possible) if I leave the
following simple code inline (instead of refactoring it to its own
MXML file for modularity and further expansion as I certainly want to
do) then the app compiles, links and loads. But if I place it in its
own MXML file, and reference the nested component in standard fashion,
things don't work, as I've described.
mx:Tree
id=foobar width=100% height=70%
xmlns:xxx=xxx.*
xmlns:esf-view=com.extensivesystems.esf.view.*
xmlns:mx=http://www.macromedia.com/2003/mxml;
/mx:Tree
--- In flexcoders@yahoogroups.com, Tracy Spratt
[EMAIL PROTECTED] wrote:
You are probably on the edge of the 32k limit.
Add ?debug=true to your app url. Sometime that gets over
the hump, and
lets you run, sometimes it shows the error message.
I you can find out where the limit is being hit, either
make the code
smaller by more refactoring, or add some bogus code. It
appears that
there is some threshold where the 32k limit strikes, but
adding more
code causes flex to generate differently.
Large script blocks are a particular problem. Move them
into a class.
But try the more code route first.
Tracy
-Original Message-
From: extensive_systems [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 4:40 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Refactored App, now: Initializing... THEN
NOTHING...
Flex 1.5
Has anybody any insight into this issue that I've just
run into after
refactoring my app's MXML code?
When I run the app the Initializing progress bar shows
up, goes to
100% then... nothing - no sign of life, no message...
All I did was make some new components (i.e., cut MXML text from a
couple of files and created a few new MXML files, then
referred to the
components represented by the latter in the former. BTW,
I can make
the app fail as described in more than one way, so it
doesn't seem to
be just one bad snippet of code.
Yahoo! Groups Links
Yahoo! Groups Links
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
--
Chris Phillips
www.dealerpeak.com
Senior Application Developer
Yahoo! Groups Links
