On 3/22/13 5:47 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
> Hi,
>
>> True, but in theory some Flash-based button could implement just enough to
>> play in this game.
>
> Would it use the IButton interface in this case? It's not exactly
> representative of what a button interface would be IMO it consists of
> emphasised (would a graphical button use this?), callLater (why is this here?)
> and now the label setter and getter.
>
> About the only place the interface is used in the SDK is in the Focus Manager
> which set emphasised to true/false on the default button.
>
> Someone asked for it so it was important to them. We should either keep the
> change or reject it and either way close the JIRA issue.
>
I hadn't looked at what was already in IButton. Not sure why callLater is
in there. It is supposed to be the interface for emphasized
Anyway, it occurs to me that to change an interface invites potential
backward compatibility issues. Probably low probability but just want to
point that out.
Honestly, I don't care whether you decide to keep it or not since the issues
are probably edge cases, I just wanted to point out the ramifications.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
