# Pass through mouse clicks - Perspective

**URL:** <https://forum.inductiveautomation.com/t/pass-through-mouse-clicks-perspective/57180>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [March 14, 2022, 10:01pm UTC](https://forum.inductiveautomation.com/t/pass-through-mouse-clicks-perspective/57180 "2022-03-14T22:01:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 14, 2022, 10:52pm UTC](https://forum.inductiveautomation.com/t/pass-through-mouse-clicks-perspective/57180/2 "2022-03-14T22:52:07Z")

</div>

_Nothing_ from Vision will translate to Perspective in this area. The underlying technologies are fundamentally completely different, even without the other hurdles (your scripts are running on the gateway, not the local browser session).

My first question is: Why do you feel you need to have two buttons overlaid?  
If you want a non-button, clickable thing, that "feels" clickable, just create a style class with appropriate `hover` and `active` styles:

> [@Perspective Custom Button](https://forum.inductiveautomation.com/t/perspective-custom-button/49119/3):
>
> I did a flex container with a style class (on the root container, crucially) - the meta props are what you’re after: [screenshot2c8ZBn]

---

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