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

Fixed polygon3d rendering bug issue #178 #1928

Closed

Conversation

ianthomas23
Copy link
Member

This is a candidate fix for the mplot3d polygon rendering bug of issue #178; it will also allow PR #1299 to proceed.

The changes are all in the mplot3d code, except for one new function in collections.py which is only called from mplot3d code. With this fix the test script added by @WeatherGod to #178 works OK, and all the existing mplot3d examples work as before.

The code changes are not elegant, but are consistent with existing mplot3d code.

I haven't PEP8'd the changes as the original mplot3d files haven't been PEP8'd yet.

seg3d = [juggle_axes(x, y, z, zdir) for (x, y, z) in seg]
return seg3d
return seg3d, codes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This changes the API of this function. The correct way to go about this is to deprecate this one and have a new function set up to replace it. Or, have a kwarg defaulting to False to indicate whether to return the codes as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@WeatherGod: I have changed all code that calls this and the other function you have highlighted. I see these as internal (i.e. private) functions, even though they are do not have leading underscores.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are not private. These are public methods to objects that people do manipulate in the wild. You will have to go through the proper process for this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants