On Thu, Oct 27, 2011 at 07:00, Burak Arslan <burak.ars...@arskom.com.tr>wrote:
> hi,
>
> calling fireImmediateEvent with no target argument used to work in 1.4,
> but it doesn't in 1.5. is this intentional, or should I file a bug?
>
> the call to fireImmediateEvent crashes at getFriendlyName function,
> called from here:
>
> https://github.com/qooxdoo/qooxdoo/blob/master/framework/source/class/qx/util/fsm/FiniteStateMachine.js#L699
Hi Burak,
I don't recall making any change to that effect. The target parameter is not
documented as optional, and I don't think it ever was.
I am trying to figure out what you'd expect to happen. Events are fired on
(target) objects. What does it mean to fire an event on an undefined target
object? What used to happen when you fired an event with no target?
I suspect something else is going on here other than what you think it is.
One change that was made, probably between 1.4 and 1.5, was that the
transitions and states can have a "context" member in their configuration
map, which specifies the context in which the functions such as
ontransition, onentry, etc. should be called. It's possible that I
erroneously altered the the default (no context member) context so that it
doesn't work like it used to, but I'm not sure how that could be affecting
the particular issue that you're having...???
Derrell
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
