Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supporting multiple API versions? #46

Open
ivan-mogilko opened this issue Dec 2, 2023 · 0 comments
Open

Supporting multiple API versions? #46

ivan-mogilko opened this issue Dec 2, 2023 · 0 comments
Labels
Milestone

Comments

@ivan-mogilko
Copy link
Contributor

ivan-mogilko commented Dec 2, 2023

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.

@ivan-mogilko ivan-mogilko added this to the 3.6.1 milestone Dec 2, 2023
@ivan-mogilko ivan-mogilko changed the title Supporting multiple engine versions? Supporting multiple API versions? Dec 2, 2023
@ivan-mogilko ivan-mogilko modified the milestones: 3.6.1, 3.6.2 Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant