From owner-oi-users  Fri Mar 10 09:35:52 1995
Return-Path: oi-users-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA19128 for oi-users-outgoing; Fri, 10 Mar 1995 09:35:52 -0800
Received: from marvin.boulder.openware.com (marvin.boulder.openware.com [192.245.99.138]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA19120 for <oi-users@freefall.cdrom.com>; Fri, 10 Mar 1995 09:35:45 -0800
Received: from boulder.openware.com (localhost.boulder.parcplace.com [127.0.0.1]) by marvin.boulder.openware.com (8.6.9/8.6.9) with ESMTP id KAA25495; Fri, 10 Mar 1995 10:32:06 -0700
Message-Id: <199503101732.KAA25495@marvin.boulder.openware.com>
To: "Pedro Cobas, CRI" <PCOBAS%ESOC.BITNET@vm.gmd.de>
Subject: Re: Rules to speed up the creation of OI objects 
Cc: "oi-users group" <oi-users@freefall.cdrom.com>
In-reply-to: Your message of Fri, 10 Mar 1995 12:10:45 +0700
Date: Fri, 10 Mar 1995 10:32:05 MST
From: Warner Losh <imp@boulder.openware.com>
Sender: oi-users-owner@FreeBSD.org
Precedence: bulk

: Based on your expericence which would be the rules to speed up the
: creation of OI objects ?.

Here are a couple that spring to mind that would apply to your current
situation:
	Don't map a window (set its state to be OI_active) until all
	its children have been parented to it.

	If you are going to add a bunch of objects to another object
	with layout, do a suspend_layout() create and add the objects
	then a resume_layout().

	Run your programs on a machine that has enough real memory :-)

Warner