Debugging waves with onPaint()

Jump to navigation Jump to search

The approach I told above is based in gathering all event data first, then process everything, only then do some output. Shift from an event driven architecture to a simpler request driven (input/process/output) architecture.

The main advantage is not being constrained with event ordering. Event ordering in Robocode doesn´t give any extra information. The main drawbacks are increased codesize (not an option for nanobots), and necessity of member variables (not an option for perceptual bots).

MN14:29, 18 May 2012

Of course, for private/temporary debugging, entangling draws and sysouts in the middle of other events is fine.

MN14:35, 18 May 2012
 

This is what I kind of what I figured the painting was for in the first place. :)

Chase-san03:23, 19 May 2012