# "LOOK AT" as trigger events \[4.26\]

**URL:** <https://forums.unrealengine.com/t/look-at-as-trigger-events-4-26/254428>\
**Category:** Blueprint\
**Tags:** unreal-engine\
**Created:** [October 6, 2021, 11:58am UTC](https://forums.unrealengine.com/t/look-at-as-trigger-events-4-26/254428 "2021-10-06T11:58:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Everynone](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/everynone/32/1135017_2.png) [@Everynone](https://forums.unrealengine.com/u/Everynone)\
**Post date:** [October 6, 2021, 12:23pm UTC](https://forums.unrealengine.com/t/look-at-as-trigger-events-4-26/254428/2 "2021-10-06T12:23:35Z")

</div>

The whole shebang:

> [@Third person crosshair object highlight troubles](https://forums.unrealengine.com/t/third-person-crosshair-object-highlight-troubles/252041/13):
>
> The communication in the example revolves around Inheritance + Interface - a potent combo, imho. the base class implements the interface (which children inherit) the widget uses the same interface - calls children receive can be propagated: Actor → Widget Component → Widget without casting or finding user widgets (this can be done in many ways, though) the player has a collision sphere and sends an interface call to overlapped actors as we approach: [image] [image] Above, handl…

The first / third person perspective should matter little. The logic is the same.

---

_[View the full topic](https://forums.unrealengine.com/t/look-at-as-trigger-events-4-26/254428)._
