|
Well, rats. Thanks guys. Since this particular
app is so unusual, and moving this process to the server is on the “roadmap”,
this particular client (me too, I guess) will either need to keep the
development machine on FP7, or deal with the 2-3 timeout prompts. I am already using the state variable /
doLater strategy to give the user some feedback, but apparently a few of the
200 steps are still too big. Thanks again. From: OK, bad news. I went searching
through the bugbase and found one for our docs team to add to the migration
guide that the timeout can no longer be greater than 60 seconds.
I’m assuming that this was actually put into Player 8, not just 8.5 since
you’re running into it. Guess that means you’re going to need
to do some tricks like Jesse showed, and in your case since you’re
building a massive tree I think this means you’re going to need to
basically -
build
some nodes -
store temporary
state to instance variables -
call
doLater using your main function (you can pass parameters to doLater too) -
at some
point your method executes the last time and you don’t need to doLater
anymore you can put up a blocker and show the busy
cursor while you’re doing this too (though using a progress bar might be
nicer) Matt From: I got the latest from the MM site and it
did not respect my settings. From: Just realized that the script timeout popup is not showing on the
regular Flash Player 8 (i.e non -debug version). Of course I tested this on another pc, so it could be that machine is
faster ...though unlikely.... - superabe On 11/1/05, Yes, I really need this. Jesse, if you are still following this thread: Besides moving
my entire process to the server(which would take me several weeks, and this is
a rare condition that only a developer will see), is there anyway to
"refactor" a single process? The is the massive calculation
(in this case it is building two 30,000 node trees) that made me implement your
status variable and doLater strategy in order to give the user some visible
feedback while this process is running. It is broken up into individual
function calls, but it still triggers the time-out. From: [email protected]
[mailto:[email protected]]
On Behalf Of superabe superabe I do hope
to refactor and optimize the code eventually, but I think the option
to override the default time limit of 60 seconds for your
script should be made available. -
superabe
On
10/31/05, JesterXL <
[EMAIL PROTECTED]> wrote: I
never knew it was an issue. Incidentally,
I think that is one of the worst features Macromedia could of implemented in
Flex, although, I understand why they did it. My
opinion; if you are using that attribute of the application tag, it's time to
refactor whatever part of your code requires it. -----
Original Message ----- From: superabe
superabe Sent: Monday, October 31, 2005 10:36 AM Subject: [flexcoders] script time warning
and Flash Player 8
Hello
list, resending
this, hoping somebody has an answer. The
scriptTimeOut property for the application tag does not seem to be -- YAHOO! GROUPS
LINKS
SPONSORED
LINKS
YAHOO!
GROUPS LINKS
|
