subject:"Re\: Compiler warnings \!"

Re: Compiler warnings !

2020-06-10 Thread serkan


I checked and confirm, it works Alex,

Thanks,
Serkan

10.06.2020 10:39 tarihinde Alex Harui yazdı:


I pushed a change that should handle (data as XML).foo.bar.baz

HTH,

-Alex

*From: *serkan 
*Date: *Tuesday, June 9, 2020 at 10:21 PM
*To: *Alex Harui , "users@royale.apache.org" 


*Subject: *Re: Compiler warnings !

I do not like the way but it is really annoying and making hard to 
find out error cases.


I may easily switch back if you can fix.

Thanks,
Serkan

10.06.2020 00:05 tarihinde Alex Harui yazdı:

Up to you.  I will try to find some time to see why “as XML” did
not work.  The risk of suppressing a warning is that you might
miss an important one.

-Alex

*From: *serkan 
<mailto:ser...@likyateknoloji.com>
*Date: *Tuesday, June 9, 2020 at 2:01 PM
*To: *Alex Harui  <mailto:aha...@adobe.com>,
"users@royale.apache.org" <mailto:users@royale.apache.org>
 <mailto:users@royale.apache.org>
*Subject: *Re: Compiler warnings !

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know. Try “as XML” and see if that solves the problem.

*From: *serkan 
<mailto:ser...@likyateknoloji.com>
*Date: *Monday, June 8, 2020 at 1:26 PM
*To: *"users@royale.apache.org"
<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>, Alex Harui
     <mailto:aha...@adobe.com>
*Subject: *Re: Compiler warnings !

Actually they are xml objects.


    
        
            SENSORDATA_HOURLY
        
        
            0
            
                false
false
false
                false
false
                false
false
false
true
            
        
    


So if I use as visible="{(data as
XML).visualParams.commandabilityParams.isResumable == true}"
may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

1)Make sure none of the properties in the binding
expression are of type Object and that the instances
support change events

2)Annotate the appropriate properties with
[Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is
Object.  If you are passing in a Foo as data, then the
expression should be:

visible="{(data as
Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not
plain Objects, the binding subsystem will watch for change
events correctly and the warning should go way.

Sometimes you do want to use a plain object where the
individual properties are not going to change.  You’ll
change the entire object instead of individual
properties.  This is common in renderers.  In such a case
you can use the “__NoChangeEvent__”.

HTH,

-Alex

Re: Compiler warnings !

2020-06-10 Thread Alex Harui

I pushed a change that should handle (data as XML).foo.bar.baz

HTH,
-Alex

From: serkan 
Date: Tuesday, June 9, 2020 at 10:21 PM
To: Alex Harui , "users@royale.apache.org" 

Subject: Re: Compiler warnings !

I do not like the way but it is really annoying and making hard to find out 
error cases.

I may easily switch back if you can fix.

Thanks,
Serkan
10.06.2020 00:05 tarihinde Alex Harui yazdı:
Up to you.  I will try to find some time to see why “as XML” did not work.  The 
risk of suppressing a warning is that you might miss an important one.

-Alex

From: serkan <mailto:ser...@likyateknoloji.com>
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui <mailto:aha...@adobe.com>, 
"users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
Subject: Re: Compiler warnings !

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan
9.06.2020 19:19 tarihinde Alex Harui yazdı:
I don’t know.  Try “as XML” and see if that solves the problem.

From: serkan <mailto:ser...@likyateknoloji.com>
Date: Monday, June 8, 2020 at 1:26 PM
To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>, Alex Harui 
<mailto:aha...@adobe.com>
Subject: Re: Compiler warnings !

Actually they are xml objects.

SENSORDATA_HOURLY

0

false
false
false
false
false
false
false
false
true

So if I use as visible="{(data as 
XML).visualParams.commandabilityParams.isResumable == true}" may fix the 
warnings. Right ? Or still need “__NoChangeEvent__”.?
8.06.2020 19:03 tarihinde Alex Harui yazdı:
There are two ways, depending on the scenario:

