Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!ogicse!milton!gibdo!slh
From: slh@gibdo.engr.washington.edu
Newsgroups: comp.windows.x.motif
Subject: Re: XmCreateFileSelectionDialog question
Message-ID: <1991Apr23.022921.18353@gibdo.engr.washington.edu>
Date: 23 Apr 91 02:33:33 GMT
References: <1991Apr22.220656.22475@murdoch.acc.Virginia.EDU>
Sender: news@milton.u.washington.edu (News)
Reply-To: slh@gibdo.engr.washington.edu (PUT YOUR NAME HERE)
Organization: zippity
Lines: 20

In article <1991Apr22.220656.22475@murdoch.acc.Virginia.EDU> scl@sasha.acc.Virginia.EDU (Steve Losen) writes:
[stuff]
|This is very useful, but there's one problem -- whenever the widget
|pops up it is always initialized with a default pattern, usually forcing
|the user to retype his pattern.  It would be much more convenient (in
|this application, at least) for the pattern to be saved between calls.
|In the code the default pattern string is being passed to
|XmCreateFileSelectionDialog.  My question is this:  Is there any way to
|get the user-modified pattern string back from this widget so that it
|can be passed to the next call to XmCreateFileSelectionDialog?  Or is
|there some other way to get the behavior I want?
|
	If instead of creating the widget every time you needed it,
	you just managed and unmanged it (which is probably a better
	thing to do anyway), the filter would be kept
	for you automatically, and so in fact you'd have to explicitely
	reset it if you want the default.
	If you actually wanted to create it every time,
	there is a resource you can query for to get the mask.
	(something like XmNdirMask or XmNdirSpec)