Alaric.Baraou

I'll take a look at this this week or the next. There is probably no need for it to run on each frame for each component indeed. Anyone interested, feel...

> a 3d rendered cursor (that can change in any way to present information such on hovering) I really like this part, I can already imagine how with such smart...

> pause menu: small point, but the user should expect the same experience across every device (mobile/desktop/vr), and on vr there's no place for a 2d pause menu. obviously most...

> The current approach seems fine to me, what is your reasoning for delegating to frameworks? Is there a performance impact? I feel like I should try keeping event listeners...

I think I'm good with all of the above. Regarding the (4 when flat, 8 when curved) advice, I went with 8 all the time because as soon as your...

>the geometry's bbox has only 4 corners when non-curved While I want to agree with this because when it's non curved it's a plane, the three.js bbox helper is showing...

@lojjic Looks way better thx ! >The alignment is improved, but: >- It doesn't always completely cover the text when there's a curveRadius >- I didn't test with a custom...

Main change : You can enable accessibility without enabling selection. But enabling selection will always enable the accessibility. I've fixed a few "bugs" when testing it with drei but now...

I totally understand the reasoning and it makes perfect sense. I took a day to think about the separation of selection and accessibility. I wasn't expecting it because the selection...

> Am I just overthinking this? In my opinion you're totally right. It's mostly my tendencies to do fun quick stuff that works more than solid clean code that fits...