>Suppose you have a TextInput that scrolls so all but the top 10 pixels are >visible. Are you going to show the bitmap or the StageText when they give it >focus? I think you have to show the >StageText in which case it will float >over the top and look bad. Same if there is a floating dialog or icon that >partially obscures the TextInput when it has focus.
Got it, thanks for the explanations. For point #1 (TI scrolled to top): - One possibility would be to prevent editing when text in partially obscured. - Another would be to scroll it back to view, so that it's not obscured anymore. For point #2 ( TI partially obscured by floating component): - I think it should be possible to detect that the text is occluded, and prevent editing in this case. Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : dimanche 17 novembre 2013 01:07 À : dev@flex.apache.org Objet : Re: Air Stage Text Issue On 11/16/13 12:19 PM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >>3) I'm not sure proxying would handle partially occluded text inputs. >What do you mean, by partially occluded text input ? >Is it that the TextInput is clipped or that there is something in front ? Either. > >I don't understand why this would be an issue with bitmap proxying. >Can you please elaborate. Suppose you have a TextInput that scrolls so all but the top 10 pixels are visible. Are you going to show the bitmap or the StageText when they give it focus? I think you have to show the StageText in which case it will float over the top and look bad. Same if there is a floating dialog or icon that partially obscures the TextInput when it has focus. -Alex
