Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!sgi.com!linton
From: linton@marktwain.rad.sgi.com (Mark Linton)
Newsgroups: comp.windows.interviews
Subject: Re: -iconic problem
Message-ID: <1991Apr16.202414.5368@odin.corp.sgi.com>
Date: 16 Apr 91 20:24:14 GMT
References: <7649.9104151912@lulu.cs.keele.ac.uk>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: linton@marktwain.rad.sgi.com (Mark Linton)
Organization: sgi
Lines: 18

In article <7649.9104151912@lulu.cs.keele.ac.uk>, yufan@cs.keele.ac.uk (Yufan Hu) writes:
|> Hi,
|> 
|> I have a problem when using -iconic option.
|> 
|> I want to start a application with -iconic set. The application will create
|> more windows by itself and all these subsequent winodows should not start
|> up in iconic form. But cuurently them do. I tried to create ApplicationWindow
|> and call ApplicationWindow->iconic(false) before mapping it. But seems not
|> effect. 
|> 
|> Could somebody help me to solve this problem?
|> 

I just put in a change for 3.0-beta that will make -iconic et al. only be interpreted
for ApplicationWindows.  If you are using interactors, you can also workaround
this by defining a name for your toplevel interactor and define the resource
"*name*iconic:off".