Hello - Before you read the rest: I *not* just here to complain... I'll post a patch tomorrow, which seems to be providing us a reasonable solution for making Java work for now.
Dan Espen forwarded Eric Hawkes as saying: |Another proposed strategy was to write more |general code for the case where we cannot |explicitly detect the running window manager. |This is the method we now use for fvwm. !!! Better late than never. It seems to me like this should always have been the default. If you want to have maximum compatibility, yet still enable fancy features a fancier window manager can deal with, then the default should clearly be the SIMPLE behavior unless it can be verified that said fancier window system is present... not the other way around. But for us, switching to some future-ware beta version in the hopes that these problems will go away (and yet unknown ones will creep in) is not an option. And switching to another window manager is Really not an option! FVWM is great, simple, and stable, and works with everything... except Java. These problems have been around since (at least) 1999, and the solution seems so obvious (assume *basic* behavior if no specific window manager is detected.) I'm not thrilled to have added my time to the cumulative time that must have been spent dealing with this over the years. Be seeing you, - Sidik -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
