This was a very interesting and rather "perfect storm" scenario to patch,
figure out, then fix:
first the patch: using the monthname property of datefield just assign an
array to that {mNames} with the month names as strings in the array fixed
the issue.the issue: I'm using localization to pass in some name/value pairs of server settings (dev vs. deploy etc..) which is quite snazzy and using a custom written ruby build tool to compile the datefield component on a page into a swf. Since upgrading to Snow Leopard on os X I had forgotten to run some flex command line compiler things for localization. Note I *did not* change flex compilers, just the OS. Hence the nulls. So the cautionary tale is to remember the stuff you had to do a long time ago, and make sure you do it again for an os change :) really an insidious bug.. wren_ wrote: > > Hi All > I am using a normal dateField: > <mx:DateField x="101" y="373" id="ICDataEntry" formatString="MM/DD/YYYY" > visible="true" /> > > when you select the date chooser it looks like such: > http://www.nabble.com/file/p25670248/Untitled-1.jpg > > I could avesworn that this was working. > How does flex initially determine what the date and time is? Where does it > get these values.. why is there @#...@! Nulls?! > > Thanks > -- View this message in context: http://www.nabble.com/date-chooser-in-date-field-showing-strange-nulls-tp25670248p25683936.html Sent from the FlexCoders mailing list archive at Nabble.com.
