You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by mark goldin <ma...@gmail.com> on 2015/10/17 12:06:51 UTC
Speed up application start
I am converting modules into applications. An application file size is a
bit bigger than a module but the loading time is significantly longer. Any
tips to speed it up?
Thanks
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
On 10/19/15, 9:37 AM, "mark goldin" <ma...@gmail.com> wrote:
>Yes, exactly. But if I preload the shell and hide it how would it show a
>module that it is loading? I am definitely missing something here.
Yes, you are missing the fact that I am strongly suggesting that you do
not hide the shell. Or, if you strongly feel you must, as long as the
module generates child display objects parented by the shell, then making
the shell visible is the same as making the module visible.
-Alex
>
>On Mon, Oct 19, 2015 at 11:35 AM Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 10/19/15, 8:29 AM, "mark goldin" <ma...@gmail.com> wrote:
>>
>> ><Usually, the shell isn’t “hidden", the module just fully covers the
>> ><visible portion of the shell.
>> >But can I load the shell without showing it and pass a reference to it
>> >around to fire modules? And how will I make a module visible?
>>
>> IMO, you do not want to “not show" the shell, you simply want to the
>>shell
>> to show the module.
>>
>> -Alex
>>
>>
Re: Speed up application start
Posted by mark goldin <ma...@gmail.com>.
Yes, exactly. But if I preload the shell and hide it how would it show a
module that it is loading? I am definitely missing something here.
On Mon, Oct 19, 2015 at 11:35 AM Alex Harui <ah...@adobe.com> wrote:
>
>
> On 10/19/15, 8:29 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> ><Usually, the shell isn’t “hidden", the module just fully covers the
> ><visible portion of the shell.
> >But can I load the shell without showing it and pass a reference to it
> >around to fire modules? And how will I make a module visible?
>
> IMO, you do not want to “not show" the shell, you simply want to the shell
> to show the module.
>
> -Alex
>
>
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
On 10/19/15, 8:29 AM, "mark goldin" <ma...@gmail.com> wrote:
><Usually, the shell isn’t “hidden", the module just fully covers the
><visible portion of the shell.
>But can I load the shell without showing it and pass a reference to it
>around to fire modules? And how will I make a module visible?
IMO, you do not want to “not show" the shell, you simply want to the shell
to show the module.
-Alex
Re: Speed up application start
Posted by mark goldin <ma...@gmail.com>.
<Usually, the shell isn’t “hidden", the module just fully covers the
<visible portion of the shell.
But can I load the shell without showing it and pass a reference to it
around to fire modules? And how will I make a module visible?
On Mon, Oct 19, 2015 at 9:51 AM Alex Harui <ah...@adobe.com> wrote:
>
>
> On 10/19/15, 6:16 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >I am not sure I fully understand an idea with a small swf shell firing
> >Flex
> >modules. My main application page is an html page. So, I could load
> >shell's
> >swf as such:
> > swfobject.embedSWF("shell.swf", "mainDiv", "100%", "100%", "14.0.0",
> >"expressInstall.swf"). The shell swf can expose whatever public methods
> >are
> >needed to run modules. My question is how and what am I going to pass
> >around to load a specific module being selected from the main html menu?
> >Another thing is the the shell must be hidden.
>
> Usually, the shell isn’t “hidden", the module just fully covers the
> visible portion of the shell. The modules would use ExternalInterface
> probably as they do now to communicate with the HTML wrapper. The shell
> SWF would expose a callback via ExternalInterface like
> “loadThisModule(url:String)” that would replace all of the
> swfobject.embedSWF calls. IOW, instead of directing swfobject to load
> things, you would call into the shell SWF.
>
> HTH,
> -Alex
>
>
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
On 10/19/15, 6:16 AM, "mark goldin" <ma...@gmail.com> wrote:
>I am not sure I fully understand an idea with a small swf shell firing
>Flex
>modules. My main application page is an html page. So, I could load
>shell's
>swf as such:
> swfobject.embedSWF("shell.swf", "mainDiv", "100%", "100%", "14.0.0",
>"expressInstall.swf"). The shell swf can expose whatever public methods
>are
>needed to run modules. My question is how and what am I going to pass
>around to load a specific module being selected from the main html menu?
>Another thing is the the shell must be hidden.
Usually, the shell isn’t “hidden", the module just fully covers the
visible portion of the shell. The modules would use ExternalInterface
probably as they do now to communicate with the HTML wrapper. The shell
SWF would expose a callback via ExternalInterface like
“loadThisModule(url:String)” that would replace all of the
swfobject.embedSWF calls. IOW, instead of directing swfobject to load
things, you would call into the shell SWF.
HTH,
-Alex
Re: Speed up application start
Posted by mark goldin <ma...@gmail.com>.
I am not sure I fully understand an idea with a small swf shell firing Flex
modules. My main application page is an html page. So, I could load shell's
swf as such:
swfobject.embedSWF("shell.swf", "mainDiv", "100%", "100%", "14.0.0",
"expressInstall.swf"). The shell swf can expose whatever public methods are
needed to run modules. My question is how and what am I going to pass
around to load a specific module being selected from the main html menu?
Another thing is the the shell must be hidden.
On Mon, Oct 19, 2015 at 12:26 AM Alex Harui <ah...@adobe.com> wrote:
>
>
> On 10/18/15, 8:40 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >My setup is the following:
> >I have an html navigation bar across the screen. I am loading my Flex
> >application by selecting a menu on the bar. That will navigate to an html
> >wrapper that looks like this:
> ><html>
> ><body style="margin: 0px; overflow: auto;">
> ><div id="mainDiv" style="height: 100%; width: 100%; overflow: visible;">
> ></div>
> ><script type="text/javascript" src="swfobject.js"></script>
> > <script type="text/javascript">
> > swfobject.embedSWF("alarms.swf", "mainDiv", "100%", "100%",
> >"14.0.0", "expressInstall.swf", 'someparameters');
> ></script>
> ></body>
> ></html>
> >
> >So, what exactly can I improve?
>
> Hard to say. I think when you started on this path some of us wondered
> why you couldn’t use a shell SWF. Basically, by converting from Modules
> to Applications you have effectively converted from DLL’s to EXE’s if you
> are familiar with Windows. A Module/DLL is smaller and faster because it
> doesn’t have to create an entire process in the runtime. Of course,
> processes give you isolation better than Modules/DLLs, but you pay for the
> construction of that isolation.
>
> Using a shell SWF to load the other sub-application SWFs might help, but
> going back to loading module SWFs will still probably be more performant.
>
> -Alex
>
>
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
On 10/18/15, 8:40 AM, "mark goldin" <ma...@gmail.com> wrote:
>My setup is the following:
>I have an html navigation bar across the screen. I am loading my Flex
>application by selecting a menu on the bar. That will navigate to an html
>wrapper that looks like this:
><html>
><body style="margin: 0px; overflow: auto;">
><div id="mainDiv" style="height: 100%; width: 100%; overflow: visible;">
></div>
><script type="text/javascript" src="swfobject.js"></script>
> <script type="text/javascript">
> swfobject.embedSWF("alarms.swf", "mainDiv", "100%", "100%",
>"14.0.0", "expressInstall.swf", 'someparameters');
></script>
></body>
></html>
>
>So, what exactly can I improve?
Hard to say. I think when you started on this path some of us wondered
why you couldn’t use a shell SWF. Basically, by converting from Modules
to Applications you have effectively converted from DLL’s to EXE’s if you
are familiar with Windows. A Module/DLL is smaller and faster because it
doesn’t have to create an entire process in the runtime. Of course,
processes give you isolation better than Modules/DLLs, but you pay for the
construction of that isolation.
Using a shell SWF to load the other sub-application SWFs might help, but
going back to loading module SWFs will still probably be more performant.
-Alex
Re: Speed up application start
Posted by mark goldin <ma...@gmail.com>.
My setup is the following:
I have an html navigation bar across the screen. I am loading my Flex
application by selecting a menu on the bar. That will navigate to an html
wrapper that looks like this:
<html>
<body style="margin: 0px; overflow: auto;">
<div id="mainDiv" style="height: 100%; width: 100%; overflow: visible;">
</div>
<script type="text/javascript" src="swfobject.js"></script>
<script type="text/javascript">
swfobject.embedSWF("alarms.swf", "mainDiv", "100%", "100%",
"14.0.0", "expressInstall.swf", 'someparameters');
</script>
</body>
</html>
So, what exactly can I improve?
On Sun, Oct 18, 2015 at 9:40 AM Alex Harui <ah...@adobe.com> wrote:
> Yeah, so you are initializing new Flash Player instances each time instead
> of just loading a small SWF into an existing FP instance.
>
> -Alex
>
> On 10/18/15, 5:06 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >I am firing my applications by navigating to its html wrapper where I am
> >using SWFObject to load the app.
> >
> >On Sun, Oct 18, 2015 at 12:05 AM Alex Harui <ah...@adobe.com> wrote:
> >
> >> Are the applications being loaded as sub-applications of a “master” SWF,
> >> or are you changing what SWFObject loads in the HTML page? If the
> >>latter,
> >> you might be waiting on a re-start of the Flash Player.
> >>
> >> Try using a profiler to find out.
> >>
> >> -Alex
> >>
> >> On 10/17/15, 3:06 AM, "mark goldin" <ma...@gmail.com> wrote:
> >>
> >> >I am converting modules into applications. An application file size is
> >>a
> >> >bit bigger than a module but the loading time is significantly longer.
> >> >Any
> >> >tips to speed it up?
> >> >
> >> >Thanks
> >>
> >>
>
>
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
Yeah, so you are initializing new Flash Player instances each time instead
of just loading a small SWF into an existing FP instance.
-Alex
On 10/18/15, 5:06 AM, "mark goldin" <ma...@gmail.com> wrote:
>I am firing my applications by navigating to its html wrapper where I am
>using SWFObject to load the app.
>
>On Sun, Oct 18, 2015 at 12:05 AM Alex Harui <ah...@adobe.com> wrote:
>
>> Are the applications being loaded as sub-applications of a “master” SWF,
>> or are you changing what SWFObject loads in the HTML page? If the
>>latter,
>> you might be waiting on a re-start of the Flash Player.
>>
>> Try using a profiler to find out.
>>
>> -Alex
>>
>> On 10/17/15, 3:06 AM, "mark goldin" <ma...@gmail.com> wrote:
>>
>> >I am converting modules into applications. An application file size is
>>a
>> >bit bigger than a module but the loading time is significantly longer.
>> >Any
>> >tips to speed it up?
>> >
>> >Thanks
>>
>>
Re: Speed up application start
Posted by mark goldin <ma...@gmail.com>.
I am firing my applications by navigating to its html wrapper where I am
using SWFObject to load the app.
On Sun, Oct 18, 2015 at 12:05 AM Alex Harui <ah...@adobe.com> wrote:
> Are the applications being loaded as sub-applications of a “master” SWF,
> or are you changing what SWFObject loads in the HTML page? If the latter,
> you might be waiting on a re-start of the Flash Player.
>
> Try using a profiler to find out.
>
> -Alex
>
> On 10/17/15, 3:06 AM, "mark goldin" <ma...@gmail.com> wrote:
>
> >I am converting modules into applications. An application file size is a
> >bit bigger than a module but the loading time is significantly longer.
> >Any
> >tips to speed it up?
> >
> >Thanks
>
>
Re: Speed up application start
Posted by Alex Harui <ah...@adobe.com>.
Are the applications being loaded as sub-applications of a “master” SWF,
or are you changing what SWFObject loads in the HTML page? If the latter,
you might be waiting on a re-start of the Flash Player.
Try using a profiler to find out.
-Alex
On 10/17/15, 3:06 AM, "mark goldin" <ma...@gmail.com> wrote:
>I am converting modules into applications. An application file size is a
>bit bigger than a module but the loading time is significantly longer.
>Any
>tips to speed it up?
>
>Thanks
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
yes, my problem is solved:
- not set selected on the radiobutton
- in callout on creationcomplete set selectedindex on group
here is a test:
<fx:Declarations>
<s:RadioButtonGroup id="group0" />
<s:Callout id="callout" >
<s:HGroup>
<s:RadioButton groupName="group0"
label="yes"
value="0" />
<s:RadioButton id="btn1" groupName="group0"
label="no"
value="1"
selected="true"/>
<s:Button label="test"
click="trace(group0.selectedIndex)" />
</s:HGroup>
</s:Callout>
</fx:Declarations>
<s:VGroup id="vgroup" width="100%" height="100%">
<s:Button id="openBtn"
label="open"
click="callout.open(openBtn)" />
</s:VGroup>
Very strange: if you place e.g. a Label or other component after
openBtn, then it works
Am 20.10.2015 um 17:11 schrieb Alex Harui:
>
> On 10/20/15, 12:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>
>> but if it was the updateDisplayList function, shouldn't the traces then
>> be different?
> Ah, ok. I understand better now. I looked at RadioButtonGroup.as just
> now. There sure seems to be a lot of code running. Not sure why.
> Anyway, am I correct that you have solved your problem?
>
>> anyway, the 2nd button is selected while the groups selectedIndex
>> property is 0
>> isn't this a bug?
> IMO, yes. If you have a small test case, feel free to file a bug.
>
> -Alex
>
Re: radiobuttongroup selectedindex problem
Posted by Alex Harui <ah...@adobe.com>.
On 10/20/15, 12:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>but if it was the updateDisplayList function, shouldn't the traces then
>be different?
Ah, ok. I understand better now. I looked at RadioButtonGroup.as just
now. There sure seems to be a lot of code running. Not sure why.
Anyway, am I correct that you have solved your problem?
>anyway, the 2nd button is selected while the groups selectedIndex
>property is 0
>isn't this a bug?
IMO, yes. If you have a small test case, feel free to file a bug.
-Alex
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
but if it was the updateDisplayList function, shouldn't the traces then
be different?
anyway, the 2nd button is selected while the groups selectedIndex
property is 0
isn't this a bug?
Am 19.10.2015 um 17:02 schrieb Alex Harui:
> Well, if I understood what you are saying, it is that code in
> updateDisplayList because the selected property on the RadioButtons are
> affecting the results and that’s what that code does: it checks the
> selected property and alters the selection in the group.
>
> Callouts and other popups get initialized slightly differently than things
> in the main app (no phased instantiation) so that could be why this only
> happens in the callout.
>
> By not setting selected on any RadioButtons and only setting the group’s
> selectedIndex, the code in updateDisplayList probably has less effect.
>
> -Alex
>
> On 10/19/15, 1:29 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>
>> So, really weird (I'm still using Flex 4.12.1 !):
>> it is the callout
>> when you put radiobuttons in a callout the pre-selection gets messed up
>> what works is to set creationComplete="myGroup.selectedIndex=1"
>> in the callout but ONLY if the radiobutton is NOT set to selected="true"
>>
>> i think it's not the updateDisplayList function in radiobutton
>> I tested it like this:
>>
>> public class MRadioButton extends RadioButton
>> {
>>
>> public function MRadioButton()
>> {
>> super();
>> }
>>
>> override protected function
>> updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void
>> {
>> trace("before: " + this.group.selectedIndex);
>> super.updateDisplayList(unscaledWidth, unscaledHeight);
>> trace("after: " + this.group.selectedIndex);
>>
>> }
>>
>> }
>>
>> when the selection got messed up, both traces showed the same, wrong
>> index:0 (instead of 1)
>>
>>
>>
>>
>>
>>
>> Am 18.10.2015 um 22:53 schrieb Alex Harui:
>>> On 10/18/15, 10:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>>>
>>>> callLater doesn't help
>>>>
>>>> the radiobuttons of each group are in separate HGroups,
>>>> which are visible="false" and includeInLayout="false"
>>>> and can be shown by a checkbox
>>>>
>>>> may this cause this behaviour?
>>>> although I'm asking for the groups property which is set manually to
>>>> selectedIndex=1, as said,
>>>> not for the state of a button
>>>>
>>>> or more precise:
>>>> does changing the visibility and "layoutinclusion" of a radiobutton can
>>>> have an effect on the selectedIndex of the button's
>>>> group..........SOMETIMES?
>>>>
>>> I took a look at RadioButton. There is some strange code in its
>>> updateDisplayList method, so yes, flipping visibility could trigger an
>>> updateDisplayList and mess up selection. I suppose that changing
>>> visible
>>> and includeInLayout on the Hgroup could trigger updateDisplayList on the
>>> RadioButtons in certain scenarios, like if the browser is running the
>>> app
>>> at different sizes on the problem machines and scrollbars are being
>>> added/removed or the callout doesn’t display in its usual size and/or
>>> position.
>>>
>>> HTH,
>>> -Alex
>>>
Re: radiobuttongroup selectedindex problem
Posted by Alex Harui <ah...@adobe.com>.
Well, if I understood what you are saying, it is that code in
updateDisplayList because the selected property on the RadioButtons are
affecting the results and that’s what that code does: it checks the
selected property and alters the selection in the group.
Callouts and other popups get initialized slightly differently than things
in the main app (no phased instantiation) so that could be why this only
happens in the callout.
By not setting selected on any RadioButtons and only setting the group’s
selectedIndex, the code in updateDisplayList probably has less effect.
-Alex
On 10/19/15, 1:29 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>So, really weird (I'm still using Flex 4.12.1 !):
>it is the callout
>when you put radiobuttons in a callout the pre-selection gets messed up
>what works is to set creationComplete="myGroup.selectedIndex=1"
>in the callout but ONLY if the radiobutton is NOT set to selected="true"
>
>i think it's not the updateDisplayList function in radiobutton
>I tested it like this:
>
>public class MRadioButton extends RadioButton
> {
>
> public function MRadioButton()
> {
> super();
> }
>
> override protected function
>updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void
> {
> trace("before: " + this.group.selectedIndex);
> super.updateDisplayList(unscaledWidth, unscaledHeight);
> trace("after: " + this.group.selectedIndex);
>
> }
>
> }
>
>when the selection got messed up, both traces showed the same, wrong
>index:0 (instead of 1)
>
>
>
>
>
>
>Am 18.10.2015 um 22:53 schrieb Alex Harui:
>>
>> On 10/18/15, 10:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>>
>>> callLater doesn't help
>>>
>>> the radiobuttons of each group are in separate HGroups,
>>> which are visible="false" and includeInLayout="false"
>>> and can be shown by a checkbox
>>>
>>> may this cause this behaviour?
>>> although I'm asking for the groups property which is set manually to
>>> selectedIndex=1, as said,
>>> not for the state of a button
>>>
>>> or more precise:
>>> does changing the visibility and "layoutinclusion" of a radiobutton can
>>> have an effect on the selectedIndex of the button's
>>> group..........SOMETIMES?
>>>
>> I took a look at RadioButton. There is some strange code in its
>> updateDisplayList method, so yes, flipping visibility could trigger an
>> updateDisplayList and mess up selection. I suppose that changing
>>visible
>> and includeInLayout on the Hgroup could trigger updateDisplayList on the
>> RadioButtons in certain scenarios, like if the browser is running the
>>app
>> at different sizes on the problem machines and scrollbars are being
>> added/removed or the callout doesn’t display in its usual size and/or
>> position.
>>
>> HTH,
>> -Alex
>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
So, really weird (I'm still using Flex 4.12.1 !):
it is the callout
when you put radiobuttons in a callout the pre-selection gets messed up
what works is to set creationComplete="myGroup.selectedIndex=1"
in the callout but ONLY if the radiobutton is NOT set to selected="true"
i think it's not the updateDisplayList function in radiobutton
I tested it like this:
public class MRadioButton extends RadioButton
{
public function MRadioButton()
{
super();
}
override protected function
updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void
{
trace("before: " + this.group.selectedIndex);
super.updateDisplayList(unscaledWidth, unscaledHeight);
trace("after: " + this.group.selectedIndex);
}
}
when the selection got messed up, both traces showed the same, wrong
index:0 (instead of 1)
Am 18.10.2015 um 22:53 schrieb Alex Harui:
>
> On 10/18/15, 10:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>
>> callLater doesn't help
>>
>> the radiobuttons of each group are in separate HGroups,
>> which are visible="false" and includeInLayout="false"
>> and can be shown by a checkbox
>>
>> may this cause this behaviour?
>> although I'm asking for the groups property which is set manually to
>> selectedIndex=1, as said,
>> not for the state of a button
>>
>> or more precise:
>> does changing the visibility and "layoutinclusion" of a radiobutton can
>> have an effect on the selectedIndex of the button's
>> group..........SOMETIMES?
>>
> I took a look at RadioButton. There is some strange code in its
> updateDisplayList method, so yes, flipping visibility could trigger an
> updateDisplayList and mess up selection. I suppose that changing visible
> and includeInLayout on the Hgroup could trigger updateDisplayList on the
> RadioButtons in certain scenarios, like if the browser is running the app
> at different sizes on the problem machines and scrollbars are being
> added/removed or the callout doesn’t display in its usual size and/or
> position.
>
> HTH,
> -Alex
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
interesting, i will investigate this,
thanks
Am 18.10.2015 um 22:53 schrieb Alex Harui:
>
> On 10/18/15, 10:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>
>> callLater doesn't help
>>
>> the radiobuttons of each group are in separate HGroups,
>> which are visible="false" and includeInLayout="false"
>> and can be shown by a checkbox
>>
>> may this cause this behaviour?
>> although I'm asking for the groups property which is set manually to
>> selectedIndex=1, as said,
>> not for the state of a button
>>
>> or more precise:
>> does changing the visibility and "layoutinclusion" of a radiobutton can
>> have an effect on the selectedIndex of the button's
>> group..........SOMETIMES?
>>
> I took a look at RadioButton. There is some strange code in its
> updateDisplayList method, so yes, flipping visibility could trigger an
> updateDisplayList and mess up selection. I suppose that changing visible
> and includeInLayout on the Hgroup could trigger updateDisplayList on the
> RadioButtons in certain scenarios, like if the browser is running the app
> at different sizes on the problem machines and scrollbars are being
> added/removed or the callout doesn’t display in its usual size and/or
> position.
>
> HTH,
> -Alex
>
Re: radiobuttongroup selectedindex problem
Posted by Alex Harui <ah...@adobe.com>.
On 10/18/15, 10:26 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>callLater doesn't help
>
>the radiobuttons of each group are in separate HGroups,
>which are visible="false" and includeInLayout="false"
>and can be shown by a checkbox
>
>may this cause this behaviour?
>although I'm asking for the groups property which is set manually to
>selectedIndex=1, as said,
>not for the state of a button
>
>or more precise:
>does changing the visibility and "layoutinclusion" of a radiobutton can
>have an effect on the selectedIndex of the button's
>group..........SOMETIMES?
>
I took a look at RadioButton. There is some strange code in its
updateDisplayList method, so yes, flipping visibility could trigger an
updateDisplayList and mess up selection. I suppose that changing visible
and includeInLayout on the Hgroup could trigger updateDisplayList on the
RadioButtons in certain scenarios, like if the browser is running the app
at different sizes on the problem machines and scrollbars are being
added/removed or the callout doesn’t display in its usual size and/or
position.
HTH,
-Alex
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
callLater doesn't help
the radiobuttons of each group are in separate HGroups,
which are visible="false" and includeInLayout="false"
and can be shown by a checkbox
may this cause this behaviour?
although I'm asking for the groups property which is set manually to
selectedIndex=1, as said,
not for the state of a button
or more precise:
does changing the visibility and "layoutinclusion" of a radiobutton can
have an effect on the selectedIndex of the button's
group..........SOMETIMES?
Am 18.10.2015 um 16:58 schrieb Frank Dahmen:
> thanks, will try that
> I set both properties (now, before only selected on radio button)
>
>
> Am 18.10.2015 um 16:39 schrieb Alex Harui:
>> Are you initializing the selectedIndex on the group or a selected
>> property
>> on a radio button?
>>
>> I suppose there could be timing issues on when the group gets set up.
>> Adding a callLater in a creationComplete handler to further delay
>> setting
>> of selectedIndex on groups might help.
>>
>> HTH,
>> -Alex
>>
>> On 10/18/15, 5:48 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>>
>>> no, it's defintly wrong
>>> to let my colleague test on his computer (without debugger etc.), I
>>> made
>>> an alert
>>> in the function where the selectenindex is checked
>>>
>>> if(group0.selectedIndex==0){
>>> //normal code to do
>>> alert(this);
>>> }
>>> else{
>>> //normal code to do
>>> alert(that);
>>> }
>>>
>>> the really really weird thing is that the error appears to 1-5% on my
>>> computer and to maybe to 80% on my colleagues computer.
>>>
>>>
>>>
>>>
>>>
>>> Am 18.10.2015 um 14:33 schrieb Evyatar Ben Halevi-Arbib:
>>>> Could it be just some debugger mistake where it shows the wrong value
>>>> (which isn't real)?
>>>> If you print the value to a log file / console does it show the same
>>>> thing?
>>>>
>>>> In addition, you said you make the selection using two properties.
>>>> Have you tried using only one of them and see if the issue still
>>>> occur?
>>>>
>>>> On Sun, Oct 18, 2015 at 3:12 PM, Frank Dahmen <fr...@dahmenia.de>
>>>> wrote:
>>>>
>>>>> even worse, after adding creationcomplete, on the first run (on my
>>>>> computer) the error appears, on all runs (maybe 10-15)after that,
>>>>> it's
>>>>> working
>>>>> (I close the browser after a run)
>>>>>
>>>>> callout and radiogroups are in the <fx:Declaration> tag of the
>>>>> component,
>>>>> maybe this is wrong?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
>>>>>
>>>>>> thanks, i will try that,
>>>>>> .....but why does it not happen on my computer....weird..
>>>>>>
>>>>>> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>>>>>>
>>>>>>> If you think it is an initialization problem, you can try
>>>>>>> setting the
>>>>>>> initial values on the callout's creationComplete event.
>>>>>>>
>>>>>>> Good luck,
>>>>>>> Evyatar
>>>>>>>
>>>>>>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>>>>>>> wrote:
>>>>>>>
>>>>>>> forgot to say that this happens only when nothing is selected by
>>>>>>> the
>>>>>>> user
>>>>>>>> if he switches between the radiobuttons everything works
>>>>>>>>
>>>>>>>> there must be an issue with the initialization.....(on the other
>>>>>>>> computers!)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>>>>>>
>>>>>>>> In a callout i have several radiobuttongroups
>>>>>>>>> and a submit button
>>>>>>>>> when pressed a function is called which checks the
>>>>>>>>> selctedindex of
>>>>>>>>> all
>>>>>>>>> groups
>>>>>>>>>
>>>>>>>>> in the first group, the second radiobutton is selected
>>>>>>>>> (selected="true")
>>>>>>>>> and also the property of the first group is set
>>>>>>>>> (selectedindex="1")
>>>>>>>>>
>>>>>>>>> BUT:
>>>>>>>>> on 2 other computers than mine, the selectedindex of the first
>>>>>>>>> group
>>>>>>>>> is 0
>>>>>>>>> instead of 1
>>>>>>>>> on my computer it works?????????
>>>>>>>>>
>>>>>>>>> also, the error appears not always, sometimes it also works
>>>>>>>>> correct on
>>>>>>>>> the other 2 computers
>>>>>>>>>
>>>>>>>>> any help?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
thanks, will try that
I set both properties (now, before only selected on radio button)
Am 18.10.2015 um 16:39 schrieb Alex Harui:
> Are you initializing the selectedIndex on the group or a selected property
> on a radio button?
>
> I suppose there could be timing issues on when the group gets set up.
> Adding a callLater in a creationComplete handler to further delay setting
> of selectedIndex on groups might help.
>
> HTH,
> -Alex
>
> On 10/18/15, 5:48 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>
>> no, it's defintly wrong
>> to let my colleague test on his computer (without debugger etc.), I made
>> an alert
>> in the function where the selectenindex is checked
>>
>> if(group0.selectedIndex==0){
>> //normal code to do
>> alert(this);
>> }
>> else{
>> //normal code to do
>> alert(that);
>> }
>>
>> the really really weird thing is that the error appears to 1-5% on my
>> computer and to maybe to 80% on my colleagues computer.
>>
>>
>>
>>
>>
>> Am 18.10.2015 um 14:33 schrieb Evyatar Ben Halevi-Arbib:
>>> Could it be just some debugger mistake where it shows the wrong value
>>> (which isn't real)?
>>> If you print the value to a log file / console does it show the same
>>> thing?
>>>
>>> In addition, you said you make the selection using two properties.
>>> Have you tried using only one of them and see if the issue still occur?
>>>
>>> On Sun, Oct 18, 2015 at 3:12 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
>>>
>>>> even worse, after adding creationcomplete, on the first run (on my
>>>> computer) the error appears, on all runs (maybe 10-15)after that, it's
>>>> working
>>>> (I close the browser after a run)
>>>>
>>>> callout and radiogroups are in the <fx:Declaration> tag of the
>>>> component,
>>>> maybe this is wrong?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
>>>>
>>>>> thanks, i will try that,
>>>>> .....but why does it not happen on my computer....weird..
>>>>>
>>>>> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>>>>>
>>>>>> If you think it is an initialization problem, you can try setting the
>>>>>> initial values on the callout's creationComplete event.
>>>>>>
>>>>>> Good luck,
>>>>>> Evyatar
>>>>>>
>>>>>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>>>>>> wrote:
>>>>>>
>>>>>> forgot to say that this happens only when nothing is selected by the
>>>>>> user
>>>>>>> if he switches between the radiobuttons everything works
>>>>>>>
>>>>>>> there must be an issue with the initialization.....(on the other
>>>>>>> computers!)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>>>>>
>>>>>>> In a callout i have several radiobuttongroups
>>>>>>>> and a submit button
>>>>>>>> when pressed a function is called which checks the selctedindex of
>>>>>>>> all
>>>>>>>> groups
>>>>>>>>
>>>>>>>> in the first group, the second radiobutton is selected
>>>>>>>> (selected="true")
>>>>>>>> and also the property of the first group is set (selectedindex="1")
>>>>>>>>
>>>>>>>> BUT:
>>>>>>>> on 2 other computers than mine, the selectedindex of the first
>>>>>>>> group
>>>>>>>> is 0
>>>>>>>> instead of 1
>>>>>>>> on my computer it works?????????
>>>>>>>>
>>>>>>>> also, the error appears not always, sometimes it also works
>>>>>>>> correct on
>>>>>>>> the other 2 computers
>>>>>>>>
>>>>>>>> any help?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
Re: radiobuttongroup selectedindex problem
Posted by Alex Harui <ah...@adobe.com>.
Are you initializing the selectedIndex on the group or a selected property
on a radio button?
I suppose there could be timing issues on when the group gets set up.
Adding a callLater in a creationComplete handler to further delay setting
of selectedIndex on groups might help.
HTH,
-Alex
On 10/18/15, 5:48 AM, "Frank Dahmen" <fr...@dahmenia.de> wrote:
>no, it's defintly wrong
>to let my colleague test on his computer (without debugger etc.), I made
>an alert
>in the function where the selectenindex is checked
>
>if(group0.selectedIndex==0){
> //normal code to do
> alert(this);
>}
>else{
> //normal code to do
> alert(that);
>}
>
>the really really weird thing is that the error appears to 1-5% on my
>computer and to maybe to 80% on my colleagues computer.
>
>
>
>
>
>Am 18.10.2015 um 14:33 schrieb Evyatar Ben Halevi-Arbib:
>> Could it be just some debugger mistake where it shows the wrong value
>> (which isn't real)?
>> If you print the value to a log file / console does it show the same
>>thing?
>>
>> In addition, you said you make the selection using two properties.
>> Have you tried using only one of them and see if the issue still occur?
>>
>> On Sun, Oct 18, 2015 at 3:12 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
>>
>>> even worse, after adding creationcomplete, on the first run (on my
>>> computer) the error appears, on all runs (maybe 10-15)after that, it's
>>> working
>>> (I close the browser after a run)
>>>
>>> callout and radiogroups are in the <fx:Declaration> tag of the
>>>component,
>>> maybe this is wrong?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
>>>
>>>> thanks, i will try that,
>>>> .....but why does it not happen on my computer....weird..
>>>>
>>>> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>>>>
>>>>> If you think it is an initialization problem, you can try setting the
>>>>> initial values on the callout's creationComplete event.
>>>>>
>>>>> Good luck,
>>>>> Evyatar
>>>>>
>>>>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>>>>> wrote:
>>>>>
>>>>> forgot to say that this happens only when nothing is selected by the
>>>>>user
>>>>>> if he switches between the radiobuttons everything works
>>>>>>
>>>>>> there must be an issue with the initialization.....(on the other
>>>>>> computers!)
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>>>>
>>>>>> In a callout i have several radiobuttongroups
>>>>>>> and a submit button
>>>>>>> when pressed a function is called which checks the selctedindex of
>>>>>>>all
>>>>>>> groups
>>>>>>>
>>>>>>> in the first group, the second radiobutton is selected
>>>>>>> (selected="true")
>>>>>>> and also the property of the first group is set (selectedindex="1")
>>>>>>>
>>>>>>> BUT:
>>>>>>> on 2 other computers than mine, the selectedindex of the first
>>>>>>>group
>>>>>>> is 0
>>>>>>> instead of 1
>>>>>>> on my computer it works?????????
>>>>>>>
>>>>>>> also, the error appears not always, sometimes it also works
>>>>>>>correct on
>>>>>>> the other 2 computers
>>>>>>>
>>>>>>> any help?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
no, it's defintly wrong
to let my colleague test on his computer (without debugger etc.), I made
an alert
in the function where the selectenindex is checked
if(group0.selectedIndex==0){
//normal code to do
alert(this);
}
else{
//normal code to do
alert(that);
}
the really really weird thing is that the error appears to 1-5% on my
computer and to maybe to 80% on my colleagues computer.
Am 18.10.2015 um 14:33 schrieb Evyatar Ben Halevi-Arbib:
> Could it be just some debugger mistake where it shows the wrong value
> (which isn't real)?
> If you print the value to a log file / console does it show the same thing?
>
> In addition, you said you make the selection using two properties.
> Have you tried using only one of them and see if the issue still occur?
>
> On Sun, Oct 18, 2015 at 3:12 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
>
>> even worse, after adding creationcomplete, on the first run (on my
>> computer) the error appears, on all runs (maybe 10-15)after that, it's
>> working
>> (I close the browser after a run)
>>
>> callout and radiogroups are in the <fx:Declaration> tag of the component,
>> maybe this is wrong?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
>>
>>> thanks, i will try that,
>>> .....but why does it not happen on my computer....weird..
>>>
>>> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>>>
>>>> If you think it is an initialization problem, you can try setting the
>>>> initial values on the callout's creationComplete event.
>>>>
>>>> Good luck,
>>>> Evyatar
>>>>
>>>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>>>> wrote:
>>>>
>>>> forgot to say that this happens only when nothing is selected by the user
>>>>> if he switches between the radiobuttons everything works
>>>>>
>>>>> there must be an issue with the initialization.....(on the other
>>>>> computers!)
>>>>>
>>>>>
>>>>>
>>>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>>>
>>>>> In a callout i have several radiobuttongroups
>>>>>> and a submit button
>>>>>> when pressed a function is called which checks the selctedindex of all
>>>>>> groups
>>>>>>
>>>>>> in the first group, the second radiobutton is selected
>>>>>> (selected="true")
>>>>>> and also the property of the first group is set (selectedindex="1")
>>>>>>
>>>>>> BUT:
>>>>>> on 2 other computers than mine, the selectedindex of the first group
>>>>>> is 0
>>>>>> instead of 1
>>>>>> on my computer it works?????????
>>>>>>
>>>>>> also, the error appears not always, sometimes it also works correct on
>>>>>> the other 2 computers
>>>>>>
>>>>>> any help?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
Re: radiobuttongroup selectedindex problem
Posted by Evyatar Ben Halevi-Arbib <ev...@gmail.com>.
Could it be just some debugger mistake where it shows the wrong value
(which isn't real)?
If you print the value to a log file / console does it show the same thing?
In addition, you said you make the selection using two properties.
Have you tried using only one of them and see if the issue still occur?
On Sun, Oct 18, 2015 at 3:12 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
> even worse, after adding creationcomplete, on the first run (on my
> computer) the error appears, on all runs (maybe 10-15)after that, it's
> working
> (I close the browser after a run)
>
> callout and radiogroups are in the <fx:Declaration> tag of the component,
> maybe this is wrong?
>
>
>
>
>
>
>
>
>
> Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
>
>> thanks, i will try that,
>> .....but why does it not happen on my computer....weird..
>>
>> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>>
>>> If you think it is an initialization problem, you can try setting the
>>> initial values on the callout's creationComplete event.
>>>
>>> Good luck,
>>> Evyatar
>>>
>>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>>> wrote:
>>>
>>> forgot to say that this happens only when nothing is selected by the user
>>>> if he switches between the radiobuttons everything works
>>>>
>>>> there must be an issue with the initialization.....(on the other
>>>> computers!)
>>>>
>>>>
>>>>
>>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>>
>>>> In a callout i have several radiobuttongroups
>>>>> and a submit button
>>>>> when pressed a function is called which checks the selctedindex of all
>>>>> groups
>>>>>
>>>>> in the first group, the second radiobutton is selected
>>>>> (selected="true")
>>>>> and also the property of the first group is set (selectedindex="1")
>>>>>
>>>>> BUT:
>>>>> on 2 other computers than mine, the selectedindex of the first group
>>>>> is 0
>>>>> instead of 1
>>>>> on my computer it works?????????
>>>>>
>>>>> also, the error appears not always, sometimes it also works correct on
>>>>> the other 2 computers
>>>>>
>>>>> any help?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
even worse, after adding creationcomplete, on the first run (on my
computer) the error appears, on all runs (maybe 10-15)after that, it's
working
(I close the browser after a run)
callout and radiogroups are in the <fx:Declaration> tag of the component,
maybe this is wrong?
Am 18.10.2015 um 12:10 schrieb Frank Dahmen:
> thanks, i will try that,
> .....but why does it not happen on my computer....weird..
>
> Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
>> If you think it is an initialization problem, you can try setting the
>> initial values on the callout's creationComplete event.
>>
>> Good luck,
>> Evyatar
>>
>> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de>
>> wrote:
>>
>>> forgot to say that this happens only when nothing is selected by the
>>> user
>>> if he switches between the radiobuttons everything works
>>>
>>> there must be an issue with the initialization.....(on the other
>>> computers!)
>>>
>>>
>>>
>>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>>
>>>> In a callout i have several radiobuttongroups
>>>> and a submit button
>>>> when pressed a function is called which checks the selctedindex of all
>>>> groups
>>>>
>>>> in the first group, the second radiobutton is selected
>>>> (selected="true")
>>>> and also the property of the first group is set (selectedindex="1")
>>>>
>>>> BUT:
>>>> on 2 other computers than mine, the selectedindex of the first
>>>> group is 0
>>>> instead of 1
>>>> on my computer it works?????????
>>>>
>>>> also, the error appears not always, sometimes it also works correct on
>>>> the other 2 computers
>>>>
>>>> any help?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
thanks, i will try that,
.....but why does it not happen on my computer....weird..
Am 18.10.2015 um 12:03 schrieb Evyatar Ben Halevi-Arbib:
> If you think it is an initialization problem, you can try setting the
> initial values on the callout's creationComplete event.
>
> Good luck,
> Evyatar
>
> On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
>
>> forgot to say that this happens only when nothing is selected by the user
>> if he switches between the radiobuttons everything works
>>
>> there must be an issue with the initialization.....(on the other
>> computers!)
>>
>>
>>
>> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>>
>>> In a callout i have several radiobuttongroups
>>> and a submit button
>>> when pressed a function is called which checks the selctedindex of all
>>> groups
>>>
>>> in the first group, the second radiobutton is selected (selected="true")
>>> and also the property of the first group is set (selectedindex="1")
>>>
>>> BUT:
>>> on 2 other computers than mine, the selectedindex of the first group is 0
>>> instead of 1
>>> on my computer it works?????????
>>>
>>> also, the error appears not always, sometimes it also works correct on
>>> the other 2 computers
>>>
>>> any help?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
Re: radiobuttongroup selectedindex problem
Posted by Evyatar Ben Halevi-Arbib <ev...@gmail.com>.
If you think it is an initialization problem, you can try setting the
initial values on the callout's creationComplete event.
Good luck,
Evyatar
On Sun, Oct 18, 2015 at 12:57 PM, Frank Dahmen <fr...@dahmenia.de> wrote:
> forgot to say that this happens only when nothing is selected by the user
> if he switches between the radiobuttons everything works
>
> there must be an issue with the initialization.....(on the other
> computers!)
>
>
>
> Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
>
>> In a callout i have several radiobuttongroups
>> and a submit button
>> when pressed a function is called which checks the selctedindex of all
>> groups
>>
>> in the first group, the second radiobutton is selected (selected="true")
>> and also the property of the first group is set (selectedindex="1")
>>
>> BUT:
>> on 2 other computers than mine, the selectedindex of the first group is 0
>> instead of 1
>> on my computer it works?????????
>>
>> also, the error appears not always, sometimes it also works correct on
>> the other 2 computers
>>
>> any help?
>>
>>
>>
>>
>>
>>
>>
>
Re: radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
forgot to say that this happens only when nothing is selected by the user
if he switches between the radiobuttons everything works
there must be an issue with the initialization.....(on the other computers!)
Am 18.10.2015 um 11:27 schrieb Frank Dahmen:
> In a callout i have several radiobuttongroups
> and a submit button
> when pressed a function is called which checks the selctedindex of all
> groups
>
> in the first group, the second radiobutton is selected (selected="true")
> and also the property of the first group is set (selectedindex="1")
>
> BUT:
> on 2 other computers than mine, the selectedindex of the first group
> is 0 instead of 1
> on my computer it works?????????
>
> also, the error appears not always, sometimes it also works correct on
> the other 2 computers
>
> any help?
>
>
>
>
>
>
radiobuttongroup selectedindex problem
Posted by Frank Dahmen <fr...@dahmenia.de>.
In a callout i have several radiobuttongroups
and a submit button
when pressed a function is called which checks the selctedindex of all
groups
in the first group, the second radiobutton is selected (selected="true")
and also the property of the first group is set (selectedindex="1")
BUT:
on 2 other computers than mine, the selectedindex of the first group is
0 instead of 1
on my computer it works?????????
also, the error appears not always, sometimes it also works correct on
the other 2 computers
any help?