Josh Goebel
Josh Goebel
Ok in taking a closer look I think the desire to set row (to start/stop music) is misguided. Actual playing state is determined by `mode` (see [docs](https://github.com/nesbox/TIC-80/wiki/RAM#sound-state)) so if one...
Actually looking more it might work just fine... Audio processing loop get killed pretty early if mode = 0 ("stop")... so I think you could pause/unpause with `0/non-zero` ... What...
> Yes, poking 0 or 1 (I still don't know if there's a difference) Oh, it's because `mode` is actually LOOP + STATUS with loop being the low bits... so...
We could probably special case the audio state to handle `poke(rows, 3)`: ```js // ie, we've updated `rows`, but not via the music API if (previous_audio_state.rows != current_audio_state.rows && music_api_not_called)...
> So either being able to get pattern and row through the API (to provide them manually when starting the music again) ```js pattern, row = peek()..., peek()... // resume...
I simply think this use case is not common (pausing and resuming at an exact spot) and we strive to have a minimal core API. It's easy to peek these...
> wasn't there a way to add elements to it Yes, there is a new meta tag (and callback) for that, but I forget the name. It's not documented on...
Can you confirm this is still an issue and provide a screen shot?
We only support a single type of block string syntax in our highlighter...and currently this is set to `[[` and `]]`? What is the difference between that and the `[=[`...