1)  Make sure none of the properties in the binding expression are of type 
Object and that the instances support change events

2)  Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is Object.  If you are 
passing in a Foo as data, then the expression should be:
visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain Objects, the 
binding subsystem will watch for change events correctly and the warning should 
go way.

Sometimes you do want to use a plain object where the individual properties are 
not going to change.  You’ll change the entire object instead of individual 
properties.  This is common in renderers.  In such a case you can use the 
“__NoChangeEvent__”.

HTH,
-Alex

Re: Compiler warnings !

2020-06-09 Thread serkan

I do not like the way but it is really annoying and making hard to find 
out error cases.


I may easily switch back if you can fix.

Thanks,
Serkan

10.06.2020 00:05 tarihinde Alex Harui yazdı:


Up to you.  I will try to find some time to see why “as XML” did not 
work.  The risk of suppressing a warning is that you might miss an 
important one.


-Alex

*From: *serkan 
*Date: *Tuesday, June 9, 2020 at 2:01 PM
*To: *Alex Harui , "users@royale.apache.org" 


*Subject: *Re: Compiler warnings !

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

*From: *serkan 
<mailto:ser...@likyateknoloji.com>
*Date: *Monday, June 8, 2020 at 1:26 PM
*To: *"users@royale.apache.org" <mailto:users@royale.apache.org>
 <mailto:users@royale.apache.org>, Alex
Harui  <mailto:aha...@adobe.com>
*Subject: *Re: Compiler warnings !

Actually they are xml objects.


    
        
            SENSORDATA_HOURLY
        
        
            0
            
                false
                false
                false
                false
                false
                false
false
false
                true
            
        
    


So if I use as visible="{(data as
XML).visualParams.commandabilityParams.isResumable == true}" may
fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

1)Make sure none of the properties in the binding expression
are of type Object and that the instances support change events

2)Annotate the appropriate properties with
[Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is
Object.  If you are passing in a Foo as data, then the
expression should be:

visible="{(data as
Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain
Objects, the binding subsystem will watch for change events
correctly and the warning should go way.

Sometimes you do want to use a plain object where the
individual properties are not going to change.  You’ll change
the entire object instead of individual properties.  This is
common in renderers.  In such a case you can use the
“__NoChangeEvent__”.

HTH,

-Alex

Re: Compiler warnings !

2020-06-09 Thread Alex Harui

Up to you.  I will try to find some time to see why “as XML” did not work.  The 
risk of suppressing a warning is that you might miss an important one.

-Alex

From: serkan 
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui , "users@royale.apache.org" 

Subject: Re: Compiler warnings !

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan
9.06.2020 19:19 tarihinde Alex Harui yazdı:
I don’t know.  Try “as XML” and see if that solves the problem.

From: serkan <mailto:ser...@likyateknoloji.com>
Date: Monday, June 8, 2020 at 1:26 PM
To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>, Alex Harui 
<mailto:aha...@adobe.com>
Subject: Re: Compiler warnings !

Actually they are xml objects.

SENSORDATA_HOURLY

0

false
false
false
false
false
false
false
false
true

So if I use as visible="{(data as 
XML).visualParams.commandabilityParams.isResumable == true}" may fix the 
warnings. Right ? Or still need “__NoChangeEvent__”.?
8.06.2020 19:03 tarihinde Alex Harui yazdı:
There are two ways, depending on the scenario:

1)  Make sure none of the properties in the binding expression are of type 
Object and that the instances support change events

2)  Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is Object.  If you are 
passing in a Foo as data, then the expression should be:
visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain Objects, the 
binding subsystem will watch for change events correctly and the warning should 
go way.

Sometimes you do want to use a plain object where the individual properties are 
not going to change.  You’ll change the entire object instead of individual 
properties.  This is common in renderers.  In such a case you can use the 
“__NoChangeEvent__”.

HTH,
-Alex

Re: Compiler warnings !

2020-06-09 Thread serkan


Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:


