Phil.Daws_at_daimlerchryslerservices-it.co.uk writes:
>
> Okay getting there :) The problem is that within my script it throws a dialog
> ue
> box to the screen where the user has to enter some data.
> This generates the environment variable that I would like the desktop to use
> throughout. It seems that when it execs the command it then
> carries on through the .fvwm2rc file. Can I make it pause until the user has
> entered the data ?
I must be missing part of the picture. If you use PipeRead
for an interactive dialog, then Fvwm will stop until the PipeRead
is done.
However, PipeRead is no good for interactive dialogs,
I don't think you want to try to operate a dialog while Fvwm is frozen.
How about using FvwmCommand?
Start the FvwmCommand server like this:
AddToFunc StartFunction I Module FvwmCommandS
After that, you can send commands to Fvwm with the program
"FvwmCommand". So have your dialog do something like:
system ("FvwmCommand \"SetEnv MYVAR test\"");
Why don't you want the rest of the .fvwm2rc processed?
Is it going to affect sub processes or the .fvwm2rc itself?
Anyway, using FvwmCommand, you can issue an fvwm read command
to read the parts that are affected, if thats the case.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Oct 31 2002 - 12:50:10 GMT