This site requires JavaScript, please enable it in your browser!
Greenfoot back
Twitter Twitter.hover
won0c
won0c wrote ...

2014/8/8

I'm Korean User. But I can't compile on 2.4.0 version

won0c won0c

2014/8/8

#
I'm Korean User. But I can't compile and I've noticed the class name is broken on 2.4.0 as follows. 'World' -> 'Wo...' 'Actor' -> 'Act...' 'Lander' -> 'Lan...' and so on <Debug log> ============== Greenfoot run started: Fri Aug 08 17:46:55 KST 2014 Greenfoot version: 2.4.0 Java version 1.7.0_51 Virtual machine: Java HotSpot(TM) Client VM 24.51-b03 (Oracle Corporation) Running on: Windows 7 6.1 (x86) Java Home: C:\Program Files\Java\jdk1.7.0_51\jre ---- Opening project: C:\Program Files\Greenfoot\scenarios\lunarlander 1407487617037: Listening for JDWP connection on address: javadebug Connected to debug VM via dt_shmem transport... Communication with debug VM fully establishedException during compilation: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at bluej.compiler.EventqueueCompileObserver.runOnEventQueue(EventqueueCompileObserver.java:70) at bluej.compiler.EventqueueCompileObserver.endCompile(EventqueueCompileObserver.java:95) at bluej.collect.DataCollectionCompileObserverWrapper.endCompile(DataCollectionCompileObserverWrapper.java:83) at bluej.compiler.Job.compile(Job.java:96) at bluej.compiler.CompilerThread.run(CompilerThread.java:70) Caused by: java.lang.reflect.InvocationTargetException at java.awt.EventQueue.invokeAndWait(EventQueue.java:1276) at java.awt.EventQueue.invokeAndWait(EventQueue.java:1251) at bluej.compiler.EventqueueCompileObserver.runOnEventQueue(EventqueueCompileObserver.java:67) ... 4 more Caused by: java.lang.NullPointerException at bluej.pkgmgr.Package$PackageCompileObserver.endCompile(Package.java:2908) at bluej.compiler.EventqueueCompileObserver.run(EventqueueCompileObserver.java:113) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:302) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) Exception during compilation: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at bluej.compiler.EventqueueCompileObserver.runOnEventQueue(EventqueueCompileObserver.java:70) at bluej.compiler.EventqueueCompileObserver.endCompile(EventqueueCompileObserver.java:95) at bluej.collect.DataCollectionCompileObserverWrapper.endCompile(DataCollectionCompileObserverWrapper.java:83) at bluej.compiler.Job.compile(Job.java:96) at bluej.compiler.CompilerThread.run(CompilerThread.java:70) Caused by: java.lang.reflect.InvocationTargetException at java.awt.EventQueue.invokeAndWait(EventQueue.java:1276) at java.awt.EventQueue.invokeAndWait(EventQueue.java:1251) at bluej.compiler.EventqueueCompileObserver.runOnEventQueue(EventqueueCompileObserver.java:67) ... 4 more Caused by: java.lang.NullPointerException at bluej.pkgmgr.Package$PackageCompileObserver.endCompile(Package.java:2908) at bluej.compiler.EventqueueCompileObserver.run(EventqueueCompileObserver.java:113) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:302) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
davmac davmac

2014/8/8

#
Hi, first, regarding the compilation problem: It looks like you've enabled the "accessibility support" in the Greenfoot preferences. The accessibility support was designed for BlueJ and does not work for Greenfoot. We will probably remove the preference in a future version (the fact that it is available now is really a mistake). second, the class name issue is something you've brought up repeatedly in the past, such as here and here. When you wrote to the support address I gave you this response:
Could you try editing the 'greenfoot.defs' file that is installed with Greenfoot (in the "lib" folder - you can use wordpad to edit it) and change this line: bluej.vm.args=-Xincgc -Dawt.useSystemAAFontSettings=on To: bluej.vm.args=-Xincgc (So, just remove the "-Dawt.useSystemAAFontSettings=on" part). This was added between Greenfoot 2.1.2 and 2.2.1 and might be part of the reason for the change in behaviour.
You reported that this fixed the problem, so I suggest that you do the same thing again. As to why you need to do this, I do not know. We have not had any reports of this problem occurring from other Korean users of Greenfoot.
won0c won0c

2014/8/10

#
I want Korean user to use Greenfoot without editing greenfoot.defs. This issue is very important to me, because I would like to promote Greenfoot in Korea. The inconvenient job will be the obstacle preventing Korean users from using Greenfoot. All the computers around me have the same problem. The reason that you have not had any reports of this issue from other Korean users is that Korean users of Greenfoot is very samll. I wished that this issue would be solved in the new release version. ps. Why is "bluej.vm.args=-Xincgc -Dawt.useSystemAAFontSettings=on" necessary? What is the purpose of this? I want you to confirm whether this problem occurs in China and Japan. Because Korean, Japanese, and Chinese is multi-character.
won0c won0c

2014/8/16

#
any idea?
davmac wrote...
Hi, first, regarding the compilation problem: It looks like you've enabled the "accessibility support" in the Greenfoot preferences. The accessibility support was designed for BlueJ and does not work for Greenfoot. We will probably remove the preference in a future version (the fact that it is available now is really a mistake). second, the class name issue is something you've brought up repeatedly in the past, such as here and here. When you wrote to the support address I gave you this response:
Could you try editing the 'greenfoot.defs' file that is installed with Greenfoot (in the "lib" folder - you can use wordpad to edit it) and change this line: bluej.vm.args=-Xincgc -Dawt.useSystemAAFontSettings=on To: bluej.vm.args=-Xincgc (So, just remove the "-Dawt.useSystemAAFontSettings=on" part). This was added between Greenfoot 2.1.2 and 2.2.1 and might be part of the reason for the change in behaviour.
You reported that this fixed the problem, so I suggest that you do the same thing again. As to why you need to do this, I do not know. We have not had any reports of this problem occurring from other Korean users of Greenfoot.
davmac davmac

2014/8/16

#
ps. Why is "bluej.vm.args=-Xincgc -Dawt.useSystemAAFontSettings=on" necessary? What is the purpose of this?
This is two settings: -Xincgc : use the incremental garbage collector, to try and reduce noticable pauses while Greenfoot is running -Dawt.useSystemAAFontSettings=on : forces text rendering to be anti-aliased. This is the one that seems to cause your problem, but it shouldn't. See here for documentation on this setting. If text is not anti-aliased, it generally looks much worse.
You need to login to post a reply.