Hi Alex,
in the class file only flexjs event is imported, so it should be that one
and not flash event. If this is not what is happening, I think we have a
bug in the compiler. I should not need to use a fully qualified name each
time I use a event to ensure the right event. what do you think?
Alex,
I now tried to fully qualified the event thrown and the result is the same.
I uploaded the TextInput modifications in a commit
(dc2d8364393aa29df8c38f3fb91082bfab4f6036)
could you take a look and let me know what you think. I'm doing something
wrong? it's a bug?
(I uploaded some changes
I just looked at the doc this morning, and much to my surprise, the
TextField's change event bubbles. That doesn't make sense to me, but
that's probably the problem. So, you'll have to listen and
stopImmediatePropagation on that change event then things should work.
Please try that. If that
Hi Alex,
just tested the proposed fix but with no luck...type coercion continues
showing :(
2014-03-01 17:16 GMT+01:00 Alex Harui aha...@adobe.com:
I just looked at the doc this morning, and much to my surprise, the
TextField's change event bubbles. That doesn't make sense to me, but
Ok will try to look tonight. Did you verify that stop propagation got called
before the error?
Sent via the PANTECH Discover, an ATT 4G LTE smartphone.
Carlos Rovira carlos.rov...@codeoscopic.com wrote:
Hi Alex,
just tested the proposed fix but with no luck...type coercion continues
showing
I've only seen the fully qualified class when there is a conflict in the file.
Peter
On Mar 1, 2014, at 5:07 AM, Carlos Rovira carlos.rov...@codeoscopic.com
wrote:
Hi Alex,
in the class file only flexjs event is imported, so it should be that one
and not flash event. If this is not
Checked in something that seemed to work for me. Let me know if it still
isn't working for you.
On 3/1/14 10:45 AM, Alex Harui aha...@adobe.com wrote:
Ok will try to look tonight. Did you verify that stop propagation got
called before the error?
Sent via the PANTECH Discover, an ATT 4G LTE
Peter, Alex,
I'm having problems with this issue, since I think there's no reference to
flash.events.Event (I was already aware of this restriction) in my
modifications in TextInput, so all should be FlexJS events
(org.apache.flex.events.Event). A similar example is in CheckBox component.
What
In textChangeHandler, are you sure new Event will resolve to
org.apache.flex.events.Event and not flash.events.Event?
On 2/28/14 3:48 PM, Carlos Rovira carlosrov...@apache.org wrote:
Peter, Alex,
I'm having problems with this issue, since I think there's no reference to
flash.events.Event (I
Hi,
I'm having a problem with FlexJS events.
* In TodoListView (a extension of ViewBase) if I use in a component
something like: change=logTodo(event)
and the method is
public function logTodo(event:Event):void {
// something
}
a type coercion error is thrown that said
We're trying not to dispatch flash.events.Event in FlexJS (since there
isn't an equivalent in JS). So the change event should be dispatching
org.apache.flex.events.Event and the component's event metadata also needs
to say that it is dispatching an org.apache.flex.events.Event and the
event
If I understand what's happening, you should not have to use any Flex
event-related classes in your FlexJS code. They are used at a low-level in
the SDK, but developer-facing code should not need them. I would just
import org.apache.flex.events.Event and remove any imports for
flash.event.* - If
12 matches
Mail list logo
