Hi Doug,

Thanks for digging into that.  We'll have to keep in mind the differences 
regarding includeInLayout in the emulation components.

-Alex

On 5/9/18, 2:12 AM, "doug777" <[email protected]> wrote:

    Hi Alex,
    
    I have finally found out what is really wrong in my code causing all these
    undefined errors.
    
    In old Flex, setting visible and includeInLayout to false prevents the
    object from appearing or having space allocated for it in the layout.
    
    In JS you only need to set visible to false to achieve the same thing.
    
    But there is another significant difference between the two. In old Flex the
    object will also not get built at all, but in JS it is built.
    
    This is what is causing all the problems. It's easy to fix and I've already
    done it.
    
    I'm not sure whether this also causes the Declarations to be undefined, but
    I can't check that out till I can get past another problem with
    RemoteObject.
    
    I have put that problem in a new thread.
    
    Doug
    
    
    
    --
    Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Ce8daa2f977854e7c8c4408d5b58cf012%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636614539306873909&sdata=ehlNBqpwFTqId5Vv9%2FmZUeQeE10xrQhpSgIRJhtEjWs%3D&reserved=0
    

Reply via email to