# Anyway to have a Custom InputBox with a Dropdown

**URL:** <https://forum.inductiveautomation.com/t/anyway-to-have-a-custom-inputbox-with-a-dropdown/36963>\
**Category:** Ignition\
**Created:** [July 22, 2020, 6:52pm UTC](https://forum.inductiveautomation.com/t/anyway-to-have-a-custom-inputbox-with-a-dropdown/36963 "2020-07-22T18:52:34Z")\
**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:** [July 22, 2020, 7:08pm UTC](https://forum.inductiveautomation.com/t/anyway-to-have-a-custom-inputbox-with-a-dropdown/36963/2 "2020-07-22T19:08:25Z")

</div>

When you stop in an event script, like what happens with any of the system.gui.\* popup boxes, the rest of the gui freezes. So, no. Something close to what you want can be done with completable futures. Start here:

> [@Nested invokeAsynchronous and invokeLater](http://forum.inductiveautomation.com/t/nested-invokeasynchronous-and-invokelater/26006/2):
>
> You can nest as shown. Another possibility would be to use just one asynchronous task and using CompletableFutures to pause that background and retrieve information from the foreground. See this discussion involving my later.py script module:

---

_[View the full topic](https://forum.inductiveautomation.com/t/anyway-to-have-a-custom-inputbox-with-a-dropdown/36963)._
