> Changed: Controller inputs are accepted even when PICO-8 is not the foreground application
PLEASE change this back. This is totally counter to how apps are supposed to work in a windowing environment. If an app doesn't have focus, the whole point is that it's not the one receiving input.
This is causing problems for me already because I can't safely pause a PICO-8 game while I play something else that uses a controller.


... or make it optional, @Felice. By default yeah it shouldn't. But with an obscure POKE it could be enabled. I'm not sure I just don't like the idea of removing it entirely. There are some programming languages like Blitz that can read keystrokes even if the window is not focused.


@kittenm4ster
Yeah, as mentioned above, I think features like this are fine as long as they're opt-in. I imagined there were use cases like yours.


Alright no problem -- it's now optional (and off by default) for 0.2.4c. I have to admit I thought "who's going to be running a PICO-8 cart in the background while they are using the controller for something else?". Lack of imagination.
@Felice -- fwiw, there's a lot of overhead in releasing an update, so I generally can only justify doing hotfixes when there are severe show-stopping bugs, and even then only when there aren't other pressing things going on. It's perhaps inadvisable to juggle so many projects as a solo developer, but these are the side effects and PICO-8 wouldn't exist in the first place otherwise ¯\(ツ)/¯


There are cases where you'd want to leave the cartridge running when not in focus -- e.g. listening to background music or defragging your PICO-8.


May I suggest that, if there's that much overhead in the process of releasing an update, then your current project ought to be to find a way to streamline that process.
You've been talking about creating a new game development platform/ecosystem in Picotron, where other creators can make and publish full games or apps or whatever. If you can't update a simpler platform like PICO-8 with any kind of regularity or timeliness, that's going to turn into a much bigger problem with Picotron.
Sorry, but I'm going to keep hammering on this point.
[Please log in to post a comment]