| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1192.1 | Basic info on colors... | GSRC::WEST | I'm just visiting this planet. | Fri Jul 28 1989 11:17 | 17 |
|
All of our current workstations, sans the VS 3520/40, have only one hardware
colormap. X defines that there will only be one active window at a time. When
a window becomes the "active" window, such as the case with input focus, the
server will load that window's color map.
Most of the time windows will share colors and the same color map so switching
from one window to another causes no problems. Since there was a private color
map being used it will be "swapped out" when another colormap is needed. This
is expected behavior. The colors will go "technicolor" on you since the color
index does not change but the value at that index is now different.
Hope this helps... 8^)
-=> Jim <=-
|
| 1192.2 | Use a terminal for debugging | LBDUCK::SCHOELLER | Who's on first? | Fri Jul 28 1989 11:53 | 9 |
| Since .1 did not give any suggestions about how to work around the problem...
The best bet when debugging DECwindows applications is to log in from a terminal
(or across the net from a another workstation). That way, you can keep focus
in your application and can reduce the chances of piling up events in the
queue while sitting at a breakpoint or single stepping.
Dick
|
| 1192.3 | An idea | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Fri Jul 28 1989 14:42 | 14 |
| Here is a method to debug from the same workstation without having the
colormaps switch one you (this means, of course, that the application window
will have the wrong colors):
During debug only,
Don't do SetWindowColormap on the application window. Then the window
manager will never know to install a different colormap. To allow
you to have the winmgr install the cmap when you want it installed, create
a small window off in the corner somewhere on which you have done SetWindowColormap.
If you click in that window, the private colormap will be installed.
A more expensive way is to get a firefox which lets you have multiple
colormaps installed!
|
| 1192.4 | Sorry, don't understand. | PRIMES::UEBERSAX | Kris, Primes DWT, Landover, Md. | Sat Jul 29 1989 22:58 | 21 |
|
re: .-1
Hmmm.
> Don't do SetWindowColormap on the application window. Then the window
>manager will never know to install a different colormap.
Okay. Now the application and DBG TE window have the default cmap.
>To allow you to have the winmgr install the cmap when you want it
>installed, create a small window off in the corner somewhere on which
>you have done SetWindowColormap. If you click in that window, the
>private colormap will be installed.
But now the small window has focus and when I click back to the TE
won't the default cmap get reinstalled just as it did when switching
focus from the application window?
|
| 1192.5 | backing store? | PRIMES::UEBERSAX | Kris, Primes DWT, Landover, Md. | Tue Aug 01 1989 08:04 | 4 |
|
Is there a ballpark timeframe for backing store? (Not asking for a
commitment.)
|
| 1192.6 | Backing store and save-unders | FLUME::dike | | Tue Aug 01 1989 10:13 | 4 |
| The MIT servers and their derivatives (i.e. PMAX servers) have it
now.
Jeff
|
| 1192.7 | what do you mean? | VAOU02::JBLAIR | party on dudes! | Thu Aug 03 1989 21:00 | 13 |
| re .6
Can you provide further explaination?
ie. PMAX but not PVAX?
or is it Ultrix but not VAX versions of the server?
Ultrix version 3.0 or 3.1?
will the VMS server have it soon?
thanks
jeanne
|
| 1192.8 | | FLUME::dike | | Fri Aug 04 1989 09:46 | 22 |
| The VAX servers (VMS and Ultrix) are compiled from the same sources,
hence they are called the common servers. According to my
understanding, these servers are different enough from the MIT servers
that integrating MIT changes into them is a lot of work. MIT, in
R3 (I think), implemented backing store and save-unders, but those
features have not yet been implemented in the common server.
The PMAX servers, on the other hand, are MIT servers with an optimized
ddx. So, when MIT implemented backing store and save unders, it was
relatively easy to integrate them. It may be that they were already
in the sources that the PMAX project started with. I'm not sure
what the relative timing of R3 and PMAX were.
The upshot of all this is that it is a lot easier to integrate MIT
changes into the PMAX servers than the common servers.
This is all based on my knowledge of UWS2.0. Since UWS has moved
to the West coast, this could have changed. I'm sure people will
be happy to correct me if any of the above is wrong.
Jeff
|
| 1192.9 | switch input focus w/out deinstall. colormap | CSCMA::HODGE | | Wed Aug 09 1989 18:00 | 13 |
|
I was able to get around deinstalling the colormap from an application
window when I switched input focus to another window by using the autofocus
program (described in note 418). With autofocus running the input focus
can be changed by moving the mouse. Clicking the mouse is still required
to install a colormap. I used this hack for a GKS program that installs
a private colormap in the GKS window and takes input from the DECterm
window. After the GKS window opens, I have to click on that window to
install the colormap. After the colormap is installed, I can switch input
focus back to the DECterm window by moving the mouse.
Frannie
|