OK, I think this will be fixed in the next nightly build.
Thanks for helping find it,
-Alex
On 7/14/16, 12:49 PM, "Harbs" wrote:
>Here’s another compile problem which causes an error in FB:
>
> public var getSelectionState():SelectionState{return null}
>instead of:
> public function
Additionally, a decent number of those issues are attributed to people who
are not actively working on Apache FlexJS these days.
- Josh
On Thu, Jul 14, 2016 at 1:25 PM, Harbs wrote:
> It’s more likely that it’s more laziness or lack of familiarity with the
> tools than anything else.
>
> On Jul
It’s more likely that it’s more laziness or lack of familiarity with the tools
than anything else.
On Jul 14, 2016, at 11:14 PM, Christofer Dutz wrote:
> But I have the impression that no-one is actually looking at the reports
> cause everyone thinks his a real badass programmer. I regularly l
Here’s another compile problem which causes an error in FB:
public var getSelectionState():SelectionState{return null}
instead of:
public function getSelectionState():SelectionState{return null}
On Jul 14, 2016, at 8:24 AM, Alex Harui wrote:
> I will try to reproduce it.
>
> Th
I’m using a nightly from a couple of weeks ago.
On Jul 14, 2016, at 8:23 AM, Alex Harui wrote:
>
>
> On 7/13/16, 10:16 PM, "Harbs" wrote:
>
>> In all likelihood, it’s one of these:
>> Warning: Initializer value NaN is not valid for type 'uint'. An initial
>> value of 0 will be used instead.
I will try to reproduce it.
Thanks,
-Alex
On 7/13/16, 10:20 PM, "Harbs" wrote:
>Yup.
>
>Changing this function get listAutoPadding:int; to this function get
>listAutoPadding():*; made the error go away.
>
>Is that enough to fix flex-compiler-oem?
>
>On Jul 14, 2016, at 8:16 AM, Harbs wrote:
>
On 7/13/16, 10:16 PM, "Harbs" wrote:
>In all likelihood, it’s one of these:
>Warning: Initializer value NaN is not valid for type 'uint'. An initial
>value of 0 will be used instead.
>static public function show(message:String, title:String=null,
>buttons:uint=NaN, dummy2:String=null, e
Yup.
Changing this function get listAutoPadding:int; to this function get
listAutoPadding():*; made the error go away.
Is that enough to fix flex-compiler-oem?
On Jul 14, 2016, at 8:16 AM, Harbs wrote:
> In all likelihood, it’s one of these:
> Warning: Initializer value NaN is not valid for t
In all likelihood, it’s one of these:
Warning: Initializer value NaN is not valid for type 'uint'. An initial value
of 0 will be used instead.
static public function show(message:String, title:String=null,
buttons:uint=NaN, dummy2:String=null, eventHandler:Function=null):void
Try compiling from the command line with mxmlc or compc. I think some
error or warning is being output which is messing up the FB integration.
-Alex
On 7/13/16, 9:40 PM, "Harbs" wrote:
>I’m not sure how to compile using Maven and I don’t have ant set up for
>this project.
>
>I tried reverting
Never mind. My revert wasn’t. I completely reverted and the error went away.
I’ll try to narrow down which class is causing the error (or I’ll try and use
ant).
On Jul 14, 2016, at 7:40 AM, Harbs wrote:
> I’m not sure how to compile using Maven and I don’t have ant set up for this
> project.
I’m not sure how to compile using Maven and I don’t have ant set up for this
project.
I tried reverting the code to a state where I know for sure it compiled without
the error, and I’m still getting the error when I compile that code.
I’ll see if Yishay and I can work this out together…
On Jul
Try compiling your code outside of FB with Ant or Maven. Odds are there
is a warning or error that is not formatted in a way the flex-compiler-oem
code expects. Getting rid of errors should unblock FB.
-Alex
On 7/13/16, 2:21 PM, "Harbs" wrote:
>I’m not sure.
>
>At some point (I think this mor
I’m not sure.
At some point (I think this morning — but it might have been yesterday) my
Workspace became completely corrupted and FB would not launch. I created a new
workspace. I think it worked at first, but I might be mistaken. I’m pretty sure
I followed the instructions in the wiki to set
On 7/13/16, 1:50 PM, "Harbs" wrote:
>Flash Builder 4.7 has been pretty unstable for me.
>
>I tried updating Java today hoping that it might help and everything went
>haywire. I can not get FB to build anything now. I think installing Java
>reset my default Java to 1.7, but I changed my symbolic
Does a clean build fix it?
Does deleting the codemodel folder fix it?
Mine is at /Users/clint/Documents/Adobe Flash Builder
4.7/.metadata/.plugins/com.adobe.flexide.codemodel.bridge
Does a new workspace fix it? Sometimes eclipse workspaces become corrupt.
RE: instability
what is your Xmx set at in
16 matches
Mail list logo
