You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2014/05/31 04:08:02 UTC
[jira] [Closed] (TAP5-146) Provide some way to get the component
that fired an event
[ https://issues.apache.org/jira/browse/TAP5-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo closed TAP5-146.
----------------------------------------------
Resolution: Won't Fix
I didn't had any need for this in the last years, so I'll close it.
> Provide some way to get the component that fired an event
> ---------------------------------------------------------
>
> Key: TAP5-146
> URL: https://issues.apache.org/jira/browse/TAP5-146
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Thiago H. de Paula Figueiredo
> Labels: bulk-close-candidate
>
> It would be very nice to have event handler methods know what component fired that event, specially for mixins.
> There's a discussion in the mailing list: http://www.nabble.com/forum/ViewPost.jtp?post=18157269&framed=y.
> Howard said:
> We could change Event to expose the source
> Component ... we could also change the EventWorker logic to see if the
> sole parameter to an event handler method is of type ComponentEvent
> and pass the event directly to the event handler method.
--
This message was sent by Atlassian JIRA
(v6.2#6252)