Jon Abrams comments

Results 36 comments of


                                            Jon Abrams

undefined local variable or method `form_buffers'

@rbatllet Thanks for the fix. Why not open a PR?

Pinball FX3 only shows half a screen (Vulkan) and black screen with sound (opengl) when updated from 1.0.0 [AMD - GCN issue]

This happens to me with every version of Pinball FX 3 I've tried **except** for base 1.0.0. Using latest Yuzu on Steam Deck (Vulkan + AMD).

Menu is closed before menu item click is handled

Sure, it's embedded in my project's codebase, so I'll have to break it out when I have some time. Feel free to close the issue in the meantime. Oh, and...

Menu is closed before menu item click is handled

I just did some more experimenting, I think the problem only occurs when `animate: false`. I think the menu closing animation is providing enough time for the menu item's `onClick`...

Menu is closed before menu item click is handled

Note: Setting `leaveTimeout` and `enterTimeout` both to `1`, and enabling the animation, gets it to work, but without a visible animation. Maybe have `animate: false` just set those two values...

Store a list of hashes

It would also allow me to add support for save states to [retropatcher](https://retropatcher.jonabrams.com/)

Cannot set property createElement of [object Module] which has only a getter

I don't think there's any need for signals to hook into React for SSR, since the state will never change server-side. Therefore, it should be enough (🤞) for signals-react to...

Cannot set property createElement of [object Module] which has only a getter

Try the library I just published on npm ([signals-react-safe](https://github.com/JonAbrams/signals-react-safe)), it fixes the re-rendering issue.

Cannot set property createElement of [object Module] which has only a getter

To have the component re-render when a signal updates, use the `useSignalValue` hook I added.

Cannot set property createElement of [object Module] which has only a getter

Under the hood `useSignalValue` uses `useState`. So it means you can only use it in client components. I should look into if it's possible to avoid using useState in server...