Skip navigation

Category Archives: Java

Just a quick tip: if you accidentally pass a data type to someTextView.setText() that cannot be implicitly coerced into a CharSequence representation (like, say, an int), logcat will display the error ‘fatal error: Resource$NotFoundException’ citing some weird hex String resource id that you probably don’t recognize. I have no idea why the Android framework does this in response to mismatched data types, but there you have it– if you see a contextually nonsensical error about some resource not being found around a TextView’s setText() method, check the data type of the argument you’re passing to setText().

It’s still early in design and the developers (possibly including me on the Android front) haven’t decided on a definite solution yet, but big changes are coming to robocode in version 2.0.  A major focus will be mobile device support for the simulation, bots, and/or the whole programming environment!  See the robocode-developer’s google group and this thread for details… Image