Eclipse is launching your application with whatever JRE you defined in your launch configuration. Since you’re running the 32-bit Eclipse, you’re running/debugging against its 32-bit SWT libraries, and you’ll need to run a 32-bit JRE. Your 64-bit JRE is, for whatever reason, your default Installed JRE. To change this, first make sure you have a … Read more
I had the same problem, turned out that TeamViewer was causing this. In your TeamViewer go to: Extras → Options → Advanced → QuickConnect button, configure it and disable the show QuickConnect button.
Pros Swing: part of java library, no need for additional native libraries works the same way on all platforms Integrated GUI Editor in Netbeans and Eclipse good online tutorials by Sun/Oracle Supported by official java extensions (like java OpenGL) Cons Swing: Native look and feel may behave different from the real native system. heavy components … Read more
You might consider any of these: JHotDraw, cited here, a meta-library for creating custom graph editors. Prefuse visualization library, illustrated here and here. Batik, which implements SVG rendering. JGraph demo and user manual. GraphStream, illustrated here. JFreeChart XYBubbleRenderer A JTree, suggested here, with a custom TreeIcon. A custom renderer, with x based on a fraction … Read more
It is thrown because your listener code is called from outside the SWT Display thread. You run code on the display thread like this: Display.getDefault().syncExec(new Runnable() { public void run() { // … } }); or, asynchronously: Display.getDefault().asyncExec(new Runnable() { public void run() { // … } });
Most of the times this is a bug in the VM. But it can be caused by any native code (e.g. JNI calls). The hs_err_pidXXX.log file should contain some information about where the problem happened. You can also check the “Heap” section inside the file. Many of the VM bugs are caused by the garbage … Read more
Decision tree: Frameworks like Qt and SWT need native DLLs. So you have to ask yourself: Are all necessary platforms supported? Can you package the native DLLs with your app? See here, how to do this for SWT. If you have a choice here, you should prefer Qt over SWT. Qt has been developed by … Read more
I’ve just run into the same problem. I haven’t tried it yet, but I plan to include versions of swt.jar for all platforms and load the correct one dynamically in the start of the main method. UPDATE: It worked. build.xml includes all jars: <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_linux_gtk_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_macosx_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_win32_x86.jar”/> <zipfileset dir=”/home/aromanov/workspace/foo/lib” includes=”swt_linux_gtk_x64.jar”/> … Read more
Just package it anywhere in the jar. One thing you have to keep in mind though – before you can use the DLLs you need to actually extract these from the JAR and dump these on the hard disk somewhere otherwise you won’t be able to load these So basically – I did JNI project … Read more