alvinhochun

Update: I got it working in an acceptable manner. The code now looks like this: ```rust fn draw_text( window: &mut Window, camera: &FirstPerson, text: &str, pos: &Point3, scale: f32, font:...

@caemanswartz I'm not seeing your point. In your code you multiply the coordinates by the window size and then divide the result by the same window size, which is almost...

I just realized that the PR #207 I am working on is related to this issue, at least it solves the third point. The first two points however I don't...

> ```toml > [package] > name = "voxelgame" > version = "0.1.0" > authors = ["rohan "] > edition = "2018" > > # See more keys and their definitions...

I think it is worth analysing the backend situation for a bit. Currently there are two backends in Kiss3d - glutin (native target) and stdweb (web target): Regarding glutin: -...

But I do wonder, if all this work is needed is it really worth supporting the *unified pointer event model* in Kiss3d? The idea of a *unified pointer event model*...

It's not absolutely necessary to deprecate `Window::render`, but it does mean there will be two separate code paths for handling the event loop since `Window::render_loop` will no longer use `poll_events`.

> 1. Is WASM support ready? I couldn't get the example project to build, and I saw some recent activity around WASM support so I'm not sure if it's still...

The problem is that it now treats char-strings as UTF-8. In some way this is a good thing, but the typical convention on Windows is that char-strings (PSTR / LPSTR)...

It seems that the problem here is the lack of a generic way for users to handle native events that aren't handled by Winit. Since Winit is in control of...