[flexcoders] HDividedBox divider events not working after changing current state
The HDividerBox dividerRelease and dividerPress event listeners no longer execute after changing the current state of a parent container (and the 'drag handle' is lost)...but the HDividedBox still 'has event listeners' for these events. Any ideas? I'll post code if necessary. Thanks.
Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
I would encode the commas as well.
Another test would be to simply pass in “foo” instead of “status...” to see if
it is something in that string that is causing the problem.
On 7/9/12 9:41 AM, "michael_reg...@dell.com" wrote:
Changing the function use encoding (%3D in place of the =) causes the function
to completely fail. I guess I can chalk this one up as an Adobe bug overall?
ExternalInterface.call("window.open",urlString,"_blank","status%3D1,scrollbars%3D1,toolbar%3D1,menubar%3D1,location%3D1,resizable%3D1");
Michael J. Regert
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf
Of Alex ! Harui
Sent: Saturday, July 07, 2012 11:46 PM
T! o: f lexcod...@yahoogroups.com
Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
I’m just guessing here, but I get suspicious when I see non-alphas (equal
signs, dashes) in a URL. See this link:
http://www.w3schools.com/tags/ref_urlencode.asp
On 7/6/12 6:22 AM, "michael_reg...@dell.com" wrote:
Thank you Alex for your reply. Can you further clarify what you mean by “try
encodin! g entities in the urlString and maybe the additional args”. I guess
I’m not understanding. The URLString I’m passing in is like
https://hostname/resources/locale/en_US/help/GUID-1234567890.html and the args
I’m passing are shown below… How do I encode them?
Michael J. Regert
Please consider the environment before printing this email.
Confidentiality Notice | This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, immediately
contact the sender by reply e-mail and destroy all copie! s of the original
message.
From: flexcode! rs@yahoo groups.com [mailto:flexcoders@yahoogroups.com] On
Behalf Of Alex Harui
Sent: Thursday, July 05, 2012 11:18 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
It appears that ExternalInterface.call takes its arguments and encodes them
into XML before passing them to the HTML/JS wrapper. If there is something in
the arguments that messes up the encoding then maybe you would get this error.
I would try encoding entities in the urlString and maybe the additional args.
On 7/5/12 12:46 PM, "mich! ael_reg...@dell.com "
wrote:
I'm working on a bug which has us puzzled and I'm looking for a bit of
direction. When we launch our external help documents (HTML) with the
following command, sometimes we get an array of XML parse errors. It is very
inconsistent and sometimes requires clicking the help button multiple times
before it appears. I cannot step into the ExternalInterface code to see what
it is failing on. The help page DOES launch correctly, so I know the URL is
fine. But when I close the HTML page, I get an error sometimes. The error is
not consistent either. Any pointers on how to debug this? Is the XML it is
trying to parse the actual HTML? I would think that Flex would just open a
browser window, ignoring the content. We're using Flex 4.0 SDK.
We're calling:
&! nbsp;ExternalInterface.call("window.open",urlStri! n! g,"
_blank","status=1,scrollbars=1,toolbar=1,me! nubar=1, location=1,resizable=1");
Errors seen include:
TypeError: Error #1090: XML parser failure: element is malformed.
at flash.external::ExternalInterface$/call()
TypeError: Error #1095: XML parser failure: Unterminated attribute.
at flash.external::ExternalInterface$/call()
Error: Error #1502: A script has executed for longer than the default timeout
period of 15 seconds.
at flash.external::ExternalInterface$/_argumentsToXML()
at flash.external::ExternalInterface$/call()
- Michael J. Regert
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
Ignore me. Those got introduced halfway down the discussion, with the message
from Alex Harui.
Sorry,
E
On Jul 9, 2012, at 4:29 PM, Erik van der Neut wrote:
> Oh, also seeing "urlStri! ng" -- must be something else then...?
>
> E
>
>
> On Jul 9, 2012, at 4:28 PM, Erik van der Neut wrote:
>
>>
>> In your original message you wrote:
>>
>> me! nubar=1
>>
>> Instead of:
>>
>> menubar=1
>>
>> I assume that was a typo in your message to this group, not in your actual
>> code?
>>
>> Erik
>>
>>
>>
>> On Jul 9, 2012, at 12:41 PM,
>> wrote:
>>
>>>
>>> Changing the function use encoding (%3D in place of the =) causes the
>>> function to completely fail. I guess I can chalk this one up as an Adobe
>>> bug overall?
>>>
>>>
>>>
>>> ExternalInterface.call("window.open",urlString,"_blank","status%3D1,scrollbars%3D1,toolbar%3D1,menubar%3D1,location%3D1,resizable%3D1");
>>>
>>>
>>>
>>>
>>>
>>> Michael J. Regert
>>>
>>>
>>>
>>> From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On
>>> Behalf Of Alex Harui
>>> Sent: Saturday, July 07, 2012 11:46 PM
>>> To: flexcoders@yahoogroups.com
>>> Subject: Re: [flexcoders] Errors in
>>> flash.external::ExternalInterface$/call()
>>>
>>>
>>>
>>>
>>>
>>> I’m just guessing here, but I get suspicious when I see non-alphas (equal
>>> signs, dashes) in a URL. See this link:
>>> http://www.w3schools.com/tags/ref_urlencode.asp
>>>
>>>
>>> On 7/6/12 6:22 AM, "michael_reg...@dell.com"
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thank you Alex for your reply. Can you further clarify what you mean by
>>> “try encoding entities in the urlString and maybe the additional args”. I
>>> guess I’m not understanding. The URLString I’m passing in is like
>>> https://hostname/resources/locale/en_US/help/GUID-1234567890.html and the
>>> args I’m passing are shown below… How do I encode them?
>>>
>>>
>>>
>>> Michael J. Regert
>>>
>>> Please consider the environment before printing this email.
>>>
>>> Confidentiality Notice | This e-mail message, including any attachments, is
>>> for the sole use of the intended recipient(s) and may contain confidential
>>> or proprietary information. Any unauthorized review, use, disclosure or
>>> distribution is prohibited. If you are not the intended recipient,
>>> immediately contact the sender by reply e-mail and destroy all copies of
>>> the original message.
>>>
>>>
>>>
>>> From: flexcode! rs@yahoo groups.com [mailto:flexcoders@yahoogroups.com] On
>>> Behalf Of Alex Harui
>>> Sent: Thursday, July 05, 2012 11:18 PM
>>> To: flexcoders@yahoogroups.com
>>> Subject: Re: [flexcoders] Errors in
>>> flash.external::ExternalInterface$/call()
>>>
>>>
>>>
>>> It appears that ExternalInterface.call takes its arguments and encodes them
>>> into XML before passing them to the HTML/JS wrapper. If there is something
>>> in the arguments that messes up the encoding then maybe you would get this
>>> error. I would try encoding entities in the urlString and maybe the
>>> additional args.
>>>
>>>
>>> On 7/5/12 12:46 PM, "michael_reg...@dell.com"
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>> I'm working on a bug which has us puzzled and I'm looking for a bit of
>>> direction. When we launch our external help documents (HTML) with the
>>> following command, sometimes we get an array of XML parse errors. It is
>>> very inconsistent and sometimes requires clicking the help button multiple
>>> times before it appears. I cannot step into the ExternalInterface code to
>>> see what it is failing on. The help page DOES launch correctly, so I know
>>> the URL is fine. But when I close the HTML page, I get an error sometimes.
>>> The error is not consistent either. Any pointers on how to debug this?
>>> Is the XML it is trying to parse the actual HTML? I would think that Flex
>>> would just open a browser window, ignoring the content. We're using Flex
>>> 4.0 SDK.
>>>
>>> We're calling:
>>> ExternalInterface.call("window.open",urlStri!
>>> ng,"_blank","status=1,scrollbars=1,toolbar=1,me! nubar=1,
>>> location=1,resizable=1");
>>>
>>> Errors seen include:
>>> TypeError: Error #1090: XML parser failure: element is malformed.
>>> at flash.external::ExternalInterface$/call()
>>>
>>> TypeError: Error #1095: XML parser failure: Unterminated attribute.
>>> at flash.external::ExternalInterface$/call()
>>>
>>> Error: Error #1502: A script has executed for longer than the default
>>> timeout period of 15 seconds.
>>> at flash.external::ExternalInterface$/_argumentsToXML()
>>> at flash.external::ExternalInterface$/call()
>>>
>>> - Michael J. Regert
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>>
>>>
>>>
>>
>
Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
Oh, also seeing "urlStri! ng" -- must be something else then...?
E
On Jul 9, 2012, at 4:28 PM, Erik van der Neut wrote:
>
> In your original message you wrote:
>
> me! nubar=1
>
> Instead of:
>
> menubar=1
>
> I assume that was a typo in your message to this group, not in your actual
> code?
>
> Erik
>
>
>
> On Jul 9, 2012, at 12:41 PM,
> wrote:
>
>>
>> Changing the function use encoding (%3D in place of the =) causes the
>> function to completely fail. I guess I can chalk this one up as an Adobe
>> bug overall?
>>
>>
>>
>> ExternalInterface.call("window.open",urlString,"_blank","status%3D1,scrollbars%3D1,toolbar%3D1,menubar%3D1,location%3D1,resizable%3D1");
>>
>>
>>
>>
>>
>> Michael J. Regert
>>
>>
>>
>> From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On
>> Behalf Of Alex Harui
>> Sent: Saturday, July 07, 2012 11:46 PM
>> To: flexcoders@yahoogroups.com
>> Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
>>
>>
>>
>>
>>
>> I’m just guessing here, but I get suspicious when I see non-alphas (equal
>> signs, dashes) in a URL. See this link:
>> http://www.w3schools.com/tags/ref_urlencode.asp
>>
>>
>> On 7/6/12 6:22 AM, "michael_reg...@dell.com" wrote:
>>
>>
>>
>>
>>
>>
>> Thank you Alex for your reply. Can you further clarify what you mean by
>> “try encoding entities in the urlString and maybe the additional args”. I
>> guess I’m not understanding. The URLString I’m passing in is like
>> https://hostname/resources/locale/en_US/help/GUID-1234567890.html and the
>> args I’m passing are shown below… How do I encode them?
>>
>>
>>
>> Michael J. Regert
>>
>> Please consider the environment before printing this email.
>>
>> Confidentiality Notice | This e-mail message, including any attachments, is
>> for the sole use of the intended recipient(s) and may contain confidential
>> or proprietary information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient,
>> immediately contact the sender by reply e-mail and destroy all copies of the
>> original message.
>>
>>
>>
>> From: flexcode! rs@yahoo groups.com [mailto:flexcoders@yahoogroups.com] On
>> Behalf Of Alex Harui
>> Sent: Thursday, July 05, 2012 11:18 PM
>> To: flexcoders@yahoogroups.com
>> Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
>>
>>
>>
>> It appears that ExternalInterface.call takes its arguments and encodes them
>> into XML before passing them to the HTML/JS wrapper. If there is something
>> in the arguments that messes up the encoding then maybe you would get this
>> error. I would try encoding entities in the urlString and maybe the
>> additional args.
>>
>>
>> On 7/5/12 12:46 PM, "michael_reg...@dell.com"
>> wrote:
>>
>>
>>
>>
>>
>>
>> I'm working on a bug which has us puzzled and I'm looking for a bit of
>> direction. When we launch our external help documents (HTML) with the
>> following command, sometimes we get an array of XML parse errors. It is
>> very inconsistent and sometimes requires clicking the help button multiple
>> times before it appears. I cannot step into the ExternalInterface code to
>> see what it is failing on. The help page DOES launch correctly, so I know
>> the URL is fine. But when I close the HTML page, I get an error sometimes.
>> The error is not consistent either. Any pointers on how to debug this? Is
>> the XML it is trying to parse the actual HTML? I would think that Flex
>> would just open a browser window, ignoring the content. We're using Flex
>> 4.0 SDK.
>>
>> We're calling:
>> ExternalInterface.call("window.open",urlStri!
>> ng,"_blank","status=1,scrollbars=1,toolbar=1,me! nubar=1,
>> location=1,resizable=1");
>>
>> Errors seen include:
>> TypeError: Error #1090: XML parser failure: element is malformed.
>> at flash.external::ExternalInterface$/call()
>>
>> TypeError: Error #1095: XML parser failure: Unterminated attribute.
>> at flash.external::ExternalInterface$/call()
>>
>> Error: Error #1502: A script has executed for longer than the default
>> timeout period of 15 seconds.
>> at flash.external::ExternalInterface$/_argumentsToXML()
>> at flash.external::ExternalInterface$/call()
>>
>> - Michael J. Regert
>>
>>
>>
>>
>>
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>>
>>
>
Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
In your original message you wrote:
me! nubar=1
Instead of:
menubar=1
I assume that was a typo in your message to this group, not in your actual code?
Erik
On Jul 9, 2012, at 12:41 PM,
wrote:
>
> Changing the function use encoding (%3D in place of the =) causes the
> function to completely fail. I guess I can chalk this one up as an Adobe bug
> overall?
>
>
>
> ExternalInterface.call("window.open",urlString,"_blank","status%3D1,scrollbars%3D1,toolbar%3D1,menubar%3D1,location%3D1,resizable%3D1");
>
>
>
>
>
> Michael J. Regert
>
>
>
> From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On
> Behalf Of Alex Harui
> Sent: Saturday, July 07, 2012 11:46 PM
> To: flexcoders@yahoogroups.com
> Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
>
>
>
>
>
> I’m just guessing here, but I get suspicious when I see non-alphas (equal
> signs, dashes) in a URL. See this link:
> http://www.w3schools.com/tags/ref_urlencode.asp
>
>
> On 7/6/12 6:22 AM, "michael_reg...@dell.com" wrote:
>
>
>
>
>
>
> Thank you Alex for your reply. Can you further clarify what you mean by “try
> encoding entities in the urlString and maybe the additional args”. I guess
> I’m not understanding. The URLString I’m passing in is like
> https://hostname/resources/locale/en_US/help/GUID-1234567890.html and the
> args I’m passing are shown below… How do I encode them?
>
>
>
> Michael J. Regert
>
> Please consider the environment before printing this email.
>
> Confidentiality Notice | This e-mail message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential or
> proprietary information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient,
> immediately contact the sender by reply e-mail and destroy all copies of the
> original message.
>
>
>
> From: flexcode! rs@yahoo groups.com [mailto:flexcoders@yahoogroups.com] On
> Behalf Of Alex Harui
> Sent: Thursday, July 05, 2012 11:18 PM
> To: flexcoders@yahoogroups.com
> Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
>
>
>
> It appears that ExternalInterface.call takes its arguments and encodes them
> into XML before passing them to the HTML/JS wrapper. If there is something
> in the arguments that messes up the encoding then maybe you would get this
> error. I would try encoding entities in the urlString and maybe the
> additional args.
>
>
> On 7/5/12 12:46 PM, "michael_reg...@dell.com" wrote:
>
>
>
>
>
>
> I'm working on a bug which has us puzzled and I'm looking for a bit of
> direction. When we launch our external help documents (HTML) with the
> following command, sometimes we get an array of XML parse errors. It is very
> inconsistent and sometimes requires clicking the help button multiple times
> before it appears. I cannot step into the ExternalInterface code to see what
> it is failing on. The help page DOES launch correctly, so I know the URL is
> fine. But when I close the HTML page, I get an error sometimes. The error
> is not consistent either. Any pointers on how to debug this? Is the XML it
> is trying to parse the actual HTML? I would think that Flex would just open
> a browser window, ignoring the content. We're using Flex 4.0 SDK.
>
> We're calling:
> ExternalInterface.call("window.open",urlStri!
> ng,"_blank","status=1,scrollbars=1,toolbar=1,me! nubar=1,
> location=1,resizable=1");
>
> Errors seen include:
> TypeError: Error #1090: XML parser failure: element is malformed.
> at flash.external::ExternalInterface$/call()
>
> TypeError: Error #1095: XML parser failure: Unterminated attribute.
> at flash.external::ExternalInterface$/call()
>
> Error: Error #1502: A script has executed for longer than the default timeout
> period of 15 seconds.
> at flash.external::ExternalInterface$/_argumentsToXML()
> at flash.external::ExternalInterface$/call()
>
> - Michael J. Regert
>
>
>
>
>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
>
>
RE: [flexcoders] Errors in flash.external::ExternalInterface$/call()
Changing the function use encoding (%3D in place of the =) causes the function
to completely fail. I guess I can chalk this one up as an Adobe bug overall?
ExternalInterface.call("window.open",urlString,"_blank","status%3D1,scrollbars%3D1,toolbar%3D1,menubar%3D1,location%3D1,resizable%3D1");
Michael J. Regert
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf
Of Alex Harui
Sent: Saturday, July 07, 2012 11:46 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
I'm just guessing here, but I get suspicious when I see non-alphas (equal
signs, dashes) in a URL. See this link:
http://www.w3schools.com/tags/ref_urlencode.asp
On 7/6/12 6:22 AM, "michael_reg...@dell.com" wrote:
Thank you Alex for your reply. Can you further clarify what you mean by "try
encoding entities in the urlString and maybe the additional args". I guess I'm
not understanding. The URLString I'm passing in is like
https://hostname/resources/locale/en_US/help/GUID-1234567890.html and the args
I'm passing are shown below... How do I encode them?
Michael J. Regert
Please consider the environment before printing this email.
Confidentiality Notice | This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, immediately
contact the sender by reply e-mail and destroy all copies of the original
message.
From: flexcode! rs@yahoo groups.com [mailto:flexcoders@yahoogroups.com] On
Behalf Of Alex Harui
Sent: Thursday, July 05, 2012 11:18 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Errors in flash.external::ExternalInterface$/call()
It appears that ExternalInterface.call takes its arguments and encodes them
into XML before passing them to the HTML/JS wrapper. If there is something in
the arguments that messes up the encoding then maybe you would get this error.
I would try encoding entities in the urlString and maybe the additional args.
On 7/5/12 12:46 PM, "michael_reg...@dell.com" wrote:
I'm working on a bug which has us puzzled and I'm looking for a bit of
direction. When we launch our external help documents (HTML) with the
following command, sometimes we get an array of XML parse errors. It is very
inconsistent and sometimes requires clicking the help button multiple times
before it appears. I cannot step into the ExternalInterface code to see what
it is failing on. The help page DOES launch correctly, so I know the URL is
fine. But when I close the HTML page, I get an error sometimes. The error is
not consistent either. Any pointers on how to debug this? Is the XML it is
trying to parse the actual HTML? I would think that Flex would just open a
browser window, ignoring the content. We're using Flex 4.0 SDK.
We're calling:
ExternalInterface.call("window.open",urlStri!
ng,"_blank","status=1,scrollbars=1,toolbar=1,me! nubar=1,
location=1,resizable=1");
Errors seen include:
TypeError: Error #1090: XML parser failure: element is malformed.
at flash.external::ExternalInterface$/call()
TypeError: Error #1095: XML parser failure: Unterminated attribute.
at flash.external::ExternalInterface$/call()
Error: Error #1502: A script has executed for longer than the default timeout
period of 15 seconds.
at flash.external::ExternalInterface$/_argumentsToXML()
at flash.external::ExternalInterface$/call()
- Michael J. Regert
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
[flexcoders] Re: Resetting Chart scale on LineAxis
Hi, The minimum and maximum properties of the LinearAxis are not bound to anything and they are the ones I have problems with (values not resetting when setting series visibility). Only the minimum and maximum properties of the DateTimeAxis are bound and there is no problem with that part. Best regards, Karl. --- In flexcoders@yahoogroups.com, claudiu ursica wrote: > > Hi Karl, > I am not an expert on the charts, I only played with an example from the docs > which updates nicely. Hence the request about some > basic example to see if it can be narrowed down. Unless you already try it, > you can debug the bindings via the > BindingManager.debugBinding() or wrap the min/max inside functions and add > temporary log/checks support inside those functions > to see if calls/updates are happenin. If it is a binding issue you are in > luck... > > On the other hand, you may also have to byte the bullet and replace the > bindings with hand written code. That way you get a better control of what > code is executing... > If it is a bug in the charts than you will need to fix/monkey patch it... > > Either way it helps if you can narrow it down to a simple example where you > can add/remove data from a button. If you can have that I can also > try to have a look at it. > > HTH, > C > > > > > From: k.sigiscar > To: flexcoders@yahoogroups.com > Sent: Monday, July 9, 2012 3:19 PM > Subject: [flexcoders] Re: Resetting Chart scale on LineAxis > > > Â > > Hi Claudiu, > > Yes, I saw that one. But he's using a CategoryAxis and not a DateTimeAxis (we > bind the minimum and maximum properties of the DateTimeAxis to the values of > our timeline component). > > Therefore, we cannot do the same thing as he does to reset the chart scale. > > Best regards, > Karl. > > --- In flexcoders@yahoogroups.com, claudiu ursica wrote: > > > > Hi Karl, > > Can you share some basic example? I don't know how your chart and data > > looks like, and how you add/discard new data. > > > > I see you already ran into this and did not work... > > https://userflex.wordpress.com/2011/04/21/update-linear-axis/ > > > > C > > > > > > > > > > From: k.sigiscar > > To: flexcoders@yahoogroups.com > > Sent: Monday, July 9, 2012 10:24 AM > > Subject: [flexcoders] Resetting Chart scale on LineAxis > > > > > > ÃÂ > > Hi, > > > > I have a chart with dynamic series on a LinearAxis (Y) and a DateTimeAxis > > (X). > > > > The series visibility can be set to true / false by the user. > > > > When a series with a very high value is displayed, the rest of the chart is > > scaled down. > > > > When the series with the high values is then discarded (visibility set to > > false), the chart doesn't scale down again. > > > > Is there a way to force the chart to "reset its scale" (min/max) values ? > > > > Best regards, > > Karl Sigiscar. > > >
Re: [flexcoders] Re: Resetting Chart scale on LineAxis
Hi Karl, I am not an expert on the charts, I only played with an example from the docs which updates nicely. Hence the request about some basic example to see if it can be narrowed down. Unless you already try it, you can debug the bindings via the BindingManager.debugBinding() or wrap the min/max inside functions and add temporary log/checks support inside those functions to see if calls/updates are happenin. If it is a binding issue you are in luck... On the other hand, you may also have to byte the bullet and replace the bindings with hand written code. That way you get a better control of what code is executing... If it is a bug in the charts than you will need to fix/monkey patch it... Either way it helps if you can narrow it down to a simple example where you can add/remove data from a button. If you can have that I can also try to have a look at it. HTH, C From: k.sigiscar To: flexcoders@yahoogroups.com Sent: Monday, July 9, 2012 3:19 PM Subject: [flexcoders] Re: Resetting Chart scale on LineAxis Hi Claudiu, Yes, I saw that one. But he's using a CategoryAxis and not a DateTimeAxis (we bind the minimum and maximum properties of the DateTimeAxis to the values of our timeline component). Therefore, we cannot do the same thing as he does to reset the chart scale. Best regards, Karl. --- In flexcoders@yahoogroups.com, claudiu ursica wrote: > > Hi Karl, > Can you share some basic example? I don't know how your chart and data looks > like, and how you add/discard new data. > > I see you already ran into this and did not work... > https://userflex.wordpress.com/2011/04/21/update-linear-axis/ > > C > > > > > From: k.sigiscar > To: flexcoders@yahoogroups.com > Sent: Monday, July 9, 2012 10:24 AM > Subject: [flexcoders] Resetting Chart scale on LineAxis > > > Â > Hi, > > I have a chart with dynamic series on a LinearAxis (Y) and a DateTimeAxis (X). > > The series visibility can be set to true / false by the user. > > When a series with a very high value is displayed, the rest of the chart is > scaled down. > > When the series with the high values is then discarded (visibility set to > false), the chart doesn't scale down again. > > Is there a way to force the chart to "reset its scale" (min/max) values ? > > Best regards, > Karl Sigiscar. >
[flexcoders] Re: Resetting Chart scale on LineAxis
Hi Claudiu, Yes, I saw that one. But he's using a CategoryAxis and not a DateTimeAxis (we bind the minimum and maximum properties of the DateTimeAxis to the values of our timeline component). Therefore, we cannot do the same thing as he does to reset the chart scale. Best regards, Karl. --- In flexcoders@yahoogroups.com, claudiu ursica wrote: > > Hi Karl, > Can you share some basic example? I don't know how your chart and data looks > like, and how you add/discard new data. > > I see you already ran into this and did not work... > https://userflex.wordpress.com/2011/04/21/update-linear-axis/ > > C > > > > > From: k.sigiscar > To: flexcoders@yahoogroups.com > Sent: Monday, July 9, 2012 10:24 AM > Subject: [flexcoders] Resetting Chart scale on LineAxis > > > Â > Hi, > > I have a chart with dynamic series on a LinearAxis (Y) and a DateTimeAxis (X). > > The series visibility can be set to true / false by the user. > > When a series with a very high value is displayed, the rest of the chart is > scaled down. > > When the series with the high values is then discarded (visibility set to > false), the chart doesn't scale down again. > > Is there a way to force the chart to "reset its scale" (min/max) values ? > > Best regards, > Karl Sigiscar. >
Re: [flexcoders] Resetting Chart scale on LineAxis
Hi Karl, Can you share some basic example? I don't know how your chart and data looks like, and how you add/discard new data. I see you already ran into this and did not work... https://userflex.wordpress.com/2011/04/21/update-linear-axis/ C From: k.sigiscar To: flexcoders@yahoogroups.com Sent: Monday, July 9, 2012 10:24 AM Subject: [flexcoders] Resetting Chart scale on LineAxis Hi, I have a chart with dynamic series on a LinearAxis (Y) and a DateTimeAxis (X). The series visibility can be set to true / false by the user. When a series with a very high value is displayed, the rest of the chart is scaled down. When the series with the high values is then discarded (visibility set to false), the chart doesn't scale down again. Is there a way to force the chart to "reset its scale" (min/max) values ? Best regards, Karl Sigiscar.
[flexcoders] Resetting Chart scale on LineAxis
Hi, I have a chart with dynamic series on a LinearAxis (Y) and a DateTimeAxis (X). The series visibility can be set to true / false by the user. When a series with a very high value is displayed, the rest of the chart is scaled down. When the series with the high values is then discarded (visibility set to false), the chart doesn't scale down again. Is there a way to force the chart to "reset its scale" (min/max) values ? Best regards, Karl Sigiscar.
