Hi Team, Actually, after looking at the experimental CallOut code, it's 95% similar to the original Callout.
I don't know the story from the beginning, but I think it has been monkey-patched because the properties "actualHorizontalPosition" and "actualVerticalPosition" were protected, to make them accessible (mx_internal). So now that I know how to change and recompile the SDK :-), I just made that simple change (ie protected => mx_internal) in the original Callout class, and I can know use it in desktop (ie the callout pops up) Of course, I used a dumb Skin, to it does not look like a callout at all, but it should be feasible to adapt the experimental CallOutSkin to make it work on the original class. And it probably needs some more testing to make sure it works fine. So maybe we don't even need two classes, after all. After all, all other spark components (List, Panel, etc..) have the same hostComponent , and only differ by their skin on mobile and desktop platforms. What do you think? Maurice -----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : dimanche 6 octobre 2013 18:54 À : dev@flex.apache.org Objet : Re: Issue with CallOut ASDOC On Oct 6, 2013 9:13 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: > > Hi Team, > > I have noticed some classes asdoc link is broken on flex.apache.org/asdoc > > https://issues.apache.org/jira/browse/FLEX-33802 > > I propose an explanation and two possible fixes , but not sure what to do, because I don't know how the release builds are done and deployed. > > Can you please confirm/contradict the proposed explanation and which fix should be implemented. +1 for renaming the fault class names. Thanks for catching this! Om > > Regards, > > Maurice Amsellem > SYSTAR R&D - BusinessBridgeFX >
