[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 |
1123.0. "Command line options for XtInitialize, ULTRIX" by SMAUG::L_HO () Mon Jul 17 1989 17:49
We want to support some of the DECwindows standard options through command
line, just like other DECwindows applications. But somehow only the "-d"
and "-sync" option work. The others, such as "-g", "-bd" doesn't have any
effect on our application.
For example, if I enter the command:
dxsnaterm gateway -a cics -d node::0 -g -10-10 -bd red
^^ ^^ ^^^
The location of the window wouldn't change, the border color wouldn't
change to red.
We used
XtInitialize( appl_title,
appl_class, /* application class */
NULL, 0, /* options */
&argc, /* arg count, from main() */
argv /* arg vector, from main() */
);
to pass the option count and options and hope DECwindows Intrinsics
would take care of the rest. Is there anything else I need to do to
force the resource values be set to those specified through command line
option?
All our widgets are defined through UIL files.
Any help would be appreciated.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1123.1 | | GVRIEL::SCHOELLER | Who's on first? | Mon Jul 17 1989 18:00 | 6 |
| Except for the ones that you mentioned, the VMS version of XtInitialize does not
recognize those command line options. You could rig up a getopt to handle them
yourself.
Dick
|
| 1123.2 | | MU::PORTER | Rightward Ho! | Mon Jul 17 1989 19:45 | 5 |
| re .-1
but it says "ultrix" in the notes title! :-)
|
| 1123.3 | | FLUME::dike | | Tue Jul 18 1989 08:17 | 4 |
| Both -g and -bd appear to work. I tried them both out on xterm with
no problems.
Jeff
|
| 1123.4 | Sorry | LBDUCK::SCHOELLER | Who's on first? | Tue Jul 18 1989 11:49 | 4 |
| Oops. I guess I ought to read the titles instead of just the text 8^{).
Dick
|
| 1123.5 | You need a XrmOptionDescRec | VINO::MCARLETON | Reality; what a concept! | Fri Jul 21 1989 18:37 | 9 |
|
In order for XtInitialize to take command line options you have to
describe the relationship between the command line '-x' options and the
resources that they are to change. The XrmOptionDescRec argument to
XtInitialize is provided for this purpose. I remember seeing an
example using this argument some place but I don't remember where.
MJC
|
| 1123.6 | Doesn't like "." | SMAUG::L_HO | | Mon Jul 24 1989 14:04 | 7 |
| Thanks for all the help.
We also found out that one of the reason is our shell_name has a "." in it,
and after taking out the "." from the shell_name string that are passed
to XtInitialize(), all the standard options seem working. Is it a
feature or a bug in DECwindows toolkits?
|
| 1123.7 | | FLUME::dike | | Mon Jul 24 1989 16:06 | 4 |
| That probably confuses the hell out of the resource manager. '*' is probably
a character to avoid as well.
Jeff
|