[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 154) Why doesn't XtDestroyWidget() actually destroy the widget?
Next Document: 156) How do I query the user synchronously using Xt?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 154) Why doesn't XtDestroyWidget() actually destroy the widget?
Next Document: 156) How do I query the user synchronously using Xt?
155) How can I open multiple displays with Xt?
Just open each display separately with XOpenDisplay or XtOpenDisplay. The latter is much simpler, since the Xt main loop will automatically poll all displays for events (if you put them all in the same application context). However, consult the skeleton X programs for multiple-displays to see how to handle the breaking of one display connection; normally Xlib issues an XIO error and then calls exit(). [Thanks to Ken Lee (kenton@rahul.net); 4/95]
Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 154) Why doesn't XtDestroyWidget() actually destroy the widget?
Next Document: 156) How do I query the user synchronously using Xt?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
faq%craft@uunet.uu.net (X FAQ maintenance address)
Last Update October 22 2009 @ 05:36 AM