| 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 |
Hi, One of my customer has a problem with modal dialog box. He has an application on a vax, performing XtToolkitInitialize XtOpenDisplay( disp1) on station 1 XtOpenDisplay( disp2) on station 2 XtOpenDisplay( disp3) on station 3 ... Creates widgets ... XtMainLoop() There's one client displaying on three servers. There's an operator on each station, working with the application. When an operator is doing a special thing (an activate for example), my customer wants to hold the application on the operator's station only (I think the application have to do some processing). He uses a modal dialog box for this, but this dialog box holds the three stations. I think it's a normal behavior. XtMainloop calls Xtdispatchevent which looks at a grablist to see if an event should be dispatch or not. Managing a modal dialog box puts something on this grablist. Am I right ? I think he can open a second display on each station and do a grabserver on this display in order to hold the application on a specific station. Is there another solution ? Can we have several input event queues in an application and only one XtMainLoop ? What about application context ? Thanks for your help. Jean-Marc.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3001.1 | R3 grablist is global | LEOVAX::TREGGIARI | Fri Aug 17 1990 13:23 | 9 | |
In R3 Intrinsics (which is what is currently shipping), there is only one global grablist. In R4, it looks from the code as if the grablist is per display. For R3, I guess they can grab the server, or make the dialog box modeless and add code to the application to ignore input from that display when in that state. Leo | |||||