Axel Bocciarelli
Axel Bocciarelli
Getting back to this, sorry for the radio silence 😅 While I don't deny that one might confuse these two flags, I still think that their two greens and their...
> Note that it could potentially be refactored to a service worker that uses the same API as a grove server, if that simplifies things. This would be brilliant! However,...
It's definitely going to help. @bmaranville also developed a [`lazyFileLRU` demo](https://github.com/bmaranville/lazyFileLRU/blob/main/src/lazyFileLRU.ts) to show feasibility. However, the amount of code required and its complexity has me worried a bit; it's not...
I agree that the debouncing is not ideal. Our main goal at the time was to avoid spamming h5grove with concurrent requests while keeping the slider responsive. I think this...
> In the scenario proposed above, where a user has moved the slider from 0 to 1 to 2, there would be no benefit to the user from starting a...
Right, I get you now, but there's still something I don't quite understand. Let's imagine we're dealing with much slower load times, say 10s per slice. You're on slice 0...
Right, it's what you say in your last sentence: "The largest possible delay to the user seeing the frame they stopped on is the time it takes to fetch and...
Yeah, only downside is, you have to actually release the mouse pointer for `onAfterChange` to be triggered. To be honest, I think we need a combination of all the above:...
### Attempt #1583 - I remove debouncing on the `dimMapping` state. - I use `useDeferredValue` on the `dimMapping` state to opt into React's concurrent rendering. This means that the suspense...
Latest progress: - I've removed debouncing on the dim mapping state in #1634 - I've tried once again to use `useDeferredValue` (i.e. concurrent mode) to not show the suspense loading...