Impact

This forum is read only and just serves as an archive. If you have any questions, please post them on github.com/phoboslab/impact

1 decade ago by coreysnyder

I'd been including 'impact.debug.debug' in my requires() in my main.js for a while. Just now when trying to port my app into Ejecta I found this line was causing me issues. The console in Xcode reads "Attempted to assign a readonly property. at line 80 in lib/impact/debug/graph-panel.js".

That line is: span.style.top = height.round() + 'px';

I suppose that makes sense since its dropping the UI for the debug outside of the single canvas element that Ejecta supports. Any plans on creating a Ejecta friendly version which you can define where in your game it places it?

1 decade ago by dannagle

I'd like to bump this thread.

What are good debug strategies when using Ejecta? The app behavior running inside Ejecta is not quite the same as when run in a browser. Something as simple as ig.log() support would be very helpful fixing quirks.

1 decade ago by Graphikos

You can use console.log()

1 decade ago by Joncom

With console.log, where would the message go?

1 decade ago by urkis

it shows up inside Xcode's log window.
I usually use the browser first for the basics.
Then Xcodes log for debugging.

and as @graphikos said console.log('lvlup')

1 decade ago by t3db0t

Console.log is an extremely limited debugging tool, and, IMO, severely insufficient. More discussion here:
https://github.com/phoboslab/Ejecta/issues/211
Page 1 of 1
« first « previous next › last »