You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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+
The text was updated successfully, but these errors were encountered: