Charley
Charley
Regards to the issue, I'm pretty sure it's because .NET Framework projects have no recognition of native runtime targets given it originally designed for Windows. But i'm no Nuget expert...
My suggestion on .NET Standard 2.1 is mostly because keeping SFML.NET on Standard 2.0 does restrict the library from potentially benefitting or supporting some of the newer things available like...
I don’t want to perpetuate the incorrect subject I accidentally brought up here but I just want to clarify. I totally understand why SFML is sticking with .NET Standard 2.0...
I've never tried SFML.Net on Linux, but i'm going to assume this error is due to the inconsistent naming of the csfml libraries between Windows and everything else. On Mono,...
Curious, was there any success resolving this?
For folks having issue on .NET Core, .NET 5 and 6, I think you've got to do some manual dll mapping as the csfml library names are different on non-windows...
I'm gonna assume the docs are wrong on this detail as they look copied from the [C++ documentation](https://www.sfml-dev.org/documentation/2.5.1/classsf_1_1VertexArray.php#a6006676417d91f42d0278f1abcfe4352) where this indexer does return a reference. I'd also imagine the VertexArray...
In this case, I don't believe the `Vertex` copy directly affects draw performance of a `VertexArray` as this indexer isn't used when drawing, but it obviously contributes to the time...
Would graphic resources created prior to a window getting recreated still be valid? _OGL context thinking sounds._
Added overloads for all Vector2 variants