| number of available windows [message #215] |
Thu, 13 February 1992 01:55  |
hofer
Messages: 16
Registered: April 1991
|
Junior Member |
|
|
Is thre some way to get the number of windows available in pv-wave? My manual tells
me that I will have 16 windows on a VMS machine (which is true on our VAXstation) and
10 windows on any unix machine. But on our Personal Iris I get 32 windows.
How can I know, how much windows my program can open whitout runtime error?
Thanks in advance for any help.
By the way: We are using pv-wave 3.03 on a VAXstation 3200 and pv-wave cl 3.10 on a
Silicon Graphics PI 4D/35
Greetings Remo Hofer
--
RFC822: <hofer@urz.unibas.ch> or <hofer%urz.unibas.ch@CERNVAX.BITNET>
X.400: S=hofer;OU=urz;O=unibas;P=SWITCH;A=ARCOM;C=CH
HEPNET/SPAN: CHGATE::YOGI::HOFER or 20579::48130::HOFER
|
|
|
|
| Re: number of available windows [message #298 is a reply to message #215] |
Fri, 21 February 1992 10:08  |
mfaust
Messages: 6
Registered: February 1991
|
Junior Member |
|
|
In article <1555@pvi.UUCP>, jeb@pvi.UUCP (John E. Bee x464) writes:
>
> In 3.1 of Wave, a new keyword, WINDOW_STATE, is now available. WINDOW_STATE
> will return an array for all available WAVE windows, with a value indicating
> if a window is opened or closed. A value of 1 shows the window is open, and 0,
> the window is closed. As an example for using this keyword, enter:
>
> WAVE> window, 3 ; Open window 3
> WAVE> device, window_state = winarray
> WAVE> print, winarray
> 0 0 0 1 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0
>
It's interesting to note that this feature is not in my
documentation that came with WAVE 3.1. When I inquired
to my tech support a few months ago I was told that
this "fix" is being worked on and not in 3.1.
What gives? Now I'm wondering what other "undocumented"
features are in 3.1?
Mitchell O. Faust
mfaust@falcon.aamrl.wpafb.af.mil
"one of those evil defense contractors you've been warned about" :-)
"These opinions and views expressed here are strictly my very own
and do not reflect the official position of either the U.S. Air
Force, its contractors, staff, management or sponsors."
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
