It's safe to say we don't know if AS is faster than MXML until we have the
data. It may be that MXML allows databinding and that is slower than
manually setting the values in AS3 in the renderer's data setter. So MXML
renderers can more easily get bogged down where as in AS3 you would
typically be
Hi there,
Can you kindly help me solve the runtime error I’m getting? I’m not able to
figure out why I get that error.
I have a Flex 3.6 application, which has a TabNavigator in main application:
Hi, I have a little issue with the default TextInput component, could not
find it in already logged issues - at least I think so, there are a lot of
issues about text input components.
This is the scenario:
1) the component instance start with editable="false"
2) user moves focus to component usi
Probably that's not new for the most of you but for those who have not noticed
it until now (like me):
Since FlashPlayer 11.3 full keyboard input is possible in fullscreen mode and
that's marvellous!
I'm so excited about this "new" feature that I want to share it with you;-)
Here's an example:
h
Hi,
Cool...thanks for sharing.
Regards,
Sugan
-Original Message-
From: Krüger, Olaf [mailto:okrue...@edscha.com]
Sent: 19 September 2013 12:57 PM
To: users@flex.apache.org
Subject: Interactive Fullscreen since FlashPlayer 11.3
Probably that's not new for the most of you but for those
Jiem,
It may still be worth looking at the addAllAt patch since addAll uses
addAllAt. Although you say you call addAll in a non-related part of your
code, I am sure the framework uses addAllAt internally.
Sorry to harp on about this patch; but until I applied it I was
experiencing an extremely si
OK glad to know that addAll calls addAllAt, could explains my troubles.
I have replaced my call to addAll by a for each loop and calls to addItem().
addItem() is safe, isn't it?
I prefer doing this than modifying the Flex SDK.
--
View this message in context:
http://apache-flex-users.246.n4
Hello.
In our code, someone has implemented a custom spark text area, that
attempts to resize based on the number of lines in the text.
Snippet-ish:
...
private function updateCompleteHandler(event:FlexEvent):void {
textFlow.flowComposer.composeToPosition();
var actualNumOfLines: int = tex
There's a difference between being "not visible" and "not being on the
display list".
AFAIK, you can be hidden by scrollbars, masks, and just about anything
else, but if you are on the display list (which doesn't mean on stage
either, just that there is a chain of parenting going back up to the
App
That was hard to follow, but remember that when you remove something from
an array or list of children, things get re-indexed and the length changes
On 9/19/13 12:19 AM, "Deepak MS" wrote:
>Hi there,
>
>Can you kindly help me solve the runtime error I¹m getting? I¹m not able
>to
>figure out why
Might be best to not allow focus if the control is not editable. Set
tabEnabled and/or focusEnabled=false.
On 9/19/13 2:45 AM, "Cosma Colanicchia" wrote:
>Hi, I have a little issue with the default TextInput component, could not
>find it in already logged issues - at least I think so, there are
Thank you Alex, but unfortunately the text input has to be focusable
because it is part of a complex search component: it accept a query text
and, on return, display a popup list of results, once selected the text
input become not editable and display the selected item. In other words,
the user mov
What is stage.focus? Maybe just assign it to the RichEditableText.
On 9/19/13 9:40 AM, "Cosma Colanicchia" wrote:
>Thank you Alex, but unfortunately the text input has to be focusable
>because it is part of a complex search component: it accept a query text
>and, on return, display a popup list
On 9/19/13 12:23 AM, "flexcapaci...@gmail.com"
wrote:
>It's safe to say we don't know if AS is faster than MXML until we have the
>data.
We do know that when we switched from MXML skins to AS skins things got
much faster. And the same for renderers, but we did not analyze why. If
you compare
Jiem,
addItem should be safe, yes. However, I was experiencing a similar (if not
the same - im working from memory here) stack when I was removing and
adding a single item from the stage once a popup had closed. Updating the
SDK fixed my issue. I don't know for sure but addAll / addAllAt _must_ be
Yes, I used it and it greatly helped.
But now I am thinking to take my control to the next level. I want to
change a width of a column. Is it going to be possible?
Thanks
On Wed, Sep 18, 2013 at 9:09 AM, Tom Chiverton wrote:
> On 18/09/2013 12:24, mark goldin wrote:
>
>> Can you please elabora
Sorry for my english mistakes, was in a rush when I typed :-)
I wanted to add that what's most bothering is that I could pass through this
code 10 times without crashing. Only sometimes, this exception will happen,
maybe there's some code elsewhere that corrupts this addChild's behavior.
--
View
The Flex framework is a layer over the Flash Player. The SystemManager is
the framework's wrapper of the Flash 'root'. You are supposed to only use
Flex APIs and avoid low-level, unwrapped Flash APIs unless you really know
what you are doing.
I can't see anything wrong with the code snippets you
Yes that's something I have figured out 3 years ago when I started to work
on this project. Oh god it was a pain when I understood how bad Flex mixes
with basic AS3 and its APIs. But I don't give up easily and today it's
probably one the biggest game project using Flex (http://faeria.net/).
GAME c
You could add event listeners to root to see if it is changing
unexpectedly.
Good luck,
-Alex
On 9/19/13 3:50 PM, "Jiem" wrote:
>Yes that's something I have figured out 3 years ago when I started to work
>on this project. Oh god it was a pain when I understood how bad Flex mixes
>with basic AS3
I have this other stack trace (before the crash would appear for 2 different
reason, now only this one seems to be left as I fixed the Menu):
RangeError: Error #2006: L'index indiqué sort des limites.
at flash.display::DisplayObjectContainer/addChildAt()
at
mx.managers::SystemManag
21 matches
Mail list logo
