DAVISM@kcgl1.eng.ohio-state.edu (Michael T. Davis) (07/28/89)
I think I might have stumbled on a possible bug with DECwindow's
implementation of XtOpenDisplay (). According to DECW$INCLUDE:Intrinsic.h,
the parameters, in order, are the application context, the display name,
the application name, the class name, a pointer to an options list, the number
of options in the options list, a pointer to the number of elements in argv[]
and a pointer to argv[]. Here is my call:
data. display = XtOpenDisplay ( data. context, "",
"mandelbrot", "Mandelbrot",
&options, XtNumber ( options ), &argc, argv );
(This is an application which produces fractals from the Mandelbrot set,
from Doug Young's book, X WINDOW SYSTEMS [sic] PROGRAMMING AND APPLICATIONS
WITH XT, modified to work with a self-written widget.)
Here is my options record:
static XrmOptionDescRec options [] =
{
{ "-depth", "*depth", XrmoptionSepArg, NULL },
{ "-ro", "*real_origin", XrmoptionSepArg, NULL },
{ "-io", "*imaginary_origin", XrmoptionSepArg, NULL },
{ "-xr", "*x_range", XrmoptionSepArg, NULL },
{ "-yr", "*y_range", XrmoptionSepArg, NULL },
{ "-distance", "*max_distance", XrmoptionSepArg, NULL }
};
What's really strange is that if I don't use application contexts
(e.g. call XtInitialize and XtMainLoop), the options seem to be parsed
correctly. Am I doing something wrong or is this really a bug?
Thanks,
Mike
________________________________________________________________________
| InterNet> davism@{kcgl1.eng|rcgl1.eng|osu-20.ircc}.ohio-state.edu |
| -or- |
| davis-m@eng.ohio-state.edu |
| CompuServe> 73667,541 |
|************************************+***********************************|
| "Daddy, Daddy!! Why's Mommy | |
| running across the field?" | These_Thoughts := My_Own |
| "Just shut up, Son, and reload." | |
------------------------------------------------------------------------