Skip to content

[3d-opengl] Don't take glm objects as parameters or store them #7

@SeanOMik

Description

@SeanOMik

Branch: feature/3d-opengl

A lot of places functions will take in a glm::vec3 (or some other glm type) as a parameter, or a class will store them in an accessible way to the engine user. Other places we're taking in a simpleengine::Vectorf. It would be better to be consistent and use the same type.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions