Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.cv.hp.com (Gabe Begeddov)
Newsgroups: comp.windows.x.motif
Subject: Re: Motif 1.1 question -- what is xmExtObjectClass <Xm/ExtObject.h>
Message-ID: <110630028@hpcvlx.cv.hp.com>
Date: 22 Nov 90 01:41:52 GMT
References: <6217@hplabsz.HPL.HP.COM>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 24


   / hpcvlx:comp.windows.x.motif / mayer@hplabsz.HPL.HP.COM (Niels Mayer) /  6:57 pm  Nov 15, 1990 /
   
   Answers anybody?

These internal objects were added to support gadget caching and "instance"
data that couldn't be added to the instance record due to binary compatability
requirements (mostly with VendorShell vs. Xt Shell subclasses). They were
also used to thread together shells in terms of the desktop and the style guide.
The latter requires that modality be enforced based on hierarchy. The desktop
parent is used for this threading up to the level of screen and display.

Motif1.1 does not have embedded dragNdrop support.

Gabe Beged-Dov
Interface Technology Operation
Hewlett-Packard
Corvallis, Oregon