[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
    Search the FAQ Archives

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

Top Document: Motif FAQ (Part 6 of 9)
Previous Document: 209) Why is my application so huge?
Next Document: 211) After I call XtSetValues, when will I see the changes in my


210) How can I improve performance when creating and deleting


hundreds of text widgets?
[Last modified: Feb 98]

Answer: Ken Lee writes: This is mostly a problem with Motif 1.2.0 through
1.2.2.  Later versions are much better.  If you're stuck with an early version
of Motif 1.2, you may be able to greatly improve performance by batching the
drop site updates: surround the create or delete code with
XmDropSiteStartUpdate and XmDropSiteEndUpdate.  Alternatively, you can
completely disable drag-and-drop for your application. See the subject: "How
can I disable Drag and Drop in my Motif 1.2 client?"

Mike Youell adds: Using XmDropSiteStartUpdate sped up destruction of widgets
in Motif 1.2.5.  Also it may be worthwhile reminding people that it is not as
simple as "surround the create or delete code with XmDropSiteStartUpdate and
XmDropSiteEndUpdate" because it doesn't destroy the widgets when you do a
XtDestroy.  X does it at a later time, hence you still need to be inside the
drop-site update when these destroys are completed by X.




Top Document: Motif FAQ (Part 6 of 9)
Previous Document: 209) Why is my application so huge?
Next Document: 211) After I call XtSetValues, when will I see the changes in my

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page


[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)

Last Update October 22 2009 @ 05:27 AM

Some parts © 2009 Advameg, Inc.