[comp.windows.x.motif] nyi sometimes on positionVect or memberName

bobb@ico.isc.com (Bob Bundy) (11/14/90)

This is posted for a friend:

========================================================================
I copied and modified a popup dialogs from the ISC Motif 1.0 examples:
nyi (from motifburger).

I created two other popup dialogs: memberName and positionVect.
memberName and positionVect appear to behave completely normally except
when *immediately* preceeded by a popup and popdown of nyi.

If nyi is popped up and down and then sometime later memberName (or
positionVect) is poped up nyi popsup on top of memberName (or positionVect).
Popping down nyi restores normalcy until the next time nyi is popped up
by itself.

Each widget is popped up by pressing one of three toggle buttons in a
radio box (about five instances in different places).

What am I doing wrong?

Environment: Logix 386/25 w/ 8 meg memory, 160 mb disk, ISC UNIX  2.2, Motif
1.0, UIL.  No ethernet.

The UIL code for the three dialog widgets is:

object
memberName : XmPromptDialog {
        arguments {
                XmNdialogTitle = 'Member Name';
        };
        callbacks {
!               XmNokCallback           = procedure memberNameOK(k
!               XmNcancelCallback       = procedure destroy_self();
!               XmNhelpCallback = procedure help_proc('Generic');
        };
};

object
nyi : XmInformationDialog {  ! code that is not finished.  Useful
                             ! for prototyping.
        arguments {
                XmNmessageString = 'Not yet implemented';
                XmNdefaultPosition = true;
                XmNautoUnmanage = true;
        };
        callbacks {
                XmNcreateCallback = procedure createProc (k_nyi);
        };
};

object
positionVect : XmFormDialog {
        arguments {
                XmNdialogTitle          = 'Position Vector';
                XmNwidth                        = kinches2_8;
        };
        controls {
                XmLabel                 pvLab1; ! specify position vector
                XmText                  pvTxF1;
                XmText                  pvTxF2;
                XmText                  pvTxF3;
                XmLabel                 pvLab2;
                XmLabel                 pvLab3;
                XmLabel                 pvLab4;
                XmPushButton    pvOK;
                XmPushButton    pvCancel;
        };
        callbacks {
                XmNcreateCallback = procedure createProc (kPositionVect);
        };
}; ! end positionVect

Thanks for any light you can shed on the problem.

David Custer
(303) 538-3517 (days)

email to
att!druco!druwy!ddc
 or
research!drutx!druwy!ddc
 or
ddc@druwy.att.com