The problem is that, when the computation is launched, the interface freezes in the most inelegant way. And any progress message sent to the GUI is not shown until the computation is over (that makes for very useless progress messages!).
A GUI is UI event driven. User clicks on an "object"...something happens...meaning that a subroutine runs and potentially displays something. One of those things that can potentially happen is a GUI window with some status display. If the GUI UI is designed correctly, the UI won't "freeze". The designer of the the GUI should update the display per "unit of work".
In reply to Re: Is there a way to free the Tk MainLoop without getting into parallel programming?
by Marshall
in thread Is there a way to free the Tk MainLoop without getting into parallel programming?
by Takuan Soho
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |