[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
|
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
254.0. "Command line switchs for XtInitialize" by OIWS20::BRYSON () Mon Feb 20 1989 13:21
I have been able use use -display on the command line when executing
DECwindows applications on VMS (this might help some of you worried
about creating so many WSA devices); however, I have been unable to
get other qualifiers to work as they do under Ultrix. I assume that
once again this is unsupported, but customers (and I) want to know
what parameters I may pass. I know that VMS will not support -xrm,
but what about the others. If someone with VMS DECwindows sources
would look in XtInitialize.c and give use the options list it would
be appreciated.
This list under Ultrix is as follows:
"+rv", "*reverseVideo"
"+synchronous","*synchronous"
"-background", "*background"
"-bd", "*borderColor"
"-bg", "*background"
"-bordercolor","*borderColor"
"-borderwidth",".borderWidth"
"-bw", ".borderWidth"
"-display", ".display"
"-fg", "*foreground"
"-fn", "*font"
"-font", "*font"
"-foreground", "*foreground"
"-geometry", ".geometry"
"-iconic", ".iconic"
"-name", ".name"
"-reverse", "*reverseVideo"
"-rv", "*reverseVideo"
"-selectionTimeout", ".selectionTimeout"
"-synchronous","*synchronous"
"-title", ".title"
"-xrm"
For those of you that have not used these qualifiers, here is an
example:
$ mcr decw$clock -display OIWS20::0
I have not been able to get it to work with RUN because I believe
that RUN will not pass the command line to the application (argv).
I'm almost sure that this is unsupported but any information would
be helpful.
David
T.R | Title | User | Personal Name | Date | Lines |
---|
254.1 | Commented-out on VMS | DECWIN::KLEIN | | Mon Feb 20 1989 14:39 | 12 |
| Unfortunately, the code that parses these switches was commented-out
of the VMS variant of INITIALIZE.C. (Correct me if I'm wrong.) There
was evidently a problem with the parsing of display names vs. file
names (both of which can contain colons). I believe that this
code was removed (for VMS only) after a problem was found in DECwindows FT2.
Lobby the toolkit group if you want to see the switches reinstated.
Obviously, a way must be found to differentiate display names and
file names on the command line, but I'm sure it can be done.
-steve-
|
254.2 | -display still works with SDC | OIWS20::BRYSON | | Wed Feb 22 1989 13:43 | 44 |
|
-display still works with SDC. In fact, the issues about not being
able to get a detached process to get the display device easily and
the concern of having so many WSA devices created can be elliminate
with the following:
CLOCK.COM
$ MCR DECW$CLOCK -display 0::0 ! Local transport
or
$ MCR DECW$CLOCK -display NODE::0 ! DECnet transport
The RUN/DETACH command
$ RUN/DETACH/PROC="Clock"/OUTPUT=NL:/INPUT=CLOCK.COM -
SYS$SYSTEM:LOGINOUT
Now, obviously the above example is limited but you could play with it
to make it more generic so that you may specify the node to connect
to. HOWEVER, THIS WILL ONLY WORK WITH TOOLKIT PROGRAMS, because it
is XtInitialize that is taking care of this for you. In the above
case, I did not create a WSA device with SET DISPLAY/CREAT nor was
the logical DECW$DISPLAY defined.
Of the list that I mentioned in .0, the only two command line switches
that XtInitialize appears to handle is -display and -name. However,
I could not get -name command to work. As I understand it, the -name
switch will set the application name for resource lookup in
DECW$XDEFAULTS.DAT.
Are these switches planned for extinction with VMS in the next version?
If not, why not document the -display switch for toolkit applications
so that you may use it on VMS. Finally, are there any switches that
were ADDED for VMS specifically (doubtful since this switching
mechanism is not supported)?
Thanks,
David
|
254.3 | Are you sure about 0::0? | IAGO::SCHOELLER | Who's on first? | Wed Feb 22 1989 14:24 | 7 |
| >$ MCR DECW$CLOCK -display 0::0 ! Local transport
Does this use local transport or decnet? When decw$display is defined to 0::0
it uses decnet to talk locally.
Dick
|
254.4 | Not really... | OIWS20::BRYSON | | Wed Feb 22 1989 14:48 | 10 |
| No. I'm not sure.
If defining decw$display to 0::0 uses DECnet then so would this syntax.
Sorry about that.
David
|