| 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 |
Using the program in 1414.2 it seems impossible to get a VisibilityUnobscured event. Completely exposing the windows always gives: visibility event window = parent VisibilityPartiallyObscured visibility event window = w1 VisibilityPartiallyObscured A customer says it works on an RT and wants to know why it doesn't on ours. Bruce
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1604.1 | Window manager interaction? | DECWIN::KLEIN | Fri Oct 20 1989 10:55 | 9 | |
I suspect that the visibility criteria includes the window borders. If you're running a window manager, the window manager supplies a window frame around each application window. That window frame obscures the application window's borders, therefore the application window is never really completely visible. Have you tried running without a window manager? -steve- | |||||
| 1604.2 | What's the WM supposed to do? | LITE::B_WACKER | Fri Oct 20 1989 11:25 | 10 | |
>Have you tried running without a window manager? No, I haven't because that wasn't the customer's situation. I thought the border was added around the outside of the window, though. Also, in the sample code there's a window within the main window which also never gets unobscured. Bruce | |||||