Skip to content

Supporting multiple API versions? #46

@ivan-mogilko

Description

@ivan-mogilko

I'd like to clarify a question of whether do we need to support multiple API versions in the standard templates.

For example, I've been testing the 3.6.1's preprocessor "#if/#else" in a VerbCoin template, where it has a switch between using Screen.Width and System.ViewportWidth, and when using pre-3.6.0 api setting the compilation failed on eKeyModCtrl use in on_key_press. Clearly there has to be more ifdefs for a proper old-style support.

Do we need to keep this support at all? Considering there are branches with old variants of these templates in repository.

EDIT: I just realized that new preprocessor command won't work at all if we support older editors. Unless I wrap them into #ifver, but that would make things quite dirty. So it's not about supporting older engines (editors) but about supporting older API levels. Fixed the issue title.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions