Point 6 is present in both Firefox and Chrome on my Windows laptop, but not on iPhone. I guess the real issue is just when the editor and documentation are open side-by-side, not necessarily the act of showing/hiding the documentation. But there’s another thing. (Isn’t there always?)
- The documentation appears superimposed over the controls if the window is narrow enough. This is automatically true on iPhone, and I should have thought to try it on PC too because it happens there too. In this situation, though, line wrapping in the editor works as expected.
However, it switches too early to having the editor & documentation side-by-side again, when the editor is too narrow to be usable. That width threshold should be higher:
- There’s a possibility for circles to get stuck in the bottom edge of the animation window. Collisions with other circles can sometimes free them. On iPhone, this frequently happens when I scroll the page up and down, but this doesn’t happen on my laptop.
It can happen on my laptop if I resize the window while the animation is running, and in fact any circles caught outside the new bounds of the animation pane stay offscreen. It appears they continue to bounce vertically up and down but do not interact with one another. For example, here I have a bunch of Play circles and some Synths that are offscreen. The line from the F#G#C# Chord going offscreen keeps moving as if the Synth it’s attached to is still moving, but I don’t hear anything anymore.
But if I resize the window with animations hidden, I do still hear the “offscreen” ones even when I show the animations again! (Example: load & run “Multiple rules example”, add a ton of Synths & Chords & Plays, click “Hide animations”, make window much narrower, click “Show animations” – you’ll hear sounds being triggered even when any on-screen Play circles haven’t collided with anything)
I’m not sure what the best way to handle this situation would be… This stuff about small screens or resizing the window might not be worth your time!
I’m sorry I’m not providing more feedback other than bugs or criticisms, but if #2 and #6 were fixed it would be a lot easier to play with the prototype and try out different combinations of rules and such.