I don’t know.  Try “as XML” and see if that solves the problem.

*From: *serkan 
*Date: *Monday, June 8, 2020 at 1:26 PM
*To: *"users@royale.apache.org" , Alex Harui 


*Subject: *Re: Compiler warnings !

Actually they are xml objects.


    
        
            SENSORDATA_HOURLY
        
        
            0
            
                false
                false
                false
                false
                false
                false
false
                false
                true
            
        
    


So if I use as visible="{(data as 
XML).visualParams.commandabilityParams.isResumable == true}" may fix 
the warnings. Right ? Or still need “__NoChangeEvent__”.?


8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

1)Make sure none of the properties in the binding expression are
of type Object and that the instances support change events

2)Annotate the appropriate properties with
[Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is
Object.  If you are passing in a Foo as data, then the expression
should be:

visible="{(data as
Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain
Objects, the binding subsystem will watch for change events
correctly and the warning should go way.

Sometimes you do want to use a plain object where the individual
properties are not going to change.  You’ll change the entire
object instead of individual properties.  This is common in
renderers.  In such a case you can use the “__NoChangeEvent__”.

HTH,

-Alex

Re: Compiler warnings !

2020-06-09 Thread Alex Harui

I don’t know.  Try “as XML” and see if that solves the problem.

From: serkan 
Date: Monday, June 8, 2020 at 1:26 PM
To: "users@royale.apache.org" , Alex Harui 

Subject: Re: Compiler warnings !

Actually they are xml objects.

SENSORDATA_HOURLY

0

false
false
false
false
false
false
false
false
true

So if I use as visible="{(data as 
XML).visualParams.commandabilityParams.isResumable == true}" may fix the 
warnings. Right ? Or still need “__NoChangeEvent__”.?
8.06.2020 19:03 tarihinde Alex Harui yazdı:
There are two ways, depending on the scenario:

1)  Make sure none of the properties in the binding expression are of type 
Object and that the instances support change events

2)  Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is Object.  If you are 
passing in a Foo as data, then the expression should be:
visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain Objects, the 
binding subsystem will watch for change events correctly and the warning should 
go way.

Sometimes you do want to use a plain object where the individual properties are 
not going to change.  You’ll change the entire object instead of individual 
properties.  This is common in renderers.  In such a case you can use the 
“__NoChangeEvent__”.

HTH,
-Alex

From: serkan <mailto:ser...@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
Date: Monday, June 8, 2020 at 7:44 AM
To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
Subject: Compiler warnings !

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan

Re: Compiler warnings !

2020-06-08 Thread serkan


Actually they are xml objects.


    
        
            SENSORDATA_HOURLY
        
        
            0
            
                false
                false
                false
                false
                false
                false
                false
                false
                true
            
        
    


So if I use as visible="{(data as 
XML).visualParams.commandabilityParams.isResumable == true}" may fix the 
warnings. Right ? Or still need “__NoChangeEvent__”.?


8.06.2020 19:03 tarihinde Alex Harui yazdı:


There are two ways, depending on the scenario:

 1. Make sure none of the properties in the binding expression are of
type Object and that the instances support change events
 2. Annotate the appropriate properties with
[Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is Object.  If 
you are passing in a Foo as data, then the expression should be:


visible="{(data as Foo).visualParams.commandabilityParams.isResumable 
== true}"


Then if visualParams and commandabilityParams are not plain Objects, 
the binding subsystem will watch for change events correctly and the 
warning should go way.


Sometimes you do want to use a plain object where the individual 
properties are not going to change. You’ll change the entire object 
instead of individual properties.  This is common in renderers.  In 
such a case you can use the “__NoChangeEvent__”.


HTH,

-Alex

*From: *serkan 
*Reply-To: *"users@royale.apache.org" 
*Date: *Monday, June 8, 2020 at 7:44 AM
*To: *"users@royale.apache.org" 
*Subject: *Compiler warnings !

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 
'isResumable'.


visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan

Re: Compiler warnings !

2020-06-08 Thread Alex Harui

