471,071 Members | 975 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,071 software developers and data experts.

Critial operations - "stopping UI interactions"....

I don't want my users to be able to press buttons/manipulate objects in my
software during a "critical operation" (defined as a write operation back to
the database, which happens on various threads). In order to prevent this,
I am "disabling" UI components before starting the write thread and then
"enabling" them again when the thread completes. One of the problems with
this approach is that certain controls (listbox, treeview) render themselves
"disabled" for the duration of the thread, which may be either 0.5 seconds
or as much as 30 seconds. This is causing an aesthetically displeasing
"flashing" of the UI. Is there any way of preventing UI interaction without
showing a modal progress dialog? (my thread executes delgates on the main
form in order to update the very components I would like to be disabled to
the user, so I don't think a modal dialog will work).
Nov 20 '05 #1
0 624

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Paul Johnston | last post: by
19 posts views Thread by VB Programmer | last post: by
3 posts views Thread by gregory_may | last post: by
59 posts views Thread by Jeff Bowden | last post: by
169 posts views Thread by JohnQ | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.