Attachments may not work on this list.  Try posting a link to the files or
file a JIRA issue and put the files in there.

On 11/12/13 10:53 PM, "Devesh Mishra" <[email protected]> wrote:

>Hi Darrel,
>
>Good to listen from you. I have attached my action script sample class
>file in this email. Hope it'll give you a more clarification.
>
>Here are my explanation regarding your queries.
>
>1) I have written PopUpManager.centerPopUp() on ready event, because I
>want to display my popup only when my module get loads completely.
>Anyways i have already tried with something else i.e. I have tried, just
>after the initialization of popup window. But still getting same issue.
>
>2) Yes, I am using moduleLoader.addChild(child), after ready event.
>You'll get more clarification after looking into attached file.
>
>Note: Again repeating, this is happening with only one module. Apart from
>that, I have lots of module in my application and all are working fine.
>Module where I am getting this issue, it contains only one <mx:Module>
>and inside module tag, there is one <s:VGroup width="100%" height="100%"
>gap="10">
>
>That's it inside my module where I am getting error.
>
>
>-----Original Message-----
>From: Darrell Loverin [mailto:[email protected]]
>Sent: 12 November 2013 21:15
>To: [email protected]
>Subject: Re: One of the parameters is invalid while loading a module
>
>A couple of things seem odd to me:
>
>1) Why is PopUpManager:centerPopUp() being called on a "ready" event?
>
>  at mx.managers::PopUpManager$/centerPopUp()[E:\dev\4.x\
>frameworks\projects\framework\src\mx\managers\PopUpManager.as:213]
>        at flash.events::EventDispatcher/dispatchEventFunction()
>        at flash.events::EventDispatcher/dispatchEvent()
>        at mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\
>frameworks\projects\framework\src\mx\core\UIComponent.as:12528]
>        at mx.modules::ModuleLoader/moduleReadyHandler()[E:\dev\4.
>x\frameworks\projects\framework\src\mx\modules\ModuleLoader.as:462]
>
>2) Are you loading the module using _moduleLoader.addChild(child as
>DisplayObject)? The moduleLoader already adds the module as a child in its
>moduleReadyHandler.
>
>I'd be happy to look into the problem more if you have a simple project
>with a reproducible scenario.
>
>
>-Darrell
>
>
>
>On Mon, Nov 11, 2013 at 11:26 PM, Devesh Mishra
><[email protected]>wrote:
>
>> Hi Darrell,
>>
>> I am using a moduleloader to load module. You can find the code snippet
>> below. I am using moduleLoader.loadModule() method, not using
>>IModule.load()
>>
>> private function loadModule(moduleLoader:ModuleLoader):void
>> {
>>         moduleLoader.unloadModule();
>>
>> moduleLoader.addEventListener(ModuleEvent.READY,onModuleLoadHandler);
>>
>> moduleLoader.addEventListener(ModuleEvent.ERROR,onModuleLoadHandler);
>>
>> moduleLoader.addEventListener(ModuleEvent.SETUP,onModuleLoadHandler);
>>
>> moduleLoader.addEventListener(ModuleEvent.PROGRESS,onModuleLoadHandler);
>>
>> moduleLoader.addEventListener(ModuleEvent.UNLOAD,onModuleLoadHandler);
>>
>>
>>moduleLoader.addEventListener(IOErrorEvent.IO_ERROR,onModuleLoadHandler);
>>         moduleLoader.loadModule(_moduleUrl);
>> }
>>
>> private function onModuleLoadComplete(child:DisplayObject):void
>> {
>>         _moduleLoader.addChild(child as DisplayObject);
>> }
>>
>> -----Original Message-----
>> From: Darrell Loverin [mailto:[email protected]]
>> Sent: 11 November 2013 19:24
>> To: [email protected]
>> Subject: Re: One of the parameters is invalid while loading a module
>>
>> Setting -isolate-styles=false is not recommended when using Spark
>> components. Verify that your calls to IModule.load() are being passed a
>> module factory as the fourth parameter.
>>
>>
>> -Darrell Loverin
>>
>>
>> On Mon, Nov 11, 2013 at 3:15 AM, Devesh Mishra <[email protected]
>> >wrote:
>>
>> > Hi,
>> >
>> > I have lots of mxml modules (which is a combination of mxml & spark
>> > controls) in my application and the way i am opening these mxml
>>modules
>> is
>> > common in a popup window.
>> >
>> > It's very strange to see that i am getting this error with only one
>> > module. This issue is not related to a specific component.
>> >
>> > As it shows in error stack, i have removed panel from module, then it
>> > start throwing same error with some other components.
>> >
>> > -----Original Message-----
>> > From: Alex Harui [mailto:[email protected]]
>> > Sent: 11 November 2013 11:30
>> > To: Devesh Mishra; [email protected]
>> > Subject: Re: One of the parameters is invalid while loading a module
>> >
>> > Some folks on the forum said it worked for them.
>> >
>> > This error stack usually means an invalid value (usually NaN) is being
>> > passed to drawRect.  But a breakpoint on PanelAccImpl and see if you
>>can
>> > figure out why it is being passed a bad value.
>> >
>> > -Alex
>> >
>> > On 11/10/13 8:57 PM, "Devesh Mishra" <[email protected]> wrote:
>> >
>> > >Hi,
>> > >
>> > >I have tried that suggestion which is given in forum and it's working
>> for
>> > >me. I am getting below error stack.
>> > >
>> > >Just want to validate whether given suggestion is valid or not.
>> > >
>> > >ArgumentError: Error #2004: One of the parameters is invalid.
>> > >       at flash.display::Graphics/drawRect()
>> > >       at
>> >
>>
>>>spark.accessibility::PanelAccImpl/eventHandler()[E:\dev\4.x\frameworks\p
>>>ro
>> > >jects\spark\src\spark\accessibility\PanelAccImpl.as:361]
>> > >       at flash.events::EventDispatcher/dispatchEventFunction()
>> > >       at flash.events::EventDispatcher/dispatchEvent()
>> > >       at
>> >
>>
>>>mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\fram
>>>ew
>> > >ork\src\mx\core\UIComponent.as:12528]
>> > >       at
>> >
>>
>>>mx.core::UIComponent/dispatchResizeEvent()[E:\dev\4.x\frameworks\project
>>>s\
>> > >framework\src\mx\core\UIComponent.as:9844]
>> > >       at
>> >
>>
>>>mx.core::UIComponent/setActualSize()[E:\dev\4.x\frameworks\projects\fram
>>>ew
>> > >ork\src\mx\core\UIComponent.as:9358]
>> > >       at
>> >
>>
>>>mx.containers.utilityClasses::Flex$/flexChildHeightsProportionally()[E:\
>>>de
>> >
>>
>>>v\4.x\frameworks\projects\framework\src\mx\containers\utilityClasses\Fle
>>>x.
>> > >as:250]
>> > >       at
>> >
>>
>>>mx.containers.utilityClasses::BoxLayout/updateDisplayList()[E:\dev\4.x\f
>>>ra
>> >
>>
>>>meworks\projects\framework\src\mx\containers\utilityClasses\BoxLayout.as
>>>:2
>> > >61]
>> > >       at
>> >
>>
>>>mx.containers::Box/updateDisplayList()[E:\dev\4.x\frameworks\projects\fr
>>>am
>> > >ework\src\mx\containers\Box.as:413]
>> > >       at
>> >
>>
>>>mx.core::UIComponent/validateDisplayList()[E:\dev\4.x\frameworks\project
>>>s\
>> > >framework\src\mx\core\UIComponent.as:8709]
>> > >       at
>> >
>>
>>>mx.core::Container/validateDisplayList()[E:\dev\4.x\frameworks\projects\
>>>fr
>> > >amework\src\mx\core\Container.as:3296]
>> > >       at
>> >
>>
>>>mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projec
>>>ts
>> > >\framework\src\mx\managers\LayoutManager.as:932]
>> > >       at
>> >
>>
>>>mx.core::UIComponent/validateNow()[E:\dev\4.x\frameworks\projects\framew
>>>or
>> > >k\src\mx\core\UIComponent.as:7792]
>> > >       at
>> >
>>
>>>mx.managers::PopUpManagerImpl/centerPopUp()[E:\dev\4.x\frameworks\projec
>>>ts
>> > >\framework\src\mx\managers\PopUpManagerImpl.as:489]
>> > >       at
>> >
>>
>>>mx.managers::PopUpManager$/centerPopUp()[E:\dev\4.x\frameworks\projects\
>>>fr
>> > >amework\src\mx\managers\PopUpManager.as:213]
>> > >       at flash.events::EventDispatcher/dispatchEventFunction()
>> > >       at flash.events::EventDispatcher/dispatchEvent()
>> > >       at
>> >
>>
>>>mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\fram
>>>ew
>> > >ork\src\mx\core\UIComponent.as:12528]
>> > >       at
>> >
>>
>>>mx.modules::ModuleLoader/moduleReadyHandler()[E:\dev\4.x\frameworks\proj
>>>ec
>> > >ts\framework\src\mx\modules\ModuleLoader.as:462]
>> > >       at flash.events::EventDispatcher/dispatchEventFunction()
>> > >       at flash.events::EventDispatcher/dispatchEvent()
>> > >       at
>> >
>>
>>>ModuleInfoProxy/moduleEventHandler()[E:\dev\4.x\frameworks\projects\fram
>>>ew
>> > >ork\src\mx\modules\ModuleManager.as:1168]
>> > >       at flash.events::EventDispatcher/dispatchEventFunction()
>> > >       at flash.events::EventDispatcher/dispatchEvent()
>> > >       at
>> >
>>
>>>ModuleInfo/readyHandler()[E:\dev\4.x\frameworks\projects\framework\src\m
>>>x\
>> > >modules\ModuleManager.as:812]
>> > >       at flash.events::EventDispatcher/dispatchEventFunction()
>> > >       at flash.events::EventDispatcher/dispatchEvent()
>> > >       at
>> >
>>
>>>mx.core::FlexModuleFactory/update()[E:\dev\4.x\frameworks\projects\frame
>>>wo
>> > >rk\src\mx\core\FlexModuleFactory.as:433]
>> > >       at
>> >
>>
>>>mx.core::FlexModuleFactory/docFrameHandler()[E:\dev\4.x\frameworks\proje
>>>ct
>> > >s\framework\src\mx\core\FlexModuleFactory.as:582]
>> > >       at
>> >
>>
>>>mx.core::FlexModuleFactory/docFrameListener()[E:\dev\4.x\frameworks\proj
>>>ec
>> > >ts\framework\src\mx\core\FlexModuleFactory.as:126]
>> > >
>> > >-----Original Message-----
>> > >From: Alex Harui [mailto:[email protected]]
>> > >Sent: 08 November 2013 22:49
>> > >To: [email protected]
>> > >Subject: Re: One of the parameters is invalid while loading a module
>> > >
>> > >What is the error message and call stack?  Did you try the workaround
>> > >suggested in the forum thread?
>> > >
>> > >On 11/8/13 1:26 AM, "Devesh Mishra" <[email protected]> wrote:
>> > >
>> > >>Hi,
>> > >>I am facing the same issue which has been reported in the given URL
>> > >>(http://forums.adobe.com/message/2783233)
>> > >>In this post, someone mentioned that this issue is coming because of
>> > >>different implementation of StyleManager in Flex 3 & Flex 4.
>> > >>Need confirmation for the same.
>> > >>MASTEK LTD.
>> > >>In the US, we're called MAJESCOMASTEK
>> > >>
>> >
>>
>>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>~~
>> > >>~
>> > >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > >>Opinions expressed in this e-mail are those of the individual and
>>not
>> > >>that of Mastek Limited, unless specifically indicated to that
>>effect.
>> > >>Mastek Limited does not accept any responsibility or liability for
>>it.
>> > >>This e-mail and attachments (if any) transmitted with it are
>> confidential
>> > >>and/or privileged and solely for the use of the intended person or
>> entity
>> > >>to which it is addressed. Any review, re-transmission,
>>dissemination or
>> > >>other use of or taking of any action in reliance upon this
>>information
>> by
>> > >>persons or entities other than the intended recipient is prohibited.
>> This
>> > >>e-mail and its attachments have been scanned for the presence of
>> computer
>> > >>viruses. It is the responsibility of the recipient to run the virus
>> check
>> > >>on e-mails and attachments before opening them. If you have received
>> this
>> > >>e-mail in error, kindly delete this e-mail from desktop and server.
>> >
>>
>>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>~~
>> > >>~
>> > >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > >
>> > >MASTEK LTD.
>> > >In the US, we're called MAJESCOMASTEK
>> > >
>> >
>>
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>~~
>> > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > >Opinions expressed in this e-mail are those of the individual and not
>> > >that of Mastek Limited, unless specifically indicated to that effect.
>> > >Mastek Limited does not accept any responsibility or liability for
>>it.
>> > >This e-mail and attachments (if any) transmitted with it are
>> confidential
>> > >and/or privileged and solely for the use of the intended person or
>> entity
>> > >to which it is addressed. Any review, re-transmission, dissemination
>>or
>> > >other use of or taking of any action in reliance upon this
>>information
>> by
>> > >persons or entities other than the intended recipient is prohibited.
>> This
>> > >e-mail and its attachments have been scanned for the presence of
>> computer
>> > >viruses. It is the responsibility of the recipient to run the virus
>> check
>> > >on e-mails and attachments before opening them. If you have received
>> this
>> > >e-mail in error, kindly delete this e-mail from desktop and server.
>> >
>>
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>~~
>> > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > >
>> >
>> > MASTEK LTD.
>> > In the US, we're called MAJESCOMASTEK
>> >
>> >
>> >
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > Opinions expressed in this e-mail are those of the individual and not
>> that
>> > of Mastek Limited, unless specifically indicated to that effect.
>>Mastek
>> > Limited does not accept any responsibility or liability for it. This
>> e-mail
>> > and attachments (if any) transmitted with it are confidential and/or
>> > privileged and solely for the use of the intended person or entity to
>> which
>> > it is addressed. Any review, re-transmission, dissemination or other
>>use
>> of
>> > or taking of any action in reliance upon this information by persons
>>or
>> > entities other than the intended recipient is prohibited. This e-mail
>>and
>> > its attachments have been scanned for the presence of computer
>>viruses.
>> It
>> > is the responsibility of the recipient to run the virus check on
>>e-mails
>> > and attachments before opening them. If you have received this e-mail
>>in
>> > error, kindly delete this e-mail from desktop and server.
>> >
>> >
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >
>> >
>> MASTEK LTD.
>> In the US, we're called MAJESCOMASTEK
>>
>>
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Opinions expressed in this e-mail are those of the individual and not
>>that
>> of Mastek Limited, unless specifically indicated to that effect. Mastek
>> Limited does not accept any responsibility or liability for it. This
>>e-mail
>> and attachments (if any) transmitted with it are confidential and/or
>> privileged and solely for the use of the intended person or entity to
>>which
>> it is addressed. Any review, re-transmission, dissemination or other
>>use of
>> or taking of any action in reliance upon this information by persons or
>> entities other than the intended recipient is prohibited. This e-mail
>>and
>> its attachments have been scanned for the presence of computer viruses.
>>It
>> is the responsibility of the recipient to run the virus check on e-mails
>> and attachments before opening them. If you have received this e-mail in
>> error, kindly delete this e-mail from desktop and server.
>>
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>MASTEK LTD.
>In the US, we're called MAJESCOMASTEK
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Opinions expressed in this e-mail are those of the individual and not
>that of Mastek Limited, unless specifically indicated to that effect.
>Mastek Limited does not accept any responsibility or liability for it.
>This e-mail and attachments (if any) transmitted with it are confidential
>and/or privileged and solely for the use of the intended person or entity
>to which it is addressed. Any review, re-transmission, dissemination or
>other use of or taking of any action in reliance upon this information by
>persons or entities other than the intended recipient is prohibited. This
>e-mail and its attachments have been scanned for the presence of computer
>viruses. It is the responsibility of the recipient to run the virus check
>on e-mails and attachments before opening them. If you have received this
>e-mail in error, kindly delete this e-mail from desktop and server.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to