dmcallis%ug.utah.edu@cs.utah.edu (Dave McAllister) (10/17/89)
<problem with twm: popup windows go blank>
Yes. I've experienced your problem several times. We use twm at Evans &
Sutherland (where it was written), and I started having things written in my
popup windows during an outbreak prank programs such as crabs, termites,
taunting faces, and other programs that do Sun graphics on the PixRect level.
If I had a popup window up and one of these programs drew something across it
it would be there the next time I pulled up that window. So apparently the
popup window bitmap is mapped back from the part of the screen where it was
displayed. I imagine since the Ardent II's presumably use different low-
level pixel calls they zero the window when it is undrawn, accounting for
the different behavior on different systems.
I'm sorry I'm not more knowledgable about this stuff (I've only used Unix
for 3 months), but hopefully this will point you closer to the source of the
problem.
Good luck!
Davebert@opusc.CS.SCAROLINA.EDU (Bert Still) (10/17/89)
I am having a problem with twm on an Ardent Titan II. The first
time I bring up a user-defined menu, things work as expected. The
overlay box is produced and filled with labels, each indicating the
appropriate window manager function. The second and all subsequent
tries at the window produce the overlay box empty (meaning that there
are no little labels). The menu will function correctly, ie. if you
select a ``label'' then release the button, the function is executed;
but, at no time is the text of the label visible. So, you must have a
very good memory in order to fully use the menus. :-)
Now that you think you have it figured out, there are two more
intersting points. The TWM window menu always works correctly: labels
and all. Furthermore, if you select the ``source .twmrc'' function
to reload the data structures, the labels will again appear the first
time (as before). Very strange...
I know that we could use awm instead, but my userbase has become
very accustomed to twm on the Sun-4's. Those that have played with
awm, myself included, have come to the conclusion that twm is more
versatile and perhaps even a shade faster. (Thank you, Tom!) Needless
to say, switching to awm/uwm/wm is not a viable option.
I have hunted through the code for almost a month now, and I think
it's time to admit defeat. The code runs flaawlessly on the Sun's, or
at least it has me fooled, and runs beautifully on the Ardent's, except
for the one flaw mentioned. Has anyone else ever seen this problem?
Does anyone have any ideas? (Tom are you listening?)
Many thanks,
bert
*************************************************************************
__
bert@cs.scarolina.edu | \__ /----/
Bert Still __ __-------| Fabi\---\ __ | 8 |
Univ of South Carolina / \^___-----------------\_ / \\----/
Parallel Supercomputer __/| () |_ |#8|P O R S C H E |:| () |
Initiative <-- \__/ |------------------|--\__/
*************************************************************************toml@Solbourne.COM (Tom LaStrange) (10/17/89)
[ I am having a problem with twm on an Ardent Titan II. The first
[ time I bring up a user-defined menu, things work as expected. The
[ overlay box is produced and filled with labels, each indicating the
[ appropriate window manager function. The second and all subsequent
[ tries at the window produce the overlay box empty (meaning that there
[ are no little labels). The menu will function correctly, ie. if you
[ select a ``label'' then release the button, the function is executed;
[ but, at no time is the text of the label visible. So, you must have a
[ very good memory in order to fully use the menus. :-)
[ Now that you think you have it figured out, there are two more
[ intersting points. The TWM window menu always works correctly: labels
[ and all. Furthermore, if you select the ``source .twmrc'' function
[ to reload the data structures, the labels will again appear the first
[ time (as before). Very strange...
I would be willing to bet money that your server has backing store problems.
the TwmMenu works because it is created when the mouse button is pressed.
Menus show up after a f.twmrc file because they too are rebuilt.
Try putting "NoBackingStore" in your .twmrc file.
--
Tom LaStrange
Solbourne Computer Inc. ARPA: toml@Solbourne.COM
1900 Pike Rd. UUCP: ...!{boulder,nbires,sun}!stan!toml
Longmont, CO 80501corbet@mead.uucp (Jonathan Corbet) (10/19/89)
bert@opusc.CS.SCAROLINA.EDU (Bert Still):
> I am having a problem with twm on an Ardent Titan II.
I think I know what your problem is. The Ardent X server has got some
serious problems with backing store. It claims to provide it, but it
doesn't. Not only that, but it fails to provide expose events when called
for, since it apparently has fooled itself into thinking that the window
can be restored from backing store. I suggest turning off the use of
backing store in twm and trying again.
Jonathan Corbet
National Center for Atmospheric Research, Field Observing Facility
corbet@stout.ucar.edu