2d-game-engine

In GitLab by @Comigo on Feb 24, 2019, 21:14

null

For an ui element made out of graphics::Canvas, is it better to

1. build a new ui::Canvas

2. make it so that ui::Image can accept either graphics::Image or graphics::Canvas

3. make it so that there's a Drawable trait that has fn draw<Q: IntoQuad>(&self, quad: Q, target: &mut Target), so that ui::Image accepts a &dyn Drawable trait object.

1 is the most logical given t

Would it be possible to add the Origin Rebase feature that is built into Physx 4.x and up into Echo?

This would enable larger worlds to be made without floating point precision errors. Here is an example of what can happen if you are too far away from origin. https://gyazo.com/a96db2d1a4ef8ff8935d2054597e151b

It would be nice if we could enable it in project settings and it was just part of

It would be nice to have a component that can expose the frames of an animated GIF image using the Animation interface; I'm picturing something like this:

import { useType, useNewComponent, GIF, useDraw } from "@hex-engine/2d";
import someGifFile from "./whatever.gif";

function MyComponent() {
  useType(MyComponent);

  const gif = u

v1
v2
v1.2
v0.5
v0.5.6

are all valid patterns

Right now, to inject version into ÖbEngine, it uses the last tag, so if you checkout to an older tag / branch, the version will not be correct.

This issue requires two things :

• if the current branch is named dev-vX / dev-vX.Y / dev-vX.Y.Z, use that version number (vX will become vX.0.0, vX.Y will become X.Y.0)
• if the branch

I think it probably makes sense to automatically install the dependencies on a new project after creating it. It would remove a manual step in the quickstart guide.

It does require that npm be in the $PATH though, maybe that's a problem in some cases. Also there are folks that prefer yarn over npm?

@ttulka How would you feel about this?

This one is pretty much what it says on the tin - the Maths namespace is lacking complete doxygen-based documentation in it's headers, especially when compared to a namespace such as ECS. Adding doxygen comments of similar caliber to the Maths headers will resolve this issue.