There is another class of window-popped_up-over-the-menu problem with some
Motif processes. Whether by Motif programming error or some poor design
interaction (it works successfully for the mwm, but not fvwm), menus
invoked by clicking on the body of windows (not pulldown menu bars!) pops
up the requested menu, but this is immediately followed by a window raise
event. I thought I might be able to do an explicit raise on the window
and then pop up the menu successfully, but this is not the case. After
the menu arrives, the parent window is raised and covers it. Placement
variations by invoking the menu near the sides of the main window allow
one to see the little popup poking its nose or foot from under the main
window. I don't know why mwm knows to avoid this and fvwm doesn't. In
all probability, there is an explicit window raise called from the
application by the mouse click. If it were invoked before the menu, it
would be OK, but mwm doesn't obscure the menu. This is similar to the
behavior mentioned in this thread. Apparently fvwm is perfectly willing
to cover up a popup menu, while mwm somehow prevents it.
What property is mwm respecting, and it one which fvwm can/should be made
to listen to?
Michael Tiefenback
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Sep 02 1997 - 10:44:41 BST