summaryrefslogtreecommitdiffstats
path: root/doc/cd.n
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2023-03-17 20:11:26 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2023-03-17 20:11:26 (GMT)
commit4ce715f36aa76db649754d59c735144551d9aac5 (patch)
treea4adc4bf1b27d4bf68d1a4cad60537c7cdbc6ebf /doc/cd.n
parent2d7572997675b69cd32554859f3ac191c00068f7 (diff)
parentbdad96ab6988802901289f1b4d1f366a2002f023 (diff)
downloadtcl-4ce715f36aa76db649754d59c735144551d9aac5.zip
tcl-4ce715f36aa76db649754d59c735144551d9aac5.tar.gz
tcl-4ce715f36aa76db649754d59c735144551d9aac5.tar.bz2
Merge 8.7
Diffstat (limited to 'doc/cd.n')
0 files changed, 0 insertions, 0 deletions
ss="hl kwa">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 immediately. .PP The \fBupdate idletasks\fR 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 \fBupdate idletasks\fR 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 \fBupdate idletasks\fR. .PP The \fBupdate\fR command with no options is useful in scripts where you are performing a long-running computation but you still want the application to respond to events such as user interactions; if you occasionally call \fBupdate\fR then user input will be processed during the next call to \fBupdate\fR. .SH KEYWORDS event, flush, handler, idle, update