Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ico!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: De-Transient'ing a transientShellWidget
Keywords: transient,shell,popup
Message-ID: <726@auto-trol.UUCP>
Date: 6 Feb 90 16:31:31 GMT
References: <597@igor.Rational.COM> <131190@sun.Eng.Sun.COM> <717@auto-trol.UUCP> <2674@bacchus.dec.com>
Reply-To: marbru@auto-trol.UUCP (Martin Brunecky)
Distribution: na
Organization: Auto-trol Technology, Denver
Lines: 29

In article <2674@bacchus.dec.com> asente@decwrl.dec.com (Paul Asente) writes:
>A far easier way to do this is to create menus that are potentially permanent
>in transient shells with the XtNoverrideRedirect resource TRUE.  To make the
>menu permanent, make XtNoverrideRedirect FALSE.
>

	That's RIGHT.

	Unfortunatelly, most of us use toolkits which don't give us
	too much freedom of shell choice. Motif, for example, creates
	"hidden" shells behind our back ( this aparently came from XUI )
	which are "shared" between multiple submenus.
	If I'd make such a menu permanent (tear-off), other submenu
	activation would fail badly.
	In addition, override shells (used for menus) do not handle
	all the properties used by transient shells. Plus, in Motif
	world, I can not substitute any other shell for Motif's
	XmMenuShell, since the entire menu system has heavy dependencies
	on this shell (and simply dies without it).


	[ I don't blame Intrinsics; I just have to live in an imperfect
	  word of toolkits which "improved" Intrinsics ].

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Martin Brunecky                   marbru@auto-trol.COM
(303) 252-2499                    {...}ncar!ico!auto-trol!marbru
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404