# Pass through mouse clicks

**URL:** <https://forum.inductiveautomation.com/t/pass-through-mouse-clicks/18080>\
**Category:** Ignition\
**Created:** [May 17, 2018, 7:19pm UTC](https://forum.inductiveautomation.com/t/pass-through-mouse-clicks/18080 "2018-05-17T19:19:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 17, 2018, 7:58pm UTC](https://forum.inductiveautomation.com/t/pass-through-mouse-clicks/18080/2 "2018-05-17T19:58:19Z")

</div>

Look at Kyle's suggestions here:

> [@Button Events Within Templates](http://forum.inductiveautomation.com/t/button-events-within-templates/14382/17):
>
> Here is how I do it. from java.awt.event import MouseEvent evt = MouseEvent(event.source.parent.parent,event.getID(),event.getWhen(),event.getModifiers(),event.x,event.y,event.clickCount,event.popupTrigger,event.button) event.source.parent.parent.dispatchEvent(evt) We take the originating event, from a label inside the template, and create a new instance of the mouse event, only changing the source. If we do not do this, then event.source will be equal to the triggering component inside the t…

Probably just need some coordinate transformations to go the other way.

---

_[View the full topic](https://forum.inductiveautomation.com/t/pass-through-mouse-clicks/18080)._