Well I had to throw in my own loading flags so its done now.
You'll understand that I'm not happy that you had to do this. There has been no feedback on the forums indicating the sort of problem that you have had. Could you help me out by answering some questions?
What version of StartupManager swc are you using?
Since
both resources are getting managed and loaded
, I presume the utility is processing the second loaded notification. When is the loading complete being sent? Do you mean after the first loaded notification is sent by your app and before the second loaded notification is sent by your app?
An important point is whether your observance of the sequence of notification sending is based on the handling of notifications in a mediator. See this topic regarding the sequence of processing of a "data loaded" notification.
http://forums.puremvc.org/index.php?topic=1049.msg4816#msg4816If there is any of your app code that you could send me, or post here, that might enable me to reproduce or diagnose your problem, that would be great.
As regards non-recognition of setTimeout(), this could be a misunderstanding of versions and API; there was a timeout property (public access) in StartupResourceProxy pre v1.3, replaced by a retryPolicy property in versions 1.3 and following. V1.3 was released 21-May-2008.
----Philip