We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Craig
I think there is a bug due to a mismatch in variable positions in the initialisation call for PhysMember
In PhysMember, when you initialise the member the super init is called with "model" variable in 10th position
In Member3D, in the initialisation function, "model" variable is in 6th position
When I am initialising the PhysMember i get an error after updating the pynite to the latest version. Possibly due to this issue I think
Regards Lino
The text was updated successfully, but these errors were encountered:
That's strange. All my unit tests are passing. I'll look into this a bit closer. I just changed it, and all my unit tests failed.
Sorry, something went wrong.
I've corrected the code to be consistent across both classes. Newest version is v0.0.88 now.
v0.0.88
thank you
No branches or pull requests
Hi Craig
I think there is a bug due to a mismatch in variable positions in the initialisation call for PhysMember
In PhysMember, when you initialise the member the super init is called with "model" variable in 10th position
In Member3D, in the initialisation function, "model" variable is in 6th position
When I am initialising the PhysMember i get an error after updating the pynite to the latest version. Possibly due to this issue I think
Regards
Lino
The text was updated successfully, but these errors were encountered: