There are two problems:it is quite possible the problem is enlightenment. i have seen java vs. e interaction issues often enough before - mainly because the devs (ie me at the time me) didn't use a single java app - had none installed and couldn't be bothered installing some as it was a pain to do so. its a tough thing to debug app and wm interaction -ESPECIALLY when the app goes through many layers of abstraction (app codes -> java -> swing/awt -> xlib and finally asynchronous messages and events coming back).
1) Enlightenment does not remember windows settings correctly. At least it doesn't work with Eclipse's dialogues.
2) Eclipse does not call the appropriate pack() and setSize() routines. I know this is a bug in Eclipse because I write applications using SWT (Eclipse's tool kit) and dialog sizes are OK only if the correct methods are called.
it's a royal pita :( but there are many badly written x programs and toolkits too. many wm's have "hacks" where they disobey icccm just to make certain broken apps work - but these "breaks" then may impact other properly written apps later... it's a real pain.
It's a pain and I hate been forced to use GNOME because I need to work Eclipse. Enlightenment is faster and cleaner, but I can't use it for the time being.
Regards,
Rodolfo
|
-- Rodolfo M. Raya <[EMAIL PROTECTED]> Maxprograms |
