wfc VS pasvulkan

I always forget to do this for new projects, but I use trunk fpc/lazarus and this busts older installs unless a project setting is applied to maximize compatibility. I've checked this and pushed up the commit, so if you re-pull, close laz, reopen the a major lpi you should see the units. also one thing to note is that this uses SDL2. I included the win32 binary in the bin directory here https://github.com/mr-highball/wfc/tree/main/examples/music/bin

nice. had a similar idea to use my implementation for some dungeon generation (did not think to productize it... but good job 👍). would be interested to know some more on the limitations you found with wfc. mine's a 3d graph implementation so things like walls I was planning to implement in the z (vertical) layer, but had an idea for coding a concept of "passes" which could do things like furniture/lighting/decoration placement etc... https://github.com/mr-highball/wfc

This guy Bero1985 wrote the 3D library / engine some years that has extensive 2D features including UI that uses SDF among the other things [0].

[0] - https://github.com/BeRo1985/pasvulkan

That reminds me of another project. Whatever you do, do not write the commit messages like that, and your are doing great: https://github.com/BeRo1985/pasvulkan/commits/master

This is the code from the PasSDL unit, it is included in Pasvulkan on github( pasvulkan/PasVulkan.SDL2.pas at master · BeRo1985/pasvulkan · GitHub, line 1284). Wanted to ask if anyone knows how to rewrite this to make it compile in PABC cuz it doesn't support this kind of notation.