DragonFly On-Line Manual Pages
UPDATE(1) User Contributed Perl Documentation UPDATE(1)
NAME
update -- command line setting of Interchange databases
VERSION
1.0
SYNOPSIS
update -c catalog [-f field -k key [-t table] value]
DESCRIPTION
Interchange's "update" is a rudimentary method of directly setting the
DBM files (not the ASCII files) of a Interchange DBM database.
NOTE: This command DOES NOT APPLY TO SQL databases. They have their own
command line monitors that are more flexible.
OPTIONS
-c name
Sets the catalog for which "update" operates. It reads the
catalog.cfg file to retrieve database settings.
-f field
The name of the field to set.
-n name
The name of the table to set. If the table is not a DBM database
the "update" program will terminate with an error.
SEE ALSO
http://www.icdevgroup.org/
AUTHOR
Mike Heins
perl v5.20.2 2015-08-31 UPDATE(1)
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
immediately.
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
application 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
asynchronous I/O, event, flush, handler, idle, update
Tcl 7.5 update(n)