Function call sequence

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Function call sequence

Serkan Taş
Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

  •     in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"
  •     in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"


So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan

Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Alex Harui-2

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Sunday, November 24, 2019 at 9:21 AM
To: "[hidden email]" <[hidden email]>
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan

Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Serkan Taş
How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,
Serkan




On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Sunday, November 24, 2019 at 9:21 AM
To: "[hidden email]" <[hidden email]>
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan

Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Alex Harui-2

private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = new FileViewPopup();

                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.addPopUp(parentApplication as mx.core.IUIComponent, fileViewWindow, true);
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


 

From: Serkan Taş <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Sunday, November 24, 2019 at 9:23 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Function call sequence

 

How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,

Serkan

 



On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Sunday, November 24, 2019 at 9:21 AM
To: "[hidden email]" <[hidden email]>
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan

Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Serkan Taş
I got the exception below after changing code :




At the line :





25.11.2019 09:03 tarihinde Alex Harui yazdı:

private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = new FileViewPopup();

                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.addPopUp(parentApplication as mx.core.IUIComponent, fileViewWindow, true);
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:23 PM
To: [hidden email] [hidden email]
Subject: Re: Function call sequence

 

How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,

Serkan

 



On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:21 AM
To: [hidden email] [hidden email]
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan


Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Serkan Taş
popUpHost host is null

  var /** @type {org.apache.royale.core.IPopUpHost} */ popUpHost = org.apache.royale.utils.UIUtils.findPopUpHost(org.apache.royale.utils.Language.as(parent, org.apache.royale.core.IUIBase));

returns null

25.11.2019 09:14 tarihinde Serkan Taş yazdı:
I got the exception below after changing code :




At the line :





25.11.2019 09:03 tarihinde Alex Harui yazdı:

private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = new FileViewPopup();

                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.addPopUp(parentApplication as mx.core.IUIComponent, fileViewWindow, true);
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:23 PM
To: [hidden email] [hidden email]
Subject: Re: Function call sequence

 

How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,

Serkan

 



On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:21 AM
To: [hidden email] [hidden email]
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan



Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Alex Harui-2

Swap the order of args to addPopUp

 

From: Serkan Taş <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>, "[hidden email]" <[hidden email]>
Date: Sunday, November 24, 2019 at 10:18 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Function call sequence

 

popUpHost host is null

  var /** @type {org.apache.royale.core.IPopUpHost} */ popUpHost = org.apache.royale.utils.UIUtils.findPopUpHost(org.apache.royale.utils.Language.as(parent, org.apache.royale.core.IUIBase));

returns null

25.11.2019 09:14 tarihinde Serkan Taş yazdı:

I got the exception below after changing code :




At the line :




25.11.2019 09:03 tarihinde Alex Harui yazdı:

private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = new FileViewPopup();

                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.addPopUp(parentApplication as mx.core.IUIComponent, fileViewWindow, true);
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }



 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:23 PM
To: [hidden email] [hidden email]
Subject: Re: Function call sequence

 

How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,

Serkan

 




On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:21 AM
To: [hidden email] [hidden email]
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan

 



Reply | Threaded
Open this post in threaded view
|

Re: Function call sequence

Serkan Taş
Swapping the args worked also I tried another workaround.

Made initialization function public, removed it from "
creationComplete" and called manually after setting the arguments.

Thanks,
Serkan

25.11.2019 09:56 tarihinde Alex Harui yazdı:

Swap the order of args to addPopUp

 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email], [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 10:18 PM
To: [hidden email] [hidden email]
Subject: Re: Function call sequence

 

popUpHost host is null

  var /** @type {org.apache.royale.core.IPopUpHost} */ popUpHost = org.apache.royale.utils.UIUtils.findPopUpHost(org.apache.royale.utils.Language.as(parent, org.apache.royale.core.IUIBase));

returns null

25.11.2019 09:14 tarihinde Serkan Taş yazdı:

I got the exception below after changing code :




At the line :




25.11.2019 09:03 tarihinde Alex Harui yazdı:

private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = new FileViewPopup();

                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.addPopUp(parentApplication as mx.core.IUIComponent, fileViewWindow, true);
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }



 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:23 PM
To: [hidden email] [hidden email]
Subject: Re: Function call sequence

 

How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?

May be I am missing something, I will check.

Thanks,

Serkan

 




On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[hidden email]> wrote:

Royale will not guarantee the timing of Flex.  Flex didn’t really guarantee the timing of creationComplete either.  If your component forced a validateNow() the creationComplete would happen in the same place.

 

It is probably best to rewrite that to instantiate and call addPopUp after setting properties.

 

My 2 cents,

-Alex

 

From: Serkan Taş [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Sunday, November 24, 2019 at 9:21 AM
To: [hidden email] [hidden email]
Subject: Function call sequence

 

Hi,

In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation.

While debugging the code;


private function showGenericPopup(fileTag:String):void {
                var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;
                fileViewWindow.isNativeXML = true;
                fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id;
                PopUpManager.centerPopUp(fileViewWindow);
                fileViewWindow.setFocus();
            }


the function defined above is called,

·             in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);"

·             in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;"

 

So in royale some attributes are not yet set while the component is created.

What should be the right behavior ?

Is this a bug or new implementation is decided like above ?

How should I overcome this issue ?

Thanks,

Serkan