-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
polygon3d ignores the "alpha" (and equivalent "opacity") argument #25095
Comments
Author: Yuan Zhou |
Commit: |
comment:3
For consistency, use alpha instead of opacity, see #21984. |
Changed keywords from IMA-PolyGeom to IMA-PolyGeom, alpha, opacity, transparency, 3d |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Reviewer: Jean-Philippe Labbé |
comment:11
Looks good to me. |
Changed branch from u/yzh/polygon3d_ignores_the__opacity__argument to |
The methods
sage.plot.plot3d.shapes2.polygon3d
andsage.plot.plot3d.shapes2.polygons3d
have the keyword argument "alpha" (as well as the equivalent, outdated "opacity" argument). However it is not passed to the plot function. For example,or
is treated as opacity=1.
Related tickets:
#21984
Update: The argument "alpha" is equivalent to "opacity" in all the 3d plot functions, such as
point3d
,line3d
,sphere
,icosahedron
,tetrahedron
,dodecahedron
,polygon3d
,polygons3d
,bezier3d
,parametric_plot3d
,revolution_plot3d
, `arrow3d', etc.#260, #9491, #15729, #21984, #23104.
CC: @mkoeppe @slel
Component: graphics
Keywords: IMA-PolyGeom, alpha, opacity, transparency, 3d
Author: Yuan Zhou
Branch/Commit:
93fe1e2
Reviewer: Jean-Philippe Labbé
Issue created by migration from https://trac.sagemath.org/ticket/25095
The text was updated successfully, but these errors were encountered: