Christopher Serr
Christopher Serr
Currently we always split the timer onto its own layer. Since then we however introduced the same concept for the native renderer where accurate information about whether certain pieces of...
The problem is that we are using https and that prevents you from connecting to anything that's not https. So you can't easily run a websocket server locally and connect...
We need to think about whether we want this to be a component. This could also just be like the control buttons underneath the layout and you can toggle it...
We are currently throttling the framerate to 30 FPS. We could go up to the display's refresh rate, but that will negatively impact the battery usage. We probably want to...
If you download splits from the leaderboard in the Run Editor, it'll override the run that is getting modified by the run editor. However if you save that, there's two...
While "normal" auto splitting won't work in the web version, what can actually work is video based auto splitting. The web has a fairly easy to use screen capturing API,...
There's two Web APIs that we can integrate into LiveSplit One - the Web Share and Web Share Target API. They allow sharing data between apps (this is really common...
This is basically just a tracking issue for eventually supporting stepping through the Rust code in the browser. I already kind of got it to work:  However it seems...
This seems like a reasonable idea. Maybe even full themes. Here's how this could look: 
This came up for the original LiveSplit where people don't want us to communicate with SRL, speedrun.com and co. in the background. We should have some kind of Offline Mode...