XmUpdateDisplay(3X)XmUpdateDisplay(3X)NAME
XmUpdateDisplay - A function that processes all pending exposure events immediately
SYNOPSIS
void XmUpdateDisplay (widget)
Widget widget;
DESCRIPTION
XmUpdateDisplay provides the application with a mechanism for forcing all pending exposure events to be removed from the input queue and
processed immediately. When a user selects a button within a MenuPane, the MenuPanes are unposted and then any activation callbacks regis-
tered by the application are invoked. If one of the callbacks performs a time-consuming action, the portion of the application window that
was covered by the MenuPanes will not have been redrawn; normal exposure processing does not occur until all of the callbacks have been
invoked. If the application writer suspects that a callback will take a long time, then the callback may choose to invoke XmUpdateDisplay
before starting its time-consuming operation. This function is also useful any time a transient window, such as a dialog box, is unposted;
callbacks are invoked before normal exposure processing can occur. Specifies any widget or gadget.
XmUpdateDisplay(3X)
Check Out this Related Man Page
update(n) Tcl Built-In Commands update(n)
__________________________________________________________________________________________________________________________________________________NAME
update - Process pending events and idle callbacks
SYNOPSIS
update ?idletasks?
_________________________________________________________________DESCRIPTION
This command is used to bring the application "up to date" by entering the event loop repeatedly until all pending events (including idle
callbacks) have been processed.
If the idletasks keyword is specified as an argument to the command, then no new events or errors are processed; only idle callbacks are
invoked. This causes operations that are normally deferred, such as display updates and window layout calculations, to be performed imme-
diately.
The update idletasks command is useful in scripts where changes have been made to the application's state and you want those changes to
appear on the display immediately, rather than waiting for the script to complete. Most display updates are performed as idle callbacks,
so update idletasks will cause them to run. However, there are some kinds of updates that only happen in response to events, such as those
triggered by window size changes; these updates will not occur in update idletasks.
The update command with no options is useful in scripts where you are performing a long-running computation but you still want the applica-
tion to respond to events such as user interactions; if you occasionally call update then user input will be processed during the next
call to update.
EXAMPLE
Run computations for about a second and then finish:
set x 1000
set done 0
after 1000 set done 1
while {!$done} {
# A very silly example!
set x [expr {log($x) ** 2.8}]
# Test to see if our time-limit has been hit. This would
# also give a chance for serving network sockets and, if
# the Tk package is loaded, updating a user interface.
update
}
SEE ALSO
after(n), interp(n)
KEYWORDS
event, flush, handler, idle, update
Tcl 7.5 update(n)
Hi Folks,
Today hasn't been the best one of my career in IT.
I've been a contractor for a major utility company for a number of years, on a number of seperate IT contracts mostly Unix. The company had 10 different flavours of unix and multiple different varsions of most of them.
At the... (3 Replies)