Re: [FLEXJS] Build failure significant

2016-01-13 Thread Michael Schmalle
On Tue, Jan 12, 2016 at 7:58 PM, Josh Tynjala wrote: > Mike, > > flash.utils.clearTimeout.length became a member access expression. > IdentifierEmitter never used the fully-qualified name for a member access > expression, so it was emitting as clearTimeout.length, without

Re: [Flex] Map Component

2016-01-13 Thread Deepak MS
Thanks Om. I tried that library with following code: var mc:MercatorProjection = new MercatorProjection(); for(var i:int = 0; i < a.length; i++) // a here is array of arrays - [ [ 151.25, -33.74 ],[ 151.25, -33.74 ] ..] { var ltlg:Array =

Re: [Flex] Map Component

2016-01-13 Thread OmPrakash Muppirala
Yes, it is lat and long. Out is the output point which should get updated during the projection. Thanks, Om On Jan 13, 2016 3:10 AM, "Deepak MS" wrote: > Thanks Om. > > I tried that library with following code: > var mc:MercatorProjection = new

Re: [Flex] Map Component

2016-01-13 Thread Deepak MS
Ok. But it isn't converting lat\long values to expected path data coordinates I believe. On Wed, Jan 13, 2016 at 5:37 PM, OmPrakash Muppirala wrote: > Yes, it is lat and long. Out is the output point which should get updated > during the projection. > > Thanks, > Om > On

Re: [FLEXJS] Build failure significant

2016-01-13 Thread Josh Tynjala
A ton of tests are good! Thank you for the effort. It really helps when someone like me (who is just learning the codebase) wants to make changes. I think your simple rule for handling member access expressions is generally the right way to go. It just happens to need a special case when a

Re: [FLEXJS] Build failure significant

2016-01-13 Thread Josh Tynjala
I found the note at the bottom of the readme about the compiler.tests/template-unittest.properties file. I had previously tried adding a unittest.properties to define the environment variables, but I guess I didn't get the details right at the time. Or maybe I didn't put it in the right directory.

Re: [Flex] Map Component

2016-01-13 Thread OmPrakash Muppirala
Give me the list of lat/long co-ordinates and the end result shape they should look like. I will try out a few things and see we can make this work. Thanks, Om On Wed, Jan 13, 2016 at 7:36 AM, OmPrakash Muppirala wrote: > > On Jan 13, 2016 4:36 AM, "Deepak MS"

Re: [Flex] Map Component

2016-01-13 Thread Deepak MS
Oh I really didn't knew that those values are swapped. Generally it would be lat\lng. Sorry for that. That was a sample data I got from the team and yes that is Oz data(NSW boundary). Anyway, to make it simple. I have created a project including the library:

Re: [Flex] Map Component

2016-01-13 Thread OmPrakash Muppirala
I took the coordinates from your earlier code and tried it out: override protected function createMap():void { var mc:MercatorProjection = new MercatorProjection(); mc.initialize(); var a:Array = [ [151.2571536004, -33.743317043500042 ], [151.2598582717,-33.74384022351 ],

Re: [Flex] Map Component

2016-01-13 Thread OmPrakash Muppirala
On Wed, Jan 13, 2016 at 2:02 PM, OmPrakash Muppirala wrote: > I took the coordinates from your earlier code and tried it out: > > override protected function createMap():void > { > var mc:MercatorProjection = new MercatorProjection(); > mc.initialize(); > var a:Array = [

Re: [Flex] Map Component

2016-01-13 Thread Paul Hastings
Latitude range is +/-90°. Might be the coords are swapped longitude, latitude. If so, puts that object somewhere in oz not UK. Were these coords the result of projecting? Bad imput params? PS: in the openscales project there's a port of proj4 to AS that works a treat.

Re: Updated Flash player / AIR hashes

2016-01-13 Thread Alex Harui
I just synced up and still get 4.15. What is in your copy of build.properties? Mine still says 4.15 and the last commit hash is d7aea2e70a1f4abb7d346ec21a37edd4aadbddd6 -Alex On 1/12/16, 9:42 PM, "Justin Mclean" wrote: >HI, > >> Does it work for you when you run ant