Thank you for the information
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : lundi 18 novembre 2013 18:58
À : dev@flex.apache.org
Objet : Re: Air Stage Text Issue
I asked him today. He pretty much confirmed what I said. The AIR team was in
the proce
yé : samedi 16 novembre 2013 19:32
>À : dev@flex.apache.org
>Objet : Re: Air Stage Text Issue
>
>I can try to ask the engineer who worked on it to see if he remembers,
>but I would guess the following:
>
>1) There was hope that AIR would provide a solution
>2) I'
ilto:aha...@adobe.com]
Envoyé : samedi 16 novembre 2013 19:32
À : dev@flex.apache.org
Objet : Re: Air Stage Text Issue
I can try to ask the engineer who worked on it to see if he remembers, but I
would guess the following:
1) There was hope that AIR would provide a solution
2) I'm not sure p
at
would help us a lot.
Thnaks
Maurice
-Message d'origine-
De : Flexicious.com [mailto:flexici...@gmail.com]
Envoyé : dimanche 17 novembre 2013 19:59
À : dev@flex.apache.org
Objet : Re: Air Stage Text Issue
Couple of things - it appears that in your test case, the textDisplay is
skinClass="skins.ExtendedStageTextInputSkin"/>
>
>
>
>
>
>
>
>
> -Message d'origine-
> De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> Envoyé : dimanche 17 novembre 2013 18:34
> À : dev@flex.apache.org
&
r.com]
Envoyé : dimanche 17 novembre 2013 18:34
À : dev@flex.apache.org
Objet : RE: Air Stage Text Issue
Ok, thanks.
I am too advanced now in my implementation to drop everything and use your code
instead, but I will keep it in case I get into a deadlock.
And of course, I will use it as a refe
om]
> Envoyé : dimanche 17 novembre 2013 17:31
> À : dev@flex.apache.org
> Objet : Re: Air Stage Text Issue
>
> For what its worth, we have a skin that solves the issue atleast for our
> scenarios.
>
> http://blog.flexicious.com/post/Scrolling-Issues-With-TextInput-for-Flex-A
om]
Envoyé : dimanche 17 novembre 2013 18:28
À : dev@flex.apache.org
Objet : Re: Air Stage Text Issue
Yes, it seems to work on iPad 2/3/4 as well as Samsung Galaxy Tab 2 . Have not
tested on phones, but doubt it should be different. It is not a perfect
solution, but for the subset of scenario
'origine-
> De : Flexicious.com [mailto:flexici...@gmail.com]
> Envoyé : dimanche 17 novembre 2013 17:31
> À : dev@flex.apache.org
> Objet : Re: Air Stage Text Issue
>
> For what its worth, we have a skin that solves the issue atleast for our
> scenarios.
>
> http:
h and that the
resulting code is so simple.
Don't you have some side effects ? does it work on Android as well?
Maurice
-Message d'origine-
De : Flexicious.com [mailto:flexici...@gmail.com]
Envoyé : dimanche 17 novembre 2013 17:31
À : dev@flex.apache.org
Objet : Re: Air Stage
For what its worth, we have a skin that solves the issue atleast for our
scenarios.
http://blog.flexicious.com/post/Scrolling-Issues-With-TextInput-for-Flex-Air-Mobile-Native-StageText.aspx
.
It may not be the best workaround, but its better than what we had. For us,
it was not only scrolling, but
OK, good luck.
On 11/17/13 7:54 AM, "Maurice Amsellem"
wrote:
>>And note that, in most cases, the next best solution is to modify the
>>application code so that scrolling is not needed. Just have more
>>screens that you can swipe between.
>>That kind of modification might be better than trying
>And note that, in most cases, the next best solution is to modify the
>application code so that scrolling is not needed. Just have more screens that
>you can swipe between.
>That kind of modification might be better than trying to implement code that
>makes sure text inputs don't get partial
On 11/17/13 2:59 AM, "Maurice Amsellem"
wrote:
>>What I am saying to myself to get some motivation to go ahead, is that
>>the "partial occluding" issue could be solved by modifying the
>>application code, so that nothing comes in the way
>Of the edited text.
And note that, in most cases, the ne
-Message d'origine-
De : jude [mailto:flexcapaci...@gmail.com]
Envoyé : dimanche 17 novembre 2013 04:44
À : dev
Objet : Re: Air Stage Text Issue
I don't understand that use case. In the suggested scenario, you have a bitmap
all the time except if the TextInput has focus. Once it h
d text.
But I know that it won't prevent people from coming to this forum (because the
other Flex fora are not active) and calling us names :-(
At least, I will try to...
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : dimanche 17 novembre
On 11/16/13 7:44 PM, "flexcapaci...@gmail.com"
wrote:
>I don't understand that use case. In the suggested scenario, you have a
>bitmap all the time except if the TextInput has focus. Once it has focus
>you would show the StageText. This is the same time that the virtual
>keyboard pops up. I don
On 11/16/13 4:52 PM, "Maurice Amsellem"
wrote:
>>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 to
I don't understand that use case. In the suggested scenario, you have a
bitmap all the time except if the TextInput has focus. Once it has focus
you would show the StageText. This is the same time that the virtual
keyboard pops up. I don't think there's any other way except the it behaves
now. I do
novembre 2013 01:07
À : dev@flex.apache.org
Objet : Re: Air Stage Text Issue
On 11/16/13 12:19 PM, "Maurice Amsellem"
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 T
On 11/16/13 12:19 PM, "Maurice Amsellem"
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
]
Envoyé : samedi 16 novembre 2013 19:35
À : dev@flex.apache.org
Objet : RE: Air Stage Text Issue
>But before you go work on that, can you look at the most recent mustella
>failures? I think there is a new DataGrid failure.
sure
-Message d'origine-
De : Alex Harui [mailto:aha.
>But before you go work on that, can you look at the most recent mustella
>failures? I think there is a new DataGrid failure.
sure
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : samedi 16 novembre 2013 19:32
À : dev@flex.apache.org
Objet : Re: Air
I can try to ask the engineer who worked on it to see if he remembers, but
I would guess the following:
1) There was hope that AIR would provide a solution
2) I'm not sure proxying would handle text selection.
3) I'm not sure proxying would handle partially occluded text inputs.
You're welcome to
Hi,
I am currently working on the issue about StageTextInput not scrolling on
mobile:
https://issues.apache.org/jira/browse/FLEX-33166
Debugging the SDK source code, it appears that "proxying" the StageTextInput
with a bitmap is already in place (see class StyleableStageText).
However, the
This may work for you:
http://blogs.adobe.com/cantrell/archives/2011/09/native-text-input-with-stagetext.html
On 30/09/2013 03:28, Flexicious.com wrote:
This may not be a Flex/Apache issue, but just wanted to see if anyone has
been successful with text on Air mobile.
The issue basically revolv
Yup saw that - should resolve the issue with the scroller getting out of
whack. Probably will make scrolling expensive, but alteast usable. but
still has the issue of the text showing through stuff (like dropdowns and
popups and such). So basically we need to evaulate objects underneath these
popup
Not so much gracefully but this might help,
http://stackoverflow.com/questions/14412301/flex-textarea-and-textinput-on-mobile-not-positioning-correctly.
On Sun, Sep 29, 2013 at 9:28 PM, Flexicious.com wrote:
> This may not be a Flex/Apache issue, but just wanted to see if anyone has
> been su
This may not be a Flex/Apache issue, but just wanted to see if anyone has
been successful with text on Air mobile.
The issue basically revolves around the native text input. It is rendered
on top of the display list, and it does not scroll within its parent
scroller. So dropdowns and such that ren
29 matches
Mail list logo
