2401
Developer's Corner / Re: Keeping the UI Responsive - What Would You Do?
« Last post by kyrathaba on May 07, 2011, 09:41 PM »Renegade,
Of the ideas you've mentioned, I'd favor this one:
Show the window just before entering the worker-thread, then as the thread completes have it close the window.
I ran into a similar but not analogous issue when coding KyrCrypt; in my case, I wound up using both a per-item progress bar and a batch progress bar (along with the requisite Cancel button).
The in-memory window should be serviceable enough, I'd imagine. Maybe not as elegant as you'd wish, but simple and intuitive, two things users need
Of the ideas you've mentioned, I'd favor this one:
Create the "waiting" window at startup so it's already in memory and doesn't need to be created, then update it's UI and .Show() it when needed
Show the window just before entering the worker-thread, then as the thread completes have it close the window.
I ran into a similar but not analogous issue when coding KyrCrypt; in my case, I wound up using both a per-item progress bar and a batch progress bar (along with the requisite Cancel button).
The in-memory window should be serviceable enough, I'd imagine. Maybe not as elegant as you'd wish, but simple and intuitive, two things users need


Recent Posts