There are two ways, depending on the scenario:


  1.  Make sure none of the properties in the binding expression are of type 
Object and that the instances support change events
  2.  Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

This expression looks like itemRenderer code and “data” is Object.  If you are 
passing in a Foo as data, then the expression should be:
visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

Then if visualParams and commandabilityParams are not plain Objects, the 
binding subsystem will watch for change events correctly and the warning should 
go way.

Sometimes you do want to use a plain object where the individual properties are 
not going to change.  You’ll change the entire object instead of individual 
properties.  This is common in renderers.  In such a case you can use the 
“__NoChangeEvent__”.

HTH,
-Alex

From: serkan 
Reply-To: "users@royale.apache.org" 
Date: Monday, June 8, 2020 at 7:44 AM
To: "users@royale.apache.org" 
Subject: Compiler warnings !

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

 
visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan

Re: Compiler warnings !

2020-06-08 Thread serkan


Thanks Carlos,

Serkan

8.06.2020 17:49 tarihinde Carlos Rovira yazdı:

Hi,

it would be good to have some @ comment to disable per case, but 
currently you can only turn all on/off:


https://apache.github.io/royale-docs/compiler/compiler-options.html#show-binding-warnings




El lun., 8 jun. 2020 a las 16:44, serkan (>) escribió:


Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to
'isResumable'.

visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan



--
Carlos Rovira
http://about.me/carlosrovira

Re: Compiler warnings !

2020-06-08 Thread Carlos Rovira

Hi,

it would be good to have some @ comment to disable per case, but currently
you can only turn all on/off:

https://apache.github.io/royale-docs/compiler/compiler-options.html#show-binding-warnings




El lun., 8 jun. 2020 a las 16:44, serkan ()
escribió:

> Hi,
>
> Is it possble to get rid of these warnings ?
>
> Warning: Data binding will not be able to detect assignments to
> 'isResumable'.
>
>
> visible="{data.visualParams.commandabilityParams.isResumable == true}"
>
> Thanks,
> Serkan
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: compiler warnings related with image visibility

2020-03-18 Thread Serkan Taş


What do you think Harbs?

17.03.2020 08:53 tarihinde Alex Harui yazdı:


I think that may be a valid set of warnings. @Harbs 
<mailto:harbs.li...@gmail.com> may know better as to whether there are 
change events in JS XML or not.


-Alex

*From: *Serkan Taş 
*Reply-To: *"users@royale.apache.org" 
*Date: *Monday, March 16, 2020 at 10:45 PM
*To: *"users@royale.apache.org" 
*Subject: *Re: compiler warnings related with image visibility

[Bindable]
public var data:XML

17.03.2020 08:15 tarihinde Alex Harui yazdı:

What class or XML has the visualParams property?

*From: *Serkan Taş 
<mailto:serkan@likyateknoloji.com>
*Reply-To: *"users@royale.apache.org"
<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
*Date: *Monday, March 16, 2020 at 9:42 PM
*To: *"users@royale.apache.org" <mailto:users@royale.apache.org>
 <mailto:users@royale.apache.org>, Carlos
Rovira  <mailto:carlosrov...@apache.org>
*Subject: *Re: compiler warnings related with image visibility

Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?

16.03.2020 12:35 tarihinde Carlos Rovira yazdı:

Hi Serkan,

for example in a renderer people use to do something like that:

[Bindable("dataChange")]

public

functionget

iconList():IconListVO

{

returndata

asIconListVO;

}

so you bind in this case to iconList, and IconListVO has
[Bindable] metadata at class level

HTH

Carlos

El lun., 16 mar. 2020 a las 8:49, Serkan Taş
(mailto:serkan@likyateknoloji.com>>) escribió:

For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML







Thanks,
Serkan


-- 


Carlos Rovira

http://about.me/carlosrovira

<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cc933e9d3379b457470f508d7ca365a4a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637200207109140930=WupyeJbZcxKAqPm0YEQCrIIMb4Bnasib0cQaX51OTqY%3D=0>

