lilybw

> This whole section might just be the cause of it. In general, I just can't recommend the use of `loading` and `error` properties over `Suspense` and `ErrorBoundary`, due to...

> The only way I am aware of to fix this, is to move the `SharedLibraryLoader` to a different package in jnigen. However, this would break every project that uses...

> The problem is more complicated in transitive dependency. If jnigen updates the package name, _every_ project that uses jnigen would need to do changes to be compatible again. It...

Update: I've finally come back around to this after forking jnigen and trying some different things. First attempt: Setting some manifest attributes to attempt to have jnigen be picked up...

> Why do you need modules here? I've only seen the existence of a module-info.java file cause problems... I don't know what you're trying to solve. They're another layer of...

> There are very few people familiar with modules in the libGDX community, and the ones who are familiar probably use it for work projects. I'm not sure where to...

> I'm familiar with Maven and use it occasionally. [This project of mine](https://github.com/tommyettinger/isonomicon) uses libGDX 1.12.1 and the LWJGL3 backend with Maven. It does not use JPMS, though. Thanks for...

> Hmm.. on one hand this is reasonable because unlike the underlying effect it never runs again which means that the return value isn't being used. On the other hand...