tcstewar

> Interface wise, are we thinking of just putting it inside the context menu that you get from left-clicking on a network? Additionally, do we want to extend the hue...

+1 I totally approve of getting rid of these... Still little bits of my bad coding habits sneaking through.

This would definitely still be handy. In recent debugging of SPA modules, I've also found it handy to have these be cloud plots (so that it's easy to see what...

The problem is that the function isn't called before the Simulation starts to run, so `_nengo_html_` isn't set before the simulation starts, so the GUI doesn't know to give you...

> Hummm...why does it work for both nodes though if you uncomment both lines? Because you're not specifying `size_out`, so it has to call the function _right away_ to figure...

> Ah so since I've only specified size out for one node, if it had to check size out for one node it checks for all? Hmm... no, that shouldn't...

Hmm... would it make sense to just modify the AceEditor such that it'll automatically pop itself open if the error message gets set? That seems like a useful feature in...

> But there is no code to display ... So the code window will be blank, but the area below that that shows the error will still be shown.

> Yeah, but wouldn't a blank code window be strange? Though, it might be better for now than not displaying errors at all. Better than not displaying the error at...

I'm now thinking a better option would be to send that error to std.error and allow Jupyter to show it instead. That might be a quick thing to try implementing....