Mike Bronson <Mike.Bronson_at_sun.com> writes:
> What is the best way to programmatically detect that fvwm2
> is the running window manger?
>
> Can it be dectected by the use of X properties? If so,
> which ones uniquely identify fvwm2 and are not left
> behind by fvwm2 when its process dies?
Do these questions have anything to do with the open
FVWM/Java problems?
FVWM doesn't set any particular property to identify itself,
but we'd be willing to set one.
FVWM can already set a property that makes FVWM pass the
"XmIsMotifRunning" test. Java doesn't seem to like that much.
According to my Solaris XChangeProperty man page:
The lifetime of a property is not tied to the storing
client. Properties remain until explicitly deleted, until
the window is destroyed, or until the server resets.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
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 Tue Aug 28 2001 - 15:49:49 BST