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

Fusion backwards compatibility #4

Open
BigRoy opened this issue May 16, 2015 · 1 comment
Open

Fusion backwards compatibility #4

BigRoy opened this issue May 16, 2015 · 1 comment
Labels

Comments

@BigRoy
Copy link
Member

BigRoy commented May 16, 2015

Newer versions of Fusion come with better methods for checking the type of an object that could ease the conversion from PyObject to the correct type. But using that automatically drops support for Fusion under 7.0. Whilst at this stage 6.0+ is also supported.

I'm raising this issue here to see what other people think about how far back we want to support Fusion versions. If we choose to stay only compatible with the Black Magic Design releases of Fusion that would be 7+. Though I know some are still operating with Eyeon's 6.4 releases.

Goal

Get a feeling of the current versions being used in productions and the importance of being backwards compatible with fusionscript over time for much older versions.

Reference

This topic briefly covers the IsClassType method only available in Fusion 7+

@BigRoy
Copy link
Member Author

BigRoy commented Sep 5, 2016

With the refactoring of the package to fusionless from the original fusionscript along with some of the latest commits this also became compatible with Fusion 8+ (alongside still supporting Fusion 6). The issue as described above still remains a valid question.

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