I see the eclipse-splash-screen for about 5 minutes and eclipse crashing afterwards, after producing a heavy load in the meanwhile.
The heavy load is probably the coredump of eclipse being written to disk. Can you produce a stack trace from this core dump ?
Well, I cannot tell what's causing the load of 3.95+ (for a short moment up to a total stop of anything except the mouse-cursor movement.), but there is nothing like a coredump. Usually, eclipse writes stuff into a logfile, but even this logfile is not written in this case...it's rather strange.
The only thing I get is non-documented exit-code of 9 of the java virtual machine. Since eclipse has an executable file which is to be used as a launcher, it is not possible to use the java-debugger for launching it. (At least I do not know how)
Seems that I have to accept this, and use the lib shipped with eclipse...as it turned out in the eclipse.tools newsgroup, I am (of course) not the only one facing this problem of a crashing eclipse when lesstif is used. There they say "better use the OpenMotif-libs".
Not quite the answer I'd liked to read...
I can't answer the mouse wheel question. Does anyone know how nedit provides support for this ? Maybe we need to add a couple of actions to scrollbars in LessTif.
Hmm...I don't know anything about this. I haven't ever looked at nedit's sources, I have to admit, I always thought that this is just done the lesstif-libs... %-|
Anyhow, thanks for your time and patience.
Volkmar
_______________________________________________ Lesstif mailing list [EMAIL PROTECTED] https://terror.hungry.com/mailman/listinfo/lesstif
