What is the src (url) for that script?  Were there any errors loading and 
running it?  Are the other Royale packages/classes in the "window" object?

One scenario I thought of is that some bug or something else creates a "window" 
property at the global window causing our package lookup to be off.

HTH,
-Alex

On 5/6/20, 8:47 AM, "Yishay Weiss" <[email protected]> wrote:

    In my example <script> element is there but it’s never loaded on IE. I can 
confirm ModuleExamle works.
    
    From: Alex Harui<mailto:[email protected]>
    Sent: Sunday, May 3, 2020 9:31 AM
    To: [email protected]<mailto:[email protected]>
    Subject: Re: Modules in IE
    
    I just ran examples/royale/ModuleExample in IE and it worked.  Does it work 
for you?
    In the debugger, window.Module and window.MainApp resolve to functions.  
window.org is an object with an apache property.
    In the DOM Explorer, there should be tons of <script> tags in the head.  
Near the end of the list should be the script for the .js file for the module.
    Do you see any exceptions?  ModuleExample works without errors.
    
    -Alex
    
    On 5/2/20, 11:01 AM, "Yishay Weiss" <[email protected]> wrote:
    
        I suppose that’s what
    
        if (window[moduleName] == null) is checking
    
        The problem is that window[moduleName] never shows up. On Chrome it 
does.
    
        From: Alex Harui<mailto:[email protected]>
        Sent: Thursday, April 30, 2020 6:29 AM
        To: [email protected]<mailto:[email protected]>
        Subject: Re: Modules in IE
    
        Is this js-debug or js-release? Did the deps file load?  Did other 
definitions get created?  If js-debug, there should be new definitions showing 
up in the global/window object.  IOW, if the main app didn't have a DataGrid 
and the module did, the mx.controls.DataGrid should make an appearance as the 
deps are loaded and evaluated.
    
        -Alex
    
        On 4/29/20, 8:19 PM, "Yishay Weiss" <[email protected]> wrote:
    
            Yes, it works on Chrome and FF. window[this.modulename] is 
undefined. Didn’t check what happens in other browsers.
    
            From: Alex Harui<mailto:[email protected]>
            Sent: Thursday, April 30, 2020 12:00 AM
            To: [email protected]<mailto:[email protected]>
            Subject: Re: Modules in IE
    
            This is IE specific?  It works in other browers?  What does 
window[modulename] return?
    
            On 4/29/20, 1:41 PM, "Yishay Weiss" <[email protected]> wrote:
    
                Has anyone seen this work?
    
                To me it’s stuck in UIModuleUtils in
    
                        COMPILE::JS
                        protected function loadDepsHandler():void
                        {
                            // wait for other scripts to load
                            if (window[moduleName] == null)
                            {
                                setTimeout(loadDepsHandler, 250);
                            }
                            else
                                loadHandler();
    
                        }
                Window[moduleName] is never not null.
    
    
    
    
    
    
    
    
    
    

Reply via email to