GBUI Setup Error

Troubleshooting gui
1

I just tried following the tutorial to setup GBUI using the latest revision and end up with these errors. Any ideas would be appreciated.




Description   Resource   Path   Location   Type
Cannot override the final method from Spatial   BRootNode.java   /gbui/src/java/com/jmex/bui   line 415   Java Problem
Cannot override the final method from Spatial   BRootNode.java   /gbui/src/java/com/jmex/bui   line 422   Java Problem
The type CanvasRootNode must implement the inherited abstract method Spatial.hasCollision(Spatial, boolean, int)   CanvasRootNode.java   /gbui/src/java/com/jmex/bui   line 33   Java Problem
The type PolledRootNode must implement the inherited abstract method Spatial.findCollisions(Spatial, CollisionResults, int)   PolledRootNode.java   /gbui/src/java/com/jmex/bui   line 44   Java Problem
The type PolledRootNode must implement the inherited abstract method Spatial.hasCollision(Spatial, boolean, int)   PolledRootNode.java   /gbui/src/java/com/jmex/bui   line 44   Java Problem
The type CanvasRootNode must implement the inherited abstract method Spatial.findCollisions(Spatial, CollisionResults, int)   CanvasRootNode.java   /gbui/src/java/com/jmex/bui   line 33   Java Problem


2

Ahh yes, this happened because of some recent changes to JME, I think those changes are here to stay, but standtrooper hasn't GBUI accordingly yet, you can fix yourself on your local copy for now.

3

Yeah, so this is b/c GBUI hasn't been updated to the latest JME 2.0 - It's on my list for the next months fixes and enhancements (as SomethingNew said)



As soon as I get one or two more of these bugs fixed I'll update GBUI (so probably Friday or Saturday-ish) to the latest JME version.  I'm hesitant to update it yet simply b/c I'm tracking down where some of these issues have come from, which look like they stemmed from one of my last updates to JME or when I refactored some code and I'd like to ensure that I get those fixed prior to potentially introducing some new bugs.  But it'll be this week for sure. 



timo

4

I'm going to guess that this issue was caused by the SVN trunk of JME 2.0 (?)



I pulled down the latest JME 2.0 zip and tried it, everything works just fine, zero issues.



I'm pulling down the svn trunk now to run it again…it looks like just those two methods, I removed them and checked them in.



timo


5

downloaded latest build and it's still happening…

6

downloaded or checked out via SVN?  SVN will not cause this issue, guaranteed, since that's the version I'm using.  Download, there's no update to the jars or zip files.

7

ah ok…

will check out the source…