[jira] [Commented] (FLEX-17567) The DateFormatter cannot format the date if the date in UTC is Jan 1st 1970 0 hours 0mins 0sec and 0 milliseconds

[ https://issues.apache.org/jira/browse/FLEX-17567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637495#comment-13637495 ] Justin Mclean commented on FLEX-17567: -- Can't reproduce probably fixed. http://ns.a

[jira] [Resolved] (FLEX-17567) The DateFormatter cannot format the date if the date in UTC is Jan 1st 1970 0 hours 0mins 0sec and 0 milliseconds

[ https://issues.apache.org/jira/browse/FLEX-17567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-17567. -- Resolution: Cannot Reproduce > The DateFormatter cannot format the date if the date in UTC

[jira] [Resolved] (FLEX-22068) DateFormatter.parse does not correctly handle positive GMT offset (such as UK)

[ https://issues.apache.org/jira/browse/FLEX-22068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved FLEX-22068. -- Resolution: Fixed This has been fixed as described in a pervious version of the SDK and works

[jira] [Assigned] (FLEX-24411) DateFormatter.parseDateString() function doesn't properly read in SQLite seconds values

[ https://issues.apache.org/jira/browse/FLEX-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned FLEX-24411: Assignee: Justin Mclean > DateFormatter.parseDateString() function doesn't properly rea

Re: DateField Issues and fixes

Hi Justin, FYI, few years ago, I did a closer examination of existing limitations of current DateFormatter from Flex3 and suggested a few fixes for the following issues (old JIRA numeration): Fixed SDK-23069 [Localization]: DateFormatter.parseDateStr

Re: DateField Issues and fixes

Hi, Thanks for that I take a look tomorrow. I have to ask did you write all the code yourself and are able to donate it to Apache Flex? From what I can see it's under a Apache style licence already. https://github.com/JabbyPanda/DateField4/blob/master/LICENSE Thanks, Justin

Re: Been out of the loop -- looking to catch up

ok, did you compile the all test at least once and ran mustella db ? one more point, if there is a space as a first char of the output lines, they should be remove before you can use them as the chooser input. -Fred -Message d'origine- From: Nicholas Kwiatkowski Sent: Sunday, April

[jira] [Closed] (FLEX-25646) ArrayCollection removeItem function

[ https://issues.apache.org/jira/browse/FLEX-25646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Rovira closed FLEX-25646. Resolution: Duplicate Fix Version/s: Apache Flex 4.10.0 This was already fixed in https://i

Re: Been out of the loop -- looking to catch up

On Sun, Apr 21, 2013 at 10:38 AM, Frédéric THOMAS wrote: > ok, did you compile the all test at least once and ran mustella db ? > Yes. I have been able to use the tool successfully before the move to SVN. > one more point, if there is a space as a first char of the output lines, > they should b

Re: Been out of the loop -- looking to catch up

On Sun, Apr 21, 2013 at 12:21 AM, Alex Harui wrote: > > > > On 4/20/13 5:23 PM, "Nicholas Kwiatkowski" wrote: > > > > - I have Tour de Flex from Adobe ready to donate (been sitting on it > for a > > few weeks, actually. I've brought it up to date from the last version > > Adobe published) . W

[jira] [Resolved] (FLEX-23974) Datagrid with ArrayCollection provider, error at setter of selectedIndex after applying filters to the ArrayCollection

[ https://issues.apache.org/jira/browse/FLEX-23974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Kessler resolved FLEX-23974. - Resolution: Fixed The itemRenderers were not updated immediately following a dataProvider refres

[jira] [Closed] (FLEX-23974) Datagrid with ArrayCollection provider, error at setter of selectedIndex after applying filters to the ArrayCollection

[ https://issues.apache.org/jira/browse/FLEX-23974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Kessler closed FLEX-23974. --- > Datagrid with ArrayCollection provider, error at setter of selectedIndex > after applying filters

Re: Been out of the loop -- looking to catch up

To be more precise, the result of this git command gives, for the 2 first chars, the status of the index and the working copy changes/add/remove of the files, for that reason, it has to cleaned up of this extra info before to be used by the chooser, or, the other option it to make the chooser c

Re: Been out of the loop -- looking to catch up

Fred, Can you update the Mustella WIKI page with that information? -Nick On Sun, Apr 21, 2013 at 1:16 PM, Frédéric THOMAS wrote: > To be more precise, the result of this git command gives, for the 2 first > chars, the status of the index and the working copy changes/add/remove of > the files, f

[jira] [Commented] (FLEX-18697) ObjectUtil.getCacheKey does not make cache key correctly

[ https://issues.apache.org/jira/browse/FLEX-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637632#comment-13637632 ] Nick Kwiatkowski commented on FLEX-18697: - Justin, Do you have any tests within

[jira] [Assigned] (FLEX-33370) max drag rate in SliderBase should not be a Constant

[ https://issues.apache.org/jira/browse/FLEX-33370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Kwiatkowski reassigned FLEX-33370: --- Assignee: Nick Kwiatkowski > max drag rate in SliderBase should not be a Constant

[jira] [Resolved] (FLEX-33370) max drag rate in SliderBase should not be a Constant

[ https://issues.apache.org/jira/browse/FLEX-33370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Kwiatkowski resolved FLEX-33370. - Resolution: Fixed Fix Version/s: Apache Flex Next Fixed in develop branch via GIT

[jira] [Reopened] (FLEX-20983) "dateFormat" value from "SharedResources.properties" should not be shared between DateFields and DateFormatters

[ https://issues.apache.org/jira/browse/FLEX-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-20983: -- +1 for consistency and wider support for date formats. > "dateFormat" value from "

[jira] [Reopened] (FLEX-17931) [Localization]:[HS:CN]The default value of property "dateFormat" of the Class "DateFormatter, DateValidator and DateField" should be "YYYY-M-D" with local zh_CN.

[ https://issues.apache.org/jira/browse/FLEX-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-17931: -- DateField now supports M and D formatting. > [Localization]:[HS:CN]The default val

[jira] [Reopened] (FLEX-24259) DateField does not correctly parse nor format dates in fr_FR locale

[ https://issues.apache.org/jira/browse/FLEX-24259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-24259: -- Now that DateFormat supports MMM this should be fixed. > DateField does not correc

[jira] [Updated] (FLEX-24259) DateField does not correctly parse nor format dates in fr_FR locale

[ https://issues.apache.org/jira/browse/FLEX-24259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-24259: - Labels: easyfix (was: ) > DateField does not correctly parse nor format dates in fr_FR local

[jira] [Updated] (FLEX-24259) DateField does not correctly parse nor format dates in fr_FR locale

[ https://issues.apache.org/jira/browse/FLEX-24259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-24259: - Labels: easytest (was: easyfix) > DateField does not correctly parse nor format dates in fr_

[jira] [Reopened] (FLEX-20951) [Localization]: DateFormatter.parseDateString does not support non-latin characters in month and days names

[ https://issues.apache.org/jira/browse/FLEX-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-20951: -- Untested but looks like issue still exists. > [Localization]: DateFormatter.parseD

[jira] [Updated] (FLEX-20951) [Localization]: DateFormatter.parseDateString does not support non-latin characters in month and days names

[ https://issues.apache.org/jira/browse/FLEX-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-20951: - Labels: easyfix easytest (was: ) > [Localization]: DateFormatter.parseDateString does not su

[jira] [Reopened] (FLEX-12503) DateFormatter with formatString "MM/DD/YYYY H:NN A" formats Time of "00:00:00" to "24:00 AM" instead of "00:00 AM"

[ https://issues.apache.org/jira/browse/FLEX-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-12503: -- Valid formatting of dates is important. > DateFormatter with formatString "MM/DD/Y

[jira] [Updated] (FLEX-12503) DateFormatter with formatString "MM/DD/YYYY H:NN A" formats Time of "00:00:00" to "24:00 AM" instead of "00:00 AM"

[ https://issues.apache.org/jira/browse/FLEX-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-12503: - Labels: easytest (was: ) > DateFormatter with formatString "MM/DD/ H:NN A" formats Time

[jira] [Reopened] (FLEX-24225) DateFormatter "parseDateString" method cannot parse dateString value formatted with non default en_US format

[ https://issues.apache.org/jira/browse/FLEX-24225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-24225: -- Should now be fixed - double check to be sure. > DateFormatter "parseDateString" m

[jira] [Updated] (FLEX-24225) DateFormatter "parseDateString" method cannot parse dateString value formatted with non default en_US format

[ https://issues.apache.org/jira/browse/FLEX-24225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-24225: - Labels: easytest (was: ) > DateFormatter "parseDateString" method cannot parse dateString va

[jira] [Reopened] (FLEX-18090) DateField with a lowercase formatString does not work

[ https://issues.apache.org/jira/browse/FLEX-18090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-18090: -- Change docs to specify only upper case letters are supported or add support lowercase letters.

[jira] [Reopened] (FLEX-20956) [Localization]: DateField should support "MMM" and "MMMM" for formatString

[ https://issues.apache.org/jira/browse/FLEX-20956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-20956: -- MMM is default in some locales so should be supported. > [Localization]: DateField

[jira] [Updated] (FLEX-20956) [Localization]: DateField should support "MMM" and "MMMM" for formatString

[ https://issues.apache.org/jira/browse/FLEX-20956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-20956: - Labels: easyfix (was: ) > [Localization]: DateField should support "MMM" and "" for form

[jira] [Reopened] (FLEX-26048) DateChooser throws #1010 error when selectableRange is empty object

[ https://issues.apache.org/jira/browse/FLEX-26048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-26048: -- Nice to fix RTEs > DateChooser throws #1010 error when selectableRange is empty ob

[jira] [Updated] (FLEX-26048) DateChooser throws #1010 error when selectableRange is empty object

[ https://issues.apache.org/jira/browse/FLEX-26048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-26048: - Labels: easyfix easytest (was: ) > DateChooser throws #1010 error when selectableRange is em

[jira] [Reopened] (FLEX-20566) Date Validator not handling single digit date configurations correctly for localized versions - i.e accepting yyyy-m-d as a legal configuration

[ https://issues.apache.org/jira/browse/FLEX-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-20566: -- Needs to support single digit M and D fields may of been fixed with recent changes.

[jira] [Updated] (FLEX-20566) Date Validator not handling single digit date configurations correctly for localized versions - i.e accepting yyyy-m-d as a legal configuration

[ https://issues.apache.org/jira/browse/FLEX-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-20566: - Labels: easytest (was: ) > Date Validator not handling single digit date configurations corr

What's the easiest way to tell if a character is a letter or not?

Hi, Anyone know how to work out if a character, including unicode characters, is a letter or not? This is not the right way of doing it: if ("a" <= letter && letter <= "z" || "A" <= letter && letter <= "Z") From the DateFormatter class for the curious. Thanks, Just

Re: What's the easiest way to tell if a character is a letter or not?

You would probably want to use the charCodeAt() function on the string. Assuming you want to search for printable, latin characters, the codes would be 65 - 90 (upper case A-Z) and 97 - 122 (lower case a-z). if ((letter.charCodeAt(0) >= 65) && (letter.charCodeAt(0) <= 90)) || ((letter.charCodeAt(

[jira] [Resolved] (FLEX-23303) getting the selectedIndex from a RadioButtonGroup

[ https://issues.apache.org/jira/browse/FLEX-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Kessler resolved FLEX-23303. - Resolution: Implemented Added new selectedIndex enhancement to the RadioButtonGroup. Small updat

[jira] [Closed] (FLEX-23303) getting the selectedIndex from a RadioButtonGroup

[ https://issues.apache.org/jira/browse/FLEX-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Kessler closed FLEX-23303. --- > getting the selectedIndex from a RadioButtonGroup > ---

[jira] [Commented] (FLEX-23303) getting the selectedIndex from a RadioButtonGroup

[ https://issues.apache.org/jira/browse/FLEX-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637728#comment-13637728 ] Mark Kessler commented on FLEX-23303: - Test app showing it working... http://ns.ado

Re: What's the easiest way to tell if a character is a letter or not?

Hi, > You would probably want to use the charCodeAt() function on the string. Would that catch characters with accents and the like this? eg "Février", "Décembre", "Ağustos" or "Eylül"? That's the issue. Thanks, Justin

[jira] [Reopened] (FLEX-32404) Legend does not accept Array of LegendItem

[ https://issues.apache.org/jira/browse/FLEX-32404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reopened FLEX-32404: -- Just run into this very issue. Looks like a mismatch between aspectRatio and markerAspectRatio. Ei

Re: What's the easiest way to tell if a character is a letter or not?

It looks like you will need to add the following : 192 - 255, exclusive of 247 & 215 (multiplication and division symbol codes). That should cover all the latin characters as well, but it won't do anything for non-latin characters. http://ascii-table.com/ansi-codes.php You may have to add 181,

Re: What's the easiest way to tell if a character is a letter or not?

On 4/22/2013 9:23 AM, Justin Mclean wrote: Would that catch characters with accents and the like this? eg "Février", "Décembre", "Ağustos" or "Eylül"? no, you'd need to extend the range a bit, 0x0041-0x00FF. though it depends on the languages/locales you wanted to support, which is somewhat

Re: What's the easiest way to tell if a character is a letter or not?

take that back, http://as3localedata.riaforge.org/ does have source.

[jira] [Commented] (FLEX-18697) ObjectUtil.getCacheKey does not make cache key correctly

[ https://issues.apache.org/jira/browse/FLEX-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637750#comment-13637750 ] Justin Mclean commented on FLEX-18697: -- Hard to see from DG code but if you run this

Re: What's the easiest way to tell if a character is a letter or not?

Hi, Thank Paul for all of that - very interesting and possible one way to go as the code is under MIT licence. I'm now thinking the quick fix solution is to skip anything that's not a space or format character as that's the smaller set. At this point in the code it doesn't really care if the m

[jira] [Commented] (FLEX-18697) ObjectUtil.getCacheKey does not make cache key correctly

[ https://issues.apache.org/jira/browse/FLEX-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637753#comment-13637753 ] Justin Mclean commented on FLEX-18697: -- Also ObjectProxy uses this with includeReadOn

[jira] [Comment Edited] (FLEX-18697) ObjectUtil.getCacheKey does not make cache key correctly

[ https://issues.apache.org/jira/browse/FLEX-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637753#comment-13637753 ] Justin Mclean edited comment on FLEX-18697 at 4/22/13 3:51 AM: -

[jira] [Created] (FLEX-33509) mx:Legend fails to copy styles in populateFromArray

Justin Mclean created FLEX-33509: Summary: mx:Legend fails to copy styles in populateFromArray Key: FLEX-33509 URL: https://issues.apache.org/jira/browse/FLEX-33509 Project: Apache Flex Issue

[jira] [Updated] (FLEX-33509) mx:Legend fails to copy styles in populateFromArray

[ https://issues.apache.org/jira/browse/FLEX-33509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated FLEX-33509: - Description: mx:Legend fails to copy styles in populateFromArray. Means setting legendMarkerRend

[jira] [Comment Edited] (FLEX-18697) ObjectUtil.getCacheKey does not make cache key correctly

[ https://issues.apache.org/jira/browse/FLEX-18697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637750#comment-13637750 ] Justin Mclean edited comment on FLEX-18697 at 4/22/13 5:44 AM: -

Re: What's the easiest way to tell if a character is a letter or not?

On 4/21/13 8:43 PM, "Justin Mclean" wrote: > Hi, > > Thank Paul for all of that - very interesting and possible one way to go as > the code is under MIT licence. > > I'm now thinking the quick fix solution is to skip anything that's not a space > or format character as that's the smaller set

Re: git commit: [flex-sdk] - Fixes FLEX-33370. Refactors MAX_DRAG_RATE to be a protected variable so that it is extenable by other components.

Hi Nick, Welcome back. I think protected vars don't go in the list in the class header. Also, git seems to show different indentation than the rest of the file. -Alex On 4/21/13 2:23 PM, "que...@apache.org" wrote: > Updated Branches: > refs/heads/develop 024a49261 -> e6c5be9c2 > > > Fix

Re: Been out of the loop -- looking to catch up

On 4/21/13 9:28 AM, "Nicholas Kwiatkowski" wrote: > On Sun, Apr 21, 2013 at 12:21 AM, Alex Harui wrote: > >> >> >> >> On 4/20/13 5:23 PM, "Nicholas Kwiatkowski" wrote: >> >> >>> - I have Tour de Flex from Adobe ready to donate (been sitting on it >> for a >>> few weeks, actually. I'v

Re: What's the easiest way to tell if a character is a letter or not?

HI, > If I understand you, I think that is actually the right solution. I think > you want to identify if a sequence of chars is a valid format pattern". This bit of the code is just skipping month names and is broken for locales with anything outside a-z,A-Z in them. This is in parseDateStrin