At the moment the main issue hindering my use of gibberwocky is present in both editors. I’m having problems while re-evaluating lines of code controlling gen~ functions (this is what throws out the error in the screenshot I guess). When evaluating a control function - for instance track[0].volume(mod) where mod is assigned to a phasor(1) - for the first time, everything is cool and I can see the graph popping out and showing me the signal. If I then decide to sequence phasor frequency like mod[0].seq([0.5, 1], 1) and evaluate this line, nothing happens (therefore I guess I have to go back to the track[0].volume(mod) line and evaluate that again. If I revaluate the line, I get an error telling me something like the graph being not ‘accepted’ as parameter and I have to delete that before re-evaluate (and to re-input the very latest ) which got deleted when the graph instanciated before). Re-evaluating the line I see a new graph popping out but it’s either empty or displaying a still 1 or 0 value. The automation is also not received correctly by the controlled parameter. In order for it to work I have to delete the graph again and re-evaluate the line. It’s also natural for me to think that changing the signal values outside of that very specific control function should be enough to change its output and the waveform displaying on the graph.
Doing few researches I have found nothing related to this issue and I’m afraid I’m the one who’s doing something wrong, but can’t really figure it out… I tested against this issue on either Brave and Safari without success.
Thank you so much for your help!
@charlieroberts after a bit of further investigation I can add another detail to the graphs behaviour. Looks like they freeze only if I re-evaluate the line of code with ctrl and not with shift. Hope my report is making sense 
