Debugger Improvements

[vlaaad]

We released a series of improvements for Lua debugger:

• Better handling and displaying of values with circular references. Previously such values could hang editor or engine on breakpoints. Now we make sure to handle it gracefully, and allow to infinitely drill down to such values in Variables panel:
  
  
• Displaying errors of evaluation results: now if your evaluated code results in error, it’s printed instead of being silently swallowed:
  
• Pretty-printing evaluation results: now your tables are pretty-printed and can be read more easily:
  
  

If you avoided debugger previously because of its unreliability, I’d suggest you to give it a try now, and tell as what you think!

[dapetcu21]

It feels mature enough to use it now. One thing I’d add is some history for the “evaluate lua” box. I’m used to the Chrome Dev Tools where I can type an expression, press enter to view it, then press up arrow to continue editing it.

[vlaaad]

True, I have the same habit, and it doesn’t work there. We should add that.

[ItsPixel]

+1 Really missing this feature.

[connor.halford]

Great improvements

[vlaaad]

Just pushed an update that improves performance on evaluating large data structures (such as _G) — no more editor freezes!

[vlaaad]

Another minor improvement added: history in Evaluate Lua text field, accessible by pressing Up.
Check for updates!