| 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 |
It's starting to look like XtInitialize on pmaxes, if it sees "-display" as one of my argv's, replaces the string pointer with 0 in my argument list. Hence my application keels over because it expects no 0's in the argv list within the range dicated by argc. The ultrix documentation under XtInitialize says nothing about this. Can anyone tell me what the correct expected behavior of XtInitialize is? Thanks. /Eric
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2441.1 | QUARK::LIONEL | Free advice is worth every cent | Tue Mar 13 1990 15:11 | 5 | |
Heck - it writes into your argc argument too. As it was explained to me, it has something to do with looking for geometry switches. The whole thing's a crock in my view. Steve | |||||
| 2441.2 | FLUME::dike | Tue Mar 13 1990 16:54 | 5 | ||
XtInitialize leaves you with a consistent argc and argv. If you are saving argc before the XtInitialize call, then you could have problems, because it will shorten argv. Do your checking using the argv and argc that XtInitialize leaves you with, and you should be ok. Jeff | |||||