Set_Mapped(4)
Set_Mapped(4) DEVICES AND NETWORK INTERFACES Set_Mapped(4)
NAME
Set_Mapped request - set whether a tool is mapped to the
screen
SYNOPSIS
Set_Mapped(in boolean mapped
[in messageID commission]);
DESCRIPTION
The Set_Mapped request sets the mapped state of the option-
ally specified window, or of the window primarily associated
with the handling procid (if no window is specified).
The mapped argument is a Boolean value indicating whether
the specified window is (to be) mapped to the screen.
The commission argument is the ID of the ongoing request, if
any, that resulted in the creation of the window in ques-
tion.
APPLICATION USAGE
The ttdt_session_join(3), and ttdt_message_accept(3), func-
tions can be used by Xt applications to register for, and
transparently process, the Set_Mapped request.
EXAMPLES
The Set_Mapped request can be sent as in the following exam-
ple:
Tt_message msg = tttk_message_create(0, TT_REQUEST, TT_SESSION,
the_recipient_procid, TTDT_SET_MAPPED,
my_callback);
tt_message_iarg_add(msg, TT_IN, Tttk_boolean, 1);
tt_message_send(msg);
WARNINGS
Set_Mapped can also be sent as a multicast notice, as an
edict to all tools in the scope of the message. The conse-
quences of doing so can be severe and unexpected.
SEE ALSO
tt_message_iarg_add(3), tt_message_send(3),
ttdt_message_accept(3), ttdt_session_join(3); Get_Mapped
request.
Unix System LaboratorLast change: 13 May 1994 1
Man(1) output converted with
man2html