Invisible wrote:
>  Which is great if you just want something to happen when the
> user presses a button, but becomes problematic if you want things to
> happen while the user isn't pressing anything. (E.g., if you wanted to
> do something compute-bound, now the GUI stops responding until the
> compute task finishes.)

That's why the computer gods invented threads.

Seriously, it's the only sane way to do something compute-bound AND have a
GUI.

Post a reply to this message