# Dropdown List Events

**URL:** <https://forum.inductiveautomation.com/t/dropdown-list-events/90537>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [May 17, 2024, 1:15am UTC](https://forum.inductiveautomation.com/t/dropdown-list-events/90537 "2024-05-17T01:15:51Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [May 20, 2024, 5:26pm UTC](https://forum.inductiveautomation.com/t/dropdown-list-events/90537/11 "2024-05-20T17:26:32Z")

</div>

> [@Devin\_Golberg](#):
>
> I had to somehow drill up to get to the parent version (which I suspected and appears to be the case)

The way your code is written, `subEvent.source` and `event.source` are the same thing, but `subEvent.source` will fail when calling a custom method because of the reason I listed above; the component loses its wrapper when referenced from the custom listener.

The most common place I encounter this issue is when I obtain a component using `SwingUtilities.getAncestorOfClass` instead of using a recursive function. See this forum post for reference:  
[Why can't custom properties and methods be accest from a component that is obtained using SwingUtilities.getAncestorOfClass](https://forum.inductiveautomation.com/t/why-cant-custom-properties-and-methods-be-accessed-from-a-component-that-is-obtained-using-swingutilities-getancestorofclass/78606/3)

> [@Devin\_Golberg](#):
>
> the simplest way to alleviate the issue was to simply rename the variable

Agreed.

---

_[View the full topic](https://forum.inductiveautomation.com/t/dropdown-list-events/90537)._