Checked the .bad.png.
All are the same: sub-pixel shift when the action bar contains a text input.
This is because the text input now displays a bitmap instead of the StageText.
Although they have the same extent (because the bitmap is supposed to be a
pixel copy of the stageText), FP is probably
Yes, but didn't run all the mobile tests, only TextInput, TextArea and
StageText.
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : lundi 18 novembre 2013 08:47
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: [dev] Build failed in Jenkins: flex-sdk_mu
Hi,
Playing 'bad cop' here: did you run the mobile Mustella tests before
pushing the commits?
EdB
On Mon, Nov 18, 2013 at 8:41 AM, Maurice Amsellem
wrote:
> Analysing the failures...
>
> -Message d'origine-
> De : flex.muste...@gmail.com [mailto:flex.muste...@gmail.com]
> Envoyé : lun
Hey, don't kill the messenger ;-)
EdB
On Mon, Nov 18, 2013 at 8:26 AM, Justin Mclean wrote:
> Hi,
>
>> I don't think we need to use '12.0'. According to [1], from now on
>> Adobe will be updating the major build numbers for each release.
>
> And what if they release a security patch or fix an
Analysing the failures...
-Message d'origine-
De : flex.muste...@gmail.com [mailto:flex.muste...@gmail.com]
Envoyé : lundi 18 novembre 2013 05:38
À : comm...@flex.apache.org; e...@ixsoftware.nl; jmcl...@apache.org; Maurice
Amsellem
Objet : Build failed in Jenkins: flex-sdk_mustella-mobil
Hi,
> I don't think we need to use '12.0'. According to [1], from now on
> Adobe will be updating the major build numbers for each release.
And what if they release a security patch or fix an important issue?
Thanks,
Justin
I don't think we need to use '12.0'. According to [1], from now on
Adobe will be updating the major build numbers for each release. They
will also be giving AIR the same version number as FP on the next
release. So, after FP 12 and AIR 4, we'll get FP 13 and AIR 13.
EdB
1 : http://blogs.adobe.com
I don't think that's right. The 4th byte is the SWF version. The
enabling tool may have forced a newer SWF version, but that could happen
for other reasons.
I think you need to decode the SWF. There are SWF decoding classes in
modules/swfutils/src/. SWFDump just calls SwfxPrinter.java.
-Alex
Hi,
It may be the same place for the same swf with it turned on or off but not 100%
sure, certainly not something I'd rely on.
Justin
Ok ... so I just had another look,
- unpacked an swf that was not enabled
- then enabled that SWF
- unpacked that content
- loaded both files in a text-compare tool
So it seems that the difference is simplywithin the first 7 bytes
Not Enabled: FWS0J+
Enabed: FWS4J+
(There seems to be some sort
Oh, I see, Justin added it to swfutils. I was looking for it in falcon
since this is where I had added the support but I don't see the code in
Apache Flex's falcon.
-Darrell
On Sun, Nov 17, 2013 at 3:46 PM, Justin Mclean wrote:
> Hi,
>
> > I believe there was a new tag added to the swf to enab
Few notes before going to bed ;-) :
1) to help debug if something goes wrong on Android, you can set the following
mx_internal flag:
ScrollableStageText.debugProxyImage = true;
It will display the proxy bitmaps in magenta background.
2) proxy methods in ScrollableStageText has been abstracted
Run mustella tests:
Mobile/Components/TextInput
Mobile/components/TextArea
Mobile/StageText
All pass.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 18 novembre 2013 01:11
À : dev@flex.apache.org
Objet : RE: Mobile TextInput Implem
Hi, I have committed and pushed tentative fix for
https://issues.apache.org/jira/browse/FLEX-33166
Tested on iPad 2 / 3.
Not tested on Android.
I couldn't run mustella mobile tests. For some reason, they are broken on my
machine ( says: Passes: 0 / Fails: 0).
The new skins are now the defaul
Founds some bugs, so I won't commit until they are fixed...
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : dimanche 17 novembre 2013 21:18
À : dev@flex.apache.org
Objet : RE: Mobile TextInput Implementation status
>I can help out with And
Hi,
Missed setting the swf version in build.xml, I've fixed that and updated the
ide utilities.
Thanks,
Justin
Hi,
> I believe there was a new tag added to the swf to enable telemetry. I don't
> see this tag supported in Apache Flex.
The new tag in the swf is supported in Apache Flex (4.10 and 4.11) otherwise
how else could we support it?
The tags value is 93, so you can look for that or just use swfdu
>I can help out with Android testing.
Thanks
>Should I wait for the nightly or are these fixes on a branch? Nightly would
>be preferable so as to allow more people to test the fix.
I will push to the develop/ so that they be in the nightly
>It would be better to keep the old one around with
On Sun, Nov 17, 2013 at 11:42 AM, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:
> Well I want to be able to detect programmatically, if advanced telemetry
> is tuned on.
> I agree, running that in Scout would prove its presence, but I want to
> check this in flexmojos testsuite.
>
Well I want to be able to detect programmatically, if advanced telemetry is
tuned on.
I agree, running that in Scout would prove its presence, but I want to check
this in flexmojos testsuite.
@Darrell: As soon as I upgraded the FDK used by Flexmojos 7 to 4.10 this was
the first compiler versio
On Nov 17, 2013 10:56 AM, "Maurice Amsellem"
wrote:
>
> Hi,
>
> Here is a brief status of the implementation of Mobile Text Input, along
with some questions:
>
> Implementation overview:
> The change is mainly on the class StyleableStageText, which now takes the
opposite approach than the previous
>this wont work on the emulator, since it depends on
>SoftKeyboardEvent.SOFT_KEYBOARD_ACTIVATE and
>SoftKeyboardEvent.SOFT_KEYBOARD_DEACTIVATE events.
It doesn't work on the iPad either: scroll up and dow several times and you
will notice the TI sometimes shows and sometimes does not show while
Merci fred.
-Message d'origine-
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : dimanche 17 novembre 2013 20:07
À : dev@flex.apache.org
Objet : RE: [ANNOUNCE] Welcome Maurice as the newest PMC member
Congrats Maurice and good job, welcome on board !
-Message d'origine
Congrats Maurice and good job, welcome on board !
-Message d'origine-
De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Envoyé : jeudi 14 novembre 2013 10:59
À : dev@flex.apache.org
Objet : RE: [ANNOUNCE] Welcome Maurice as the newest PMC member
Congratulations and welcome !
:
Couple of things - it appears that in your test case, the textDisplay is of
0 width and height. If you debug through, you will notice that it does not
actually capture the screen shot. Second, this wont work on the emulator,
since it depends on SoftKeyboardEvent.SOFT_KEYBOARD_ACTIVATE and
SoftKeybo
Hi,
Here is a brief status of the implementation of Mobile Text Input, along with
some questions:
Implementation overview:
The change is mainly on the class StyleableStageText, which now takes the
opposite approach than the previous one:
- display proxy image bitmap by default
- display Sta
@Flexicious,
FYI, I have tried the ExtendedStageTextInputSkin and it does not solve at all
the scrolling problem:
- Simple code to show the issue below:
- Run the app even in the ADL, and scroll the Form: the TextInput stays in
place.
Can you confirm the behavior on your side ?
Run scout?
On Nov 17, 2013 7:01 PM, "Darrell Loverin"
wrote:
> I believe there was a new tag added to the swf to enable telemetry. I don't
> see this tag supported in Apache Flex.
>
>
> -Darrell Loverin
>
>
>
> On Sun, Nov 17, 2013 at 8:30 AM, christofer.d...@c-ware.de <
> christofer.d...@c-ware.
I’d like to propose a different view on the problem.
Many native mobile components provide a separate UI strategy for display
end edit: think of single and multiple selection controls, date and time
input controls, etc. Text input controls, in native applications, have a
mixed approach: sometimes,
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 reference implementation.
>It is not a perfect solution, but for the subset of scenarios that this
>current cl
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 scenarios that this current client cared
about, it seems to work.
On Sun, Nov 17, 2013 at 12:08 PM, Maurice Amse
Thank you Mr. Flexicious for the code :-)
I am taking pretty much the same approach, expect that I have encapsulated
StageText and ImageProxy in its own class, like in StyleableStageText.
That way, it can be reused in TextAreaStageSkin as well.
There is something I don't understand in your impl
I believe there was a new tag added to the swf to enable telemetry. I don't
see this tag supported in Apache Flex.
-Darrell Loverin
On Sun, Nov 17, 2013 at 8:30 AM, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:
> Hi,
>
> I have recently extedned Flexmojos to support the advanc
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
Yeah, I'd hold off on that for a bit. There was some wackyness with
the VM. Give it one more full run before taking action.
EdB
On Sun, Nov 17, 2013 at 4:51 PM, Alex Harui wrote:
> Looks like there is a second test failing that might have been masked by
> the first one. Can you look at the la
>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
Looks like there is a second test failing that might have been masked by
the first one. Can you look at the latest run's failure?
Thanks,
-Alex
On 11/16/13 12:09 PM, "mamsel...@apache.org" wrote:
>Updated Branches:
> refs/heads/develop fa12f02de -> 78eab008d
>
>
>FIXED broken mustella tests
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
Excellent! Thanks!
-Alex
On 11/17/13 3:33 AM, "Erik de Bruin" wrote:
>I now get a 'clean' publish on both the DataBindingTest and
>DataGridExample examples. No more warnings!
>
>And both projects now run correctly in 'release' mode as well.
>
>EdB
>
>
>
>On Sun, Nov 17, 2013 at 11:49 AM, wro
Hi,
I have recently extedned Flexmojos to support the advanced telemetry compiler
flag. Also I have created unit-tests that sort of test that functionality.
Unfortunately I can simply see that below flex 4.10 that flag is simply not
supported by the compiler. I can't however check if the file i
>There is code in Flex (or AIR?) that is clipping the StageText successfully
Not it does not, even if you set a viewport that is smaller that the StageText,
it will be displayed in its entirety, expected if clipped by the screen device,
which is not what we are talking about (see Alex comment).
I now get a 'clean' publish on both the DataBindingTest and
DataGridExample examples. No more warnings!
And both projects now run correctly in 'release' mode as well.
EdB
On Sun, Nov 17, 2013 at 11:49 AM, wrote:
> Updated Branches:
> refs/heads/develop 8482d7219 -> 753c7853a
>
>
> Found th
>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.
>Neither of these proposed solutions are 'perfect'. They will cause some
>grumbling from users
Thanks Justin.
I'd like to help with this, so I'll try to fix some bugs soon and submit
patch.
Piotr
-
Flex/Air developer open to new job offers and challenges.
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/SDK-4-11-service
45 matches
Mail list logo
