Skip to content

Merge patch-1 branch with master #2

@Boobies

Description

@Boobies

For some reason the corrected link is in the patch-1 branch, you should probably merge that. Although when editing the link you forgot the trailing _ so you should go ahead and add that back.

PS: After finally changing ShivaVG's "temporary" context handling to EGL (see #3) I have fonts/gyphs on the way. I will hopefully get around to finishing it this weekend. But given that I'm not sure you are ever coming back, it is not worth it for me to continue working on clean feature branches. I will keep the current PR clean and then build on top of it in a separate branch continuing to work on the project normally so I don't have to deal with merge conflicts forever.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions