Re: flatspark bug on default button

2016-07-20 Thread Vincent Sotto
> > > width="213" > height="{ButtonSizeEnum.Large}" > > brand="{BrandColorEnum.Primary}" /> > width="213"

Re: flatspark bug on default button

2016-07-20 Thread OK
{ skinClass: ClassReference("flatspark.skins.ButtonIconSkin"); } [2]: https://forums.adobe.com/thread/880144 -- View this message in context: http://apache-flex-development.247.n4.nabble.com/flatspark-bug-on-default-button-tp54000p54033.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: flatspark bug on default button

2016-07-20 Thread Vincent Sotto
width="213" >> height="{ButtonSizeEnum.Large}" >> >> brand="{BrandColorEnum.Primary}" >> skinClass="flatspark.skins.ButtonIconSkin"/> >> >width

Re: flatspark bug on default button

2016-07-20 Thread Vincent Sotto
d="{BrandColorEnum.Primary}" > skinClass="flatspark.skins.ButtonIconSkin"/> > width="213" > height="{ButtonSizeEnum.Large}" > > brand="{BrandColorEnum.Primary}

Re: flatspark bug on default button

2016-07-19 Thread OK
- View this message in context: http://apache-flex-development.247.n4.nabble.com/flatspark-bug-on-default-button-tp54000p54028.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: flatspark bug on default button

2016-07-19 Thread Vincent Sotto
for whatever reason. > Could you provide some test code or could you create a JIRA ticket? > > Thanks, > Olaf > > > > -- > View this message in context: > http://apache-flex-development.247.n4.nabble.com/flatspark-bug-on-default-button-tp54000p54003.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >

Re: flatspark bug on default button

2016-07-19 Thread OK
om/flatspark-bug-on-default-button-tp54000p54003.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

flatspark bug on default button

2016-07-18 Thread Vincent Sotto
theres a bug when i set a buttonicon as default button of a form, the skin changes back to default spark. any workaround on this issue or is this already reported? thank you