Re: compiler warnings related with image visibility

2020-03-17 Thread Serkan Taş


Thank Aelx,

Serkan.

17.03.2020 08:53 tarihinde Alex Harui yazdı:


I think that may be a valid set of warnings. @Harbs 
<mailto:harbs.li...@gmail.com> may know better as to whether there are 
change events in JS XML or not.


-Alex

*From: *Serkan Taş 
*Reply-To: *"users@royale.apache.org" 
*Date: *Monday, March 16, 2020 at 10:45 PM
*To: *"users@royale.apache.org" 
*Subject: *Re: compiler warnings related with image visibility

[Bindable]
public var data:XML

17.03.2020 08:15 tarihinde Alex Harui yazdı:

What class or XML has the visualParams property?

*From: *Serkan Taş 
<mailto:serkan@likyateknoloji.com>
*Reply-To: *"users@royale.apache.org"
<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
*Date: *Monday, March 16, 2020 at 9:42 PM
*To: *"users@royale.apache.org" <mailto:users@royale.apache.org>
 <mailto:users@royale.apache.org>, Carlos
Rovira  <mailto:carlosrov...@apache.org>
*Subject: *Re: compiler warnings related with image visibility

Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?

16.03.2020 12:35 tarihinde Carlos Rovira yazdı:

Hi Serkan,

for example in a renderer people use to do something like that:

[Bindable("dataChange")]

public

functionget

iconList():IconListVO

{

returndata

asIconListVO;

}

so you bind in this case to iconList, and IconListVO has
[Bindable] metadata at class level

HTH

Carlos

El lun., 16 mar. 2020 a las 8:49, Serkan Taş
(mailto:serkan@likyateknoloji.com>>) escribió:

For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML







Thanks,
Serkan


-- 


Carlos Rovira

http://about.me/carlosrovira

<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cc933e9d3379b457470f508d7ca365a4a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637200207109140930=WupyeJbZcxKAqPm0YEQCrIIMb4Bnasib0cQaX51OTqY%3D=0>

Re: compiler warnings related with image visibility

2020-03-16 Thread Alex Harui

I think that may be a valid set of warnings.  
@Harbs<mailto:harbs.li...@gmail.com> may know better as to whether there are 
change events in JS XML or not.

-Alex



From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, March 16, 2020 at 10:45 PM
To: "users@royale.apache.org" 
Subject: Re: compiler warnings related with image visibility

[Bindable]
public var data:XML
17.03.2020 08:15 tarihinde Alex Harui yazdı:
What class or XML has the visualParams property?

From: Serkan Taş 
<mailto:serkan@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>
Date: Monday, March 16, 2020 at 9:42 PM
To: "users@royale.apache.org"<mailto:users@royale.apache.org> 
<mailto:users@royale.apache.org>, Carlos Rovira 
<mailto:carlosrov...@apache.org>
Subject: Re: compiler warnings related with image visibility

Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?
16.03.2020 12:35 tarihinde Carlos Rovira yazdı:
Hi Serkan,

for example in a renderer people use to do something like that:


[Bindable("dataChange")]

public
function get
iconList():IconListVO

{

return data
as IconListVO;

}


so you bind in this case to iconList, and IconListVO has [Bindable] metadata at 
class level

HTH

Carlos


El lun., 16 mar. 2020 a las 8:49, Serkan Taş 
(mailto:serkan@likyateknoloji.com>>) 
escribió:
For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML

[cid:image001.png@01D5FBE5.B7236390]


[cid:image002.png@01D5FBE5.B7236390]


Thanks,
Serkan


--
Carlos Rovira
http://about.me/carlosrovira<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Cc933e9d3379b457470f508d7ca365a4a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637200207109140930=WupyeJbZcxKAqPm0YEQCrIIMb4Bnasib0cQaX51OTqY%3D=0>

Re: compiler warnings related with image visibility

2020-03-16 Thread Serkan Taş


[Bindable]
public var data:XML

