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

2014/11/28

Persistent problem with GamePad (as has been reported before)

stevegreen stevegreen

2014/11/28

#
I'm a PhD student preparing a university java course that starts soon. With the GamePad I have continued problems as I get the exception stack trace in |1|, also shown in |2|. The problem seems to have been reported before on the 16th of June 2014, see |3|. I have check that the problem persists: - multiple Greenfoot versions (e.g., 2.4.0 and 2.3.0) - used multiple zip programs (e.g., 7zip and file-roller) - is not easily fixed, at least My questions: 1. is this a platform specific problem? I.e., I am using 64-bit arch linux and Open JDK 7.u71 and use the pure java version of Greenfoot. 2. what java version is recommended to test problems / suspected bugs? JRE, OracleJDK, OpenJDK and Java version 1.7, 1.8, etc. and also minor number (e.g. “Open JDK 7.u71”). I’d rather check with the officially supported java version before posting. What Java version do developers use while testing. The ReadMe doesn’t recomend 3. is there an offical distributed version repository for Greenfoot, i.e., to participate in coding and look at the commit messages? 4. if the error is not apparent, is there a workaround where I can include the needed classes and jar file for the game pad via class path (and avoid loading the class files dynamically)? Thank you for suggestions, Steve PS: The stack trace is the same with any GamePad template, i.e., also the most basic one. |1| https://gist.github.com/anonymous/7d16eabe2fa271de7b4e |2| http://picpaste.com/Greenfoot_Exception-9IuFR5CK.png |3| http://www.greenfoot.org/topics/find/43834
davmac davmac

2014/11/28

#
I don't have time to look into this in detail right now, but a quick look at the GamePad class within the template reveals some Windows-style paths in lines such as:
                    method.invoke( cl, new File(".\\gamepadlib").toURI().toURL() );
Perhaps this is the problem?
You need to login to post a reply.