Josh Goebel

I'd probably prefer just using the larger struct when we can vs creating a local pointer. ``` static inline void updpal(tic_core* core, tic_blitpal* pal0, tic_blitpal* pal1) { tic_mem* mem =...

Why? Is this more about "class" field privacy or separation of concerns? > the studio shouldn't know anything about tic_core It kind of knows a **lot** actually since it's calling...

Oh wow, this is neat. Let me give it some thought. I think up/down works really well for audio... but you could pair it with a beep or something for...

> but you could pair it with a beep or something for "on" at least I think. Actually I think a 8x8 icon could probably be squeezed in reasonably also.

> I considered those kinds of things but wanted to keep code size minimal. Either is doable if we can afford the space. I've cut over 4kb from the compile...

Although I suppose if it's one mode you might need to do both on the same screen, so that would affect the design a little. There are theoretically 10-12 useful...

A fully on screen isn't the best thing to judge the brightness though. If there was a way to mix both the settings on as screen that would give you...

I don't even think you need to hold B now... B gets into settings then up/down left/right changes things, then A/B saves.?

> Just seeing the entire screen inverted would suffice for that, wouldn't it? Well, it's the reason Apple changed the way brightness works on the iPhone. You know what I"m...

> Currently, my code saves immediately when the action button is detected, but only if he change is required. The release of the B button just exits the scan loop....