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" <harbs.li...@gmail.com> wrote:
>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 <aha...@adobe.com> wrote:
>
>> I will try to reproduce it.
>>
>> Thanks,
>> -Alex
>>
>> On 7/13/16, 10:20 PM, "Harbs" <harbs.li...@gmail.com> 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 <harbs.li...@gmail.com> 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, eventHandler:Function=null):void
>>>>
>>>> ^
>>>>
>>>>
>>>>
>>>>/Users/harbs/Documents/git/PrintUI/printui-flexjs/PortedPrintUI/src/com
>>>>/p
>>>> rintui/dummy/tlf/ITextLayoutFormat.as:25
>>>> Syntax error: Expected PAREN_OPEN but got ':'
>>>> function get listAutoPadding:int;
>>>>
>>>> I’d guess it’s the second one, although I’m not sure why I’m not
>>>> getting the first output in FB.
>>>>
>>>> On Jul 14, 2016, at 7:46 AM, Alex Harui <aha...@adobe.com> wrote:
>>>>
>>>>> 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" <harbs.li...@gmail.com> wrote:
>>>>>
>>>>>> 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…
>>>>>
>>>>
>>>
>>
>
