I am having a problem with FVWM not behaving the same as
mwm when I set the TransientFor hint property. What I am trying to
do is make the window of a separate task behave like it is a dialog
of my main task. I am doing the following steps:
1) Run my program called 'MyTask'
2) MyTask spawns the standalone FontSel program using a pipe
to get the selected font from FontSel's standard output.
3) MyTask looks for the WindowID of FontSel based on its window
name using a timer and QueryTree().
4) When MyTask finds the WindowID of FontSel, it calls
XSetTransientForHint() using the WindowID of MyTask
as the parent window and the found WindowID of FontSel
as the dialog window.
When I do this under mwm, the stacking order is maintained
so that clicking on the window for MyTask will caused the window
for FontSel to be raised as well. Under FVWM, the two windows
continue to operate independently and clicking on the window for
MyTask raises it in front of the window for FontSel.
When I saw that this technique didn't work under FVWM,
I tried setting the windowgroup for the FontSel window to the
WindowID of MyTask, but this didn't work either.
Duane
--
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 Thu Oct 29 1998 - 09:39:29 GMT