[dev] Re: [dwm] Java Swing sucks, any solutions?
Yes, I did export AWT_TOOLKIT=MToolkit and it's working. Thanks a lot! In gmane.comp.misc.suckless, you wrote: >> I'm forced to use jmeter for the next two weeks at work. It's a swing >> app. Swing and dwm don't seem to wrk at all. > Doesn't the good ol' ``export AWT_TOOKIT=MToolkit'' work for ya? > If not, define "not working". > > Surma > >
Re: [dev] [dwm] Java Swing sucks, any solutions?
On 02/05/2010 03:47 PM, Alexander Surma wrote: >> I'm forced to use jmeter for the next two weeks at work. It's a swing >> app. Swing and dwm don't seem to wrk at all. > Doesn't the good ol' ``export AWT_TOOKIT=MToolkit'' work for ya? > If not, define "not working". > > Surma > > In most swing/awt-applications, this will cause a sigsegv (especially under amd64). I got best results with: $ wmname LG3D $ unset AWT_TOOLKIT $ run_your_app
Re: [dev] [dwm] Java Swing sucks, any solutions?
> I'm forced to use jmeter for the next two weeks at work. It's a swing > app. Swing and dwm don't seem to wrk at all. Doesn't the good ol' ``export AWT_TOOKIT=MToolkit'' work for ya? If not, define "not working". Surma
[dev] [dwm] Java Swing sucks, any solutions?
I'm forced to use jmeter for the next two weeks at work. It's a swing app. Swing and dwm don't seem to wrk at all. I know that this is swings fault and that it has come up in the past, but I'm wondering if anyone has ver found a workable solution. I have been running fluxbox in xnest just for jmeter, but xnest keeps crashing. Right now I'm installing tightvnc. I know I _can_ stop using dwm for the next two weeks, but I cringe at the thought. Are there any other solutions that people have come up with?
