I would pay another $100 for a debugger...yet since the preview mode runs outside of C2 in the browser I can't see any way of getting it to work without having something like Glimpse
running (I'm linking to YouTube as his site seems to be down).
Maybe we don't need a full blown debugger with the ability to step through code (inside C2 I mean). Maybe we could get an extension to preview.js that has clearer list of all the objects and their values, as well as a simpler overview of where the program is currently pointing. I could live with not being able to step through my code if I could just add "runtime.sprite.player.X" to the Chrome watch window and see what the current value is. I'm sure something like that is possible now, but you have to wade through some pretty large objects to do it. The irony is we all keep asking for a debugger - we already have a debugger in our browsers, we just need a easier way to make sense of the data. Maybe that is a more realistic goal?
[QUOTE=Arima]You could also make your own 'debugger messages' by putting a text object on a layer and appending the text via an action.[/QUOTE]
For those who might not have seen it yet, I highly recommend using the Chrome logger
by wgfunstorm. It lets you spit out data and even arrays into the chrome console tab. Immensely helpful. (Note: I'm linking to the version I added array logging to - The regular version wgfunstorm is missing some files in the zip and he hasn't been on in a while to fix it).boolean2013-01-03 14:48:36