Debugging waves with onPaint()

Fragment of a discussion from Talk:Robocode/Graphical Debugging
← Thread:Talk:Robocode/Graphical Debugging/Debugging waves with onPaint()/reply (9)

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).

MN‎

You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in the group: Users.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

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

Return to Thread:Talk:Robocode/Graphical Debugging/Debugging waves with onPaint()/reply (10).

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

Retrieved from "http://robowiki.net/wiki/Thread:Talk:Robocode/Graphical_Debugging/Debugging_waves_with_onPaint()/reply_(9)#Debugging_waves_with_onPaint.28.29_807"