# Flash the background

**URL:** <https://forum.inductiveautomation.com/t/flash-the-background/19993>\
**Category:** Ignition\
**Created:** [October 5, 2018, 3:22pm UTC](https://forum.inductiveautomation.com/t/flash-the-background/19993 "2018-10-05T15:22:10Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![chasondeshotel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/chasondeshotel/32/20032_2.png) [@chasondeshotel](https://forum.inductiveautomation.com/u/chasondeshotel)\
**Post date:** [October 8, 2018, 10:44pm UTC](https://forum.inductiveautomation.com/t/flash-the-background/19993/5 "2018-10-08T22:44:07Z")

</div>

To expand on the sleep() thing, because I didn't know this and almost did a bad with the project I'm working on:

> [@Time.sleep function in Ignition](http://forum.inductiveautomation.com/t/time-sleep-function-in-ignition/10337/3):
>
> [quote=“dlaki”]Anyone here have tried to to use time.sleep function of time module in Ignition?[/quote]Nick hints at this, but let me be more explicit: Never, ever, use time.sleep or any other delay function in Ignition unless it is on its own asynchronous thread. Delays on the event dispatch thread (darn near everything in a client) will freeze the user interface for the duration of the delay. Just say no to any form of sleep. When you need delays, always use system.util.invokeLater() with …

That thread gives the reasons why you shouldn't use sleep() and a few workarounds

---

_[View the full topic](https://forum.inductiveautomation.com/t/flash-the-background/19993)._
