| 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 |
I have written a routine for someone that initializes the toolkit,
creates an application context and connects to a specific node. It
then creates a CautionBox widget with a yes and no button whose labels
are Accept and Reject. The reason for this is that the user would like
to announce a problem or task to be either accepted or rejected by an
operator on a given node. Everything works peachy-keen the first time
but if the routine is called again it accvios while creating the
CautionBox widget. Is this another re-entrance problem??
After the user activates one of the buttons or the timer times out, I
do an XtDestroyApplicationContext and then return control to the
caller. Why does this croak upon the second call?? I'm pretty sure
I'm not writing on anybodys stack as I've meticulously checked
everything (??) and I've also checked that the arguments pushed for the
call to CautionButtonCreate are good.
Any ideas?? I can supply the routines if need be.
John
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2760.1 | my experience... | GSRC::WEST | Help stamp out and abolish redundancy ! | Tue May 15 1990 14:12 | 14 |
Are you using XtInitialize(...) or XtToolkitInitialize() ? In any case I think you can only one INITIALIZE per process activation. I had the same problem a while back. I did just one INITIALIZE and I even kept the app context and just re-used them. This did the trick. This was done in DECwindows V1.0. This may not be the case for V2.0. I also recall that there was a note talking about this and I think it had something to do with a bug/feature of the toolkit. -=> Jim <=- | |||||