Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!samsung!uakari.primate.wisc.edu!uwm.edu!csd4.csd.uwm.edu
From: duncan@csd4.csd.uwm.edu (Shan D Duncan)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper Bug Figured Out.
Message-ID: <696@uwm.edu>
Date: 1 Nov 89 01:28:48 GMT
References: <970@unsvax.NEVADA.EDU>
Sender: news@uwm.edu
Reply-To: duncan@csd4.csd.uwm.edu
Distribution: all
Lines: 33

From article <970@unsvax.NEVADA.EDU>, by maniac@arrakis.nevada.edu (ERIC SCHWERTFEGER):
> 
>      Well, after much fighting, I think I finally figured out the problems
> with Xoper 2.0 (yes, I meant plural).
>      First of all, Xoper will hang if you don't have "xoper.startup" in s:,
> but this could be related to another bug.
>      Second, if you don't specify "usescreen" in the xoper.startup file,
> Xoper will attempt to open a window on the WB screen, and will hang.
>      Finally, you can't use the -b command on the CLI line, nor can you
> use the "hold" command in the xoper.startup file, because both cause
> XOper to get hung up.
> 
>      In other words, you must have a file "xoper.startup" in s:, and you
> must also specify "usescreen" as an option in that file.
> 
> Eric Schwertfeger, UNLV, maniac@arrakis.nevada.edu



This is exactly what I finally figured out.  This means no
iconify feature.

Good work Eric!


I reread the docs and it does say xoper will not startup until after
the file xoper.startup has been read.  He also says the file goes in
S:

I haven't tried the usewindow instead of usescreen so I'm holding off
writing the author (on bitnet) until I RTFM.  

-Shan D.