The idea of using the buffer output from imgui is specifically to avoid needing to deal with those platform specific functions.

Rather than basing your work off C++ imgui examples, you should look at how we do it in hlimgui/heaps, the same concepts should work fine, they just need tweaked to play nice with Lime

@tall-teacher-57409 Critically, hlimgui needs to work with all heaps backends (SDL, DX, and in the future vulkan/dx12 when cannasse finishes those up). Our implementation strategy lets us cover all of those without any platform awareness from hlimgui.

I get it and thanks for the suggestion, but when saying lime, I mean pure opengl (almost), so it's deffo not very straightforward to port over from heaps, but we're trying in #1109854315272753253

How would you create levels whose contents are not known at compile time? I could, in theory, use json to store all the level data, but is there any easy to use library that has already implemented this? I am new to game development but not to programming, so I don't know much about the ecosystem for heaps

The intended use for this is to enable user generated levels, so it would be preferable if the loadable levels don't allow directly executing low level code.

Not really, that’s usually a very custom thing. You could somehow implement that with ldtk

Alright, it shouldn't be too difficult to implement

Hey all. Anybody know of any basic physics libraries that integrate nicely with Heaps, or do you usually just roll your own?

I don't need anything complex like Box2d, just something to do bounds checking/clamping positional values based on collisions

echo, but it may bring more than what you need

differ is a pure collision, no physics lib if you'd prefer that

Differ seems like it might work! Thanks! :D

I spent some time over the last couple days trying to roll my own collision detection, and it reminded me that I'm bad at coding things when I know next to nothing about them

I do most of my programming in Odin nowadays so I'm pretty well used to having to roll my own stuff

I actually hadn’t heard of differ before, that would work for me in places where I would have used echo for pure sensing objects

I use Echo, personally. It is a bit like Box2D, but I find it very simple to use. I was up and running in about 10 minutes with it.

It's also very extensible.

replaced (out of curiosity)

hxd.Res.initLocal();

with

hxd.Res.initEmbed();

and faced quite an error:

Compiler failure
Please submit an issue at https://github.com/HaxeFoundation/haxe/issues/new
Haxe: 4.3.1; OS type: windows;
File "src/generators/genhl.ml", line 3678, characters 41-48
Called from file "src/generators/genhl.ml" (inlined), line 3689, characters 19-39
Called from file "src/generators/genhl.ml", line 3810, characters 3-27
Called from file "array.ml", line 93, characters 31-48
Called from file "src/generators/genhl.ml", line 3809, characters 2-108
Called from file "src/compiler/generate.ml", line 99, characters 2-14
Called from file "src/compiler/compiler.ml", line 332, characters 29-64
Called from file "src/compiler/compiler.ml", line 347, characters 1-5
Called from file "src/compiler/compiler.ml", line 434, characters 2-162
Called from file "src/compiler/compiler.ml", line 408, characters 2-9
Called from file "src/compiler/compiler.ml", line 630, characters 5-43
Called from file "src/compiler/compiler.ml", line 640, characters 13-22
Called from file "src/compiler/server.ml", line 979, characters 1-39
Called from file "src/compiler/haxe.ml", line 53, characters 0-56
File "src/core/globals.ml", line 156, characters 1-7: Assertion failed

Why would it ask me to create new issue tho, thats confusing

Usually you put that in places where you have no idea how to replicate an error and need to rely on reports from others

because it is a compiler error

you've come across a situation that isn't accounted for

quite important to report as it improves haxe as a whole

Well then, going to report it

if you can create a simple test case, maybe just a heaps init for someone to unzip and compile that would be extra useful

Oh, its very simple

provide the code and the setup and they'll figure out the issue!

There is

Main.hx

class Main extends hxd.App {
    override function init() {
        hxd.Res.initEmbed(); // <- that's it
    }
    static function main() {
        new Main();
    }
}

build.hxml

is just like for fresh new hl build:

-cp src
-lib heaps
-lib hlsdl

-D no-deprecation-warnings # <- prevents ALOT depr warnings from hxd/Res.hx:4
-hl bin/hl/build.hl
-main Main

Fails for me on current night builds of HL and haxe

perfect!

Super easy test case, that’s rare