| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 892.1 | Steal PSW's code from XFISH | GR8FUL::HERBERT | Wasted daze; wasted knights | Wed Jun 07 1989 12:55 | 9 |
| The easiest way to do it is to periodically poll for the creation of a
window with the proper characteristics (one that covers the entire
screen and is at the correct place in the window heirarchy). XFISH
contains a routine to do this; you can look through this conference to
find a pointer to the sources. Please point a pointer when you do find
it...
Kevin
|
| 892.2 | I bought my fish at... | NEURON::NICHOLSON | A belly as big as an oil spill | Wed Jun 07 1989 14:04 | 2 |
| GVRIEL::DUA1:[SCHOELLER.C.XFISH]
|
| 892.3 | | PSW::WINALSKI | Careful with that VAX, Eugene | Wed Jun 07 1989 18:27 | 5 |
| PSW::PSW$DUA1:[WINALSKI.XFISH]FISH.C contains a routine that will find a
DECwindows Session Manager's pause window on either VMS or Ultrix.
--PSW
|
| 892.4 | ...but I didn't want to poll... | JCR::RZUCIDLO | John Rzucidlo - INDEC New Products | Thu Jun 08 1989 11:16 | 9 |
| I was really looking for a way to initiate a command procedure of my choice
when the session was paused... I guess that would require a change to the
session manager to check a logical name or something and (if defined "true",
let's say) execute my procedure. A bit wish-list-ish...
Thank's anyway!
jr
|
| 892.5 | Poll initially, then use events | GR8FUL::HERBERT | Class B Computing Device | Thu Jun 08 1989 12:03 | 6 |
| You could poll for the window before it was initially created, and the
select MapNotify events on the window, so that you'd get an event when
the workstation was subsequently paused.
Kevin
|
| 892.6 | | PSW::WINALSKI | Careful with that VAX, Eugene | Thu Jun 08 1989 18:50 | 13 |
| A note about the Session Manager pause window: the Session Manager doesn't
create this window until you pause the session for the first time. The window
doesn't exist when the SM first comes up. If you resume a paused session, the
SM unmaps the window but it doesn't delete it. If you pause again, it re-uses
the window. Once created, the pause window ID never changes. Thus, the
application should poll for the pause window ID every so often (suitable
interval depends on how responsive you want the application to be, fish and
kaleidoscope use 5 seconds), as long as the window ID is coming back zero. When
you get a non-zero ID, you can select MapNotify events on it (if the server will
let you) and from then on let those events drive the application.
--PSW
|