paul59

> _My 0.02._ I'm personally not sure it's good to slowly duplicate all the wiki content inside the application (and also and squeeze it into the tiny TIC-80 screen) -...

> As a variant, we could add something like clickable wiki links somewhere below the API description, or add a special `wiki` parameter to open the API help on the...

> > isn't much use without being able to see the key codes. > > Keycodes are included in the in-app help system also. I didn't know that - how...

> > I didn't know that - how are they accessed? > > `help buttons` and `help keys`, respectively! :) I added those a couple of weeks ago. > I'm...

I think the selection bar should go from 'options' to quit, not a selectable empty row between... either that or get rid of the blank line and move 'quit' and...

> I interpret as the pin being gray as it being "activated", but I can definitely see people having either interpretation What about the sliders in 'Options', grey when inactive/false?

> Those are blue / gray as opposed to gray / white, though I get what you mean Yeah that would work for consistency at least (and less to code/change...

From a practical point of view, why would you purposely insert trace() (without arguments) in a program? It handles nil values ok so it's 'debug-friendly' in that way.

> Calling `trace()` is not the only way to call trace without arguments. ... > Try running the first code example from the initial issue. Yes, I realise that but...

@joshgoebel thanks for that. It's been a very long time indeed since I did any C programming (best part of 30 years) so my recollection of what's possible is sketchy...