William Sherman -Visualization (wsherman++at++ncsa.uiuc.edu)
Thu, 26 Feb 1998 17:11:24 -0600 (CST)
I'm wondering if anyone else has noticed this, and specifically if
anyone at SGI can explain why a change was made to ircombine, and
whether the old feature can be re-implemented in the next version.
I just noticed a problem with one of my ircombine scripts that
occured when we upgraded our OS from IRIX6.2 for R4400 to IRIX6.2
for R10K (even though we've had the R10Ks for a while). So I'm
making the slight presumption that the problem I'm seeing comes
from a change in versions of /usr/gfx/ircombine.
The problem is that ircombine now reports:
"Error: -destination active is illegal when -target is specified"
for a script that used to work just fine.
As it happens, my script does indeed use both the "-destintation active"
and "-target" options. But I don't see why that is now disallowed -- we
need that option!
I've figured out two solutions that both seem to work, but neither
is as clean or easy as the previous solution, so I'd still like
this "error" check to be removed.
The two solutions:
1) Use an old copy of ircombine -- seems to work fine, but
generates a new error, probably because a lot of other
things in the OS are different. The error message it
generates is:
"Managed Area too large, and/or pixel size too big given 0 RM6's
Allocated pixel size: Illegal"
2) Use "setenv DISPLAY <target>" before calling ircombine. (So why
is this allowed when I can't specify "-target" on the command
line?)
Thanks,
Bill
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:54 PDT