Traces in engine code

[Gama11]

I'm not a fan of having traces in engine code. I made sure they are all encased by debug-conditionals, but still, that doesn't really solve the issue - personally, it would annoy me to no end that my own traces are lost in the flood of the engine's own traces.

Two options:

• Remove them entirely
• Create a flag like FlxUI.debug to toggle them (not a fan of introducing new compiler conditionals where not necessary)

[gamedevsam]

Where are there traces in engine code? Did I accidentally leave some debug code?

[larsiusprime]

Probably my fault. I'll see if I can track them down and fix them.

[Gama11]

@crazysam We're talking about flixel-ui here.

@larsiusprime Finding them is pretty easy via FD's find and replace. But I thought they might be there intentionally?

[larsiusprime]

Just a bad habit of mine. They can be removed, hidden behind debug flags,
or switched to FlxG.log

On Sat, Jan 11, 2014 at 1:37 PM, Gama11 notifications@github.com wrote:

@crazysam https://github.com/crazysam We're talking about flixel-ui
here.

@larsiusprime https://github.com/larsiusprime Finding them is pretty
easy via FD's find and replace. But I thought they might be there
intentionally?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-32104843
.

www.fortressofdoors.com -- Games, Art, Design

[Gama11]

Alright. Do whatever works for you! :)