Home > Articles > Operating Systems, Server > Linux/UNIX/Open Source

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Registering Procedures

Three primary methods exist for registering procedures for the receipt of events in an X Window application: callbacks, event handlers, and translations. Each method has the common purpose of providing the X Server a point of entry into the application at the occurrence of specific events. This is accomplished by invoking the registered procedure and passing as a parameter the appropriate event structure for processing.


Callbacks, which are provided by the internals of a widget, are function lists that are maintained by the widget for invocation when events that are consistent with the list's purpose are received from the X Server.

All callbacks are registered with the Xt function XtAddCallback. The function expects the following four parameters:

  • The widget in which the event must occur

  • The callback reason

  • A pointer to the procedure being registered (meaning one placed in the widget's function list for the specified reason)

  • Client data to pass to the procedure when it is invoked

  • Client data to pass to the procedure when it is invoked

Consider the following lines from Listing 1:

130:      XtAddCallback( btn, XtNcallback, 
131:                     callbackProc, data->func );

The widget specified in the XtAddCallback request is the newly created button. XtNcallback is the reason or function list in which the procedure pointer is stored. The final two parameters include a pointer to the callback function callbackProc (found in lines 54 through 65 of Listing 1), and the function pointer stored in the menuButtons array (in lines 30 through 41), which is passed as client data to callbackProc.

In defining a callback function for registration with the widget, it is crucial to honor the expected parameter list. Notice the three arguments expected by callbackProc:

54: static void callbackProc( Widget w, XtPointer _func,
55:                           XtPointer cbs )

As registered procedures are invoked from within the widget upon receipt of the appropriate event, the application programmer must conform to the standardized parameter list imposed by the authors of X.

The standard parameters expected by XtCallbackProc (third parameter to XtAddCallback) follows this form:

void function( Widget, XtPointer, XtPointer );

Similarly, other methods of registering procedures dictate the prototypes of the procedures registered.

This example accounts for the button press event that occurs in the button widget. However, what if the programmer desires notification when the mouse cursor enters or leaves the widget's window? Because the button widget does not inherently allow for procedure registration for these notification events, it is necessary to augment the widget by assigning an event handler.

Event Handlers

The addition of event handlers to augment a widget's functionality is provided by merit of the Xt layer of the X Window development environment. Any widget that is instantiated in an application may assign any number of event handlers by using the function XtAddEventHandler, as demonstrated in the following lines from Listing 1:

122:      XtAddEventHandler(btn, EnterWindowMask, False,
123:                       (XtEventHandler)statusProc,
124:                       (XtPointer)data->message);
126:      XtAddEventHandler(btn, LeaveWindowMask, False,
127:                       (XtEventHandler)statusProc,
128:                       (XtPointer)NULL );

The two calls to XtAddEventHandler could be combined by OR-ing the event masks EnterWindowMask and LeaveWindowMask together using the pipe symbol (|). However, notice that the fifth parameter in the two invocations differ. Upon entering the window (EnterWindowMask), the statusProc function is passed the message field of the menuButton to display; when leaving the window, it is passed NULL, informing statusProc to clear the status field.

An event handler may be assigned to any widget using one or more of nearly two dozen event masks that are defined by X in the file X.h, which is found under Linux in the path /usr/include/X11/.

As with the registration of the XtCallbackProc described earlier, the Intrinsics layer of X invokes all event handlers that are assigned to the widget when it receives the specified event in the widget's window.

The difference between callbacks and event handlers should be clear. Callbacks are lists that are inherent to a widget and are used to associate procedures to events. Event handlers are less direct and they augment a widget's capability.

Translations are similar to event handlers, but are registered within the widget at a lower level. A translation constitutes an advanced method of requesting and processing events in an X Window application.


Every widget has a table that defines how to translate actions that occur in the widget's window. An example of a translation table for the commandWidget is shown here:

BSelect Press: Arm()BSelect Click: Activate(), Disarm()

In these lines, BSelect Press corresponds to a mouse press, which the translation table associates with the action Arm. The Arm action maps to a function inherent in the widget that is responsible for altering the colors of the widget, in order to make it appear as if the button has been pressed.

If the mouse is clicked (pressed and released), then the Activate and Disarm functions are called. The Activate function consults the XtNcallback list for procedures registered with the widget, invoking those it finds. The Disarm function is responsible for returning normal colors to the widget so that it no longer appears to be pressed.

The X Toolkit Intrinsics layer of X Window development allows the programmer to manipulate translation tables by optionally defining and installing new actions and translations. Consider the install_translations routine defined in Listing 1:

250: void install_translations( Widget w )
251: {
252:  /* define a new action table */
253:   static XtActionsRec actions[] = {
254:     { "FollowCursor", (XtActionProc)actionProc },
255:   };
256:  /* define a new translation table */
257:   static char trans_tbl[] =
258:    ": FollowCursor()\n";
259:  /* install the actions into the application
260:   * context of the application
261:   */
262:   XtAppAddActions(XtWidgetToApplicationContext(w),
263:                   actions,
264:                   XtNumber(actions));
265:  /* install the parsed translations in the
266:   * widget specified
267:   */
268:   XtVaSetValues( w, 
269:                  XtNtranslations, 
270:                  XtParseTranslationTable(trans_tbl), 
271:                  NULL);
272: }

Three steps are necessary for the installation of new translations for a widget. First come the definition of an action such as “FollowCursor” and the registration of a function to invoke when the action occurs. The second step requires creating the interpreter or translation table for associating an event type to the new action. Finally, the translations are installed in the widget by assigning the result of the parsed translation table to the widget's internal table.

In this example, the widget’s entire translation is overwritten with a new one. It is often necessary to leave the widget's existing table intact and simply to complement it. In order to accomplish this, the function XtAugmentTranslations is used to install the new translations in the widget without affecting the existing table's contents.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020