Fedor Logachev

Hi, thanks for the work done, custom events look interesting! But with current implementation it is possible to use only one type of custom events over the whole application, right?...

> This approach would mean that if the message arrived just after we started sleeping until it was time to draw the next frame Yes, but it basically the same...

Now, this is implemented on windows/wasm/linux! https://github.com/not-fl3/miniquad/pull/173 Thanks again, @scurest! Marking the issue as "Help wanted" as a call for help for mac os implementation :)

The VertexLayout is more about data layout in the memory buffer and the Vertex struct representation. For example, VertexLayout for instancing rendering will say something like: the attribute "position" is...

And another example: ``` VertexAttribute::with_buffer("pos", VertexFormat::Float3, 0), VertexAttribute::with_buffer("color", VertexFormat::Float4, 1), VertexAttribute::with_buffer("normal", VertexFormat::Float3, 2), `` here each attribute lives in its own gpu buffer. Shader does not care about this stuff,...

There are two solutions: - get rid of docker and install all the android things locally. Will give the best results - skipping docker will save a few seconds -...

Fixed that specific error and now it builds for arm-unknown-linux-gnueabihf But I am not sure that miniquad will works on raspberry - afaik there was some raspberry-specific GL loader required.

Hm, interesting, `_` works for me with `cargo build --arm-unknown-linux-gnueabihf` and I can't see the difference with `_` and `u8`. How do you compile for raspberry? Any way to reproduce...

Just tried on the raspbian and it works for me. (just for the record - miniquad took 13 minutes to compile in qemu and raspbian). Could you try it again...

awesome, thanks!