See if you can do a "Step return" after the error until you actually
get code. That might help you isolate what is causing the error.
Richard Rodseth wrote:
Hi Jeff. Yes, my event classes do descend from Event. I've also run in
debug mode, but you don't get a
stack crawl on the 1034. It ju
m] On
Behalf Of Jeffry Houser
Sent: Tuesday, February 03, 2009 7:54 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Another 1034 - events and event types
A single event class being used for multiple events is common within
the Flex Framework; why recommend not re-using the same type?
"activate" event -- other names seemed safe though,
> depending on what component your DateRangePicker is being extended from.
>
>
>
> HTH,
>
> Ryan
>
> *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On
> Behalf Of *Richard Rodseth
>
odseth
Sent: Tuesday, February 03, 2009 5:59 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Another 1034 - events and event types
Hi Jeff. Yes, my event classes do descend from Event. I've also run in
debug mode, but you don't get a
stack crawl on the 1034. It just says &q
It's a little hard to be certain, since the error was not 100% reproducible,
but it appears that it occurred if I used "activate" for my pickers, meaning
"focusIn". If I used "focusIn" I ran into a different coercion failure
(perhaps because the pickers derive from Box).
For the moment "focusInPic
Hi Jeff. Yes, my event classes do descend from Event. I've also run in debug
mode, but you don't get a
stack crawl on the 1034. It just says "main thread".
On Tue, Feb 3, 2009 at 4:54 PM, Jeffry Houser wrote:
>
> A single event class being used for multiple events is common within the
> Flex Fr
A single event class being used for multiple events is common within
the Flex Framework; why recommend not re-using the same type?
Back to the problem:
Are you sure that your event class extends flash.events.Event ? I
might expect odd errors if not.
Have you tried running the code in debug
I see that Tree dispatches a "change" which is of type ListEvent, whereas
Button, Checkbox etc dispatch a "change" of type Event.
So if I can use "changePicker" in a variety of my components, rather than
"changeDate", "changeAddress" etc., why not just "change".
It's a little hard to debug, since
As Flex, or as any others within the app?
On Tue, Feb 3, 2009 at 4:25 PM, Tracy Spratt wrote:
>I would not use the same type name.
>
>
>
> Tracy Spratt
> Lariat Services
>
> Flex development bandwidth available
> --
>
> *From:* flexcoders@yahoogroups.com [mailto
I would not use the same type name.
Tracy Spratt
Lariat Services
Flex development bandwidth available
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of Richard Rodseth
Sent: Tuesday, February 03, 2009 6:11 PM
To: flexcoders@
10 matches
Mail list logo