17.03.2020 08:15 tarihinde Alex Harui yazdı:


What class or XML has the visualParams property?

*From: *Serkan Taş 
*Reply-To: *"users@royale.apache.org" 
*Date: *Monday, March 16, 2020 at 9:42 PM
*To: *"users@royale.apache.org" , Carlos 
Rovira 

*Subject: *Re: compiler warnings related with image visibility

Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?

16.03.2020 12:35 tarihinde Carlos Rovira yazdı:

Hi Serkan,

for example in a renderer people use to do something like that:

[Bindable("dataChange")]

public

functionget

iconList():IconListVO

{

returndata

asIconListVO;

}

so you bind in this case to iconList, and IconListVO has
[Bindable] metadata at class level

HTH

Carlos

El lun., 16 mar. 2020 a las 8:49, Serkan Taş
(mailto:serkan@likyateknoloji.com>>) escribió:

For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML







Thanks,
Serkan


-- 


Carlos Rovira

http://about.me/carlosrovira

<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Ceb338cde9e644befc43608d7ca2d866d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637200169194667245=ZAf11ggS8hnTQI4gMDjsErD7xQulNWeB61L0YusjJSo%3D=0>

Re: compiler warnings related with image visibility

2020-03-16 Thread Alex Harui

What class or XML has the visualParams property?

From: Serkan Taş 
Reply-To: "users@royale.apache.org" 
Date: Monday, March 16, 2020 at 9:42 PM
To: "users@royale.apache.org" , Carlos Rovira 

Subject: Re: compiler warnings related with image visibility

Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?
16.03.2020 12:35 tarihinde Carlos Rovira yazdı:
Hi Serkan,

for example in a renderer people use to do something like that:


[Bindable("dataChange")]

public
function get
iconList():IconListVO

{

return data
as IconListVO;

}


so you bind in this case to iconList, and IconListVO has [Bindable] metadata at 
class level

HTH

Carlos


El lun., 16 mar. 2020 a las 8:49, Serkan Taş 
(mailto:serkan@likyateknoloji.com>>) 
escribió:
For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML

[cid:image001.png@01D5FBE0.61997270]


[cid:image002.png@01D5FBE0.61997270]


Thanks,
Serkan


--
Carlos Rovira
http://about.me/carlosrovira<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Ceb338cde9e644befc43608d7ca2d866d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637200169194667245=ZAf11ggS8hnTQI4gMDjsErD7xQulNWeB61L0YusjJSo%3D=0>

Re: compiler warnings related with image visibility

2020-03-16 Thread Serkan Taş


Hi Carlos,

I am not sure how to implement in my case.

How can bind to Image ?

16.03.2020 12:35 tarihinde Carlos Rovira yazdı:

Hi Serkan,

for example in a renderer people use to do something like that:

[Bindable("dataChange")]
public function get iconList():IconListVO
{
return data as IconListVO;
}

so you bind in this case to iconList, and IconListVO has [Bindable] 
metadata at class level


HTH

Carlos


El lun., 16 mar. 2020 a las 8:49, Serkan Taş 
(>) escribió:


For the source below I get some warnings. How can I avoid ?


[Bindable]
public var data:XML







Thanks,
Serkan



--
Carlos Rovira
http://about.me/carlosrovira

Re: compiler warnings related with image visibility

2020-03-16 Thread Carlos Rovira

Hi Serkan,

for example in a renderer people use to do something like that:

[Bindable("dataChange")]
public function get iconList():IconListVO
{
return data as IconListVO;
}

so you bind in this case to iconList, and IconListVO has [Bindable]
metadata at class level

HTH

Carlos


El lun., 16 mar. 2020 a las 8:49, Serkan Taş ()
escribió:

> For the source below I get some warnings. How can I avoid ?
>
>
> [Bindable]
> public var data:XML
>
>
>
>
>
>
>
> Thanks,
> Serkan
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: Compiler warnings !

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

Re: compiler warnings related with image visibility

17 matches

Site Navigation

Mail list logo

Footer information