Opened 9 years ago
Closed 6 years ago
#11275 closed defect (fixed)
bug in canvas3d html5 rendering of 3d plots
Reported by: | was | Owned by: | jason, was |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | graphics | Keywords: | |
Cc: | vbraun, ppurka, novoselt | Merged in: | |
Authors: | Reviewers: | Jeroen Demeyer | |
Report Upstream: | Fixed upstream, but not in a stable release. | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
In the notebook, try this:
First, in an input cell put this and evaluate:
G = sphere() #+ sphere((0,0,1),color='red') G.show(viewer='canvas3d') G.show(viewer='tachyon')
The above should work fine. Then remove the # comment in the first line to get
G = sphere() + sphere((0,0,1),color='red') G.show(viewer='canvas3d') G.show(viewer='tachyon')
Notice that the canvas3d output is wrong. What seems to happen is that if you modify a given input cell, then the canvas3d output *never* gets changed. This is very confusing.
Change History (13)
comment:1 follow-up: ↓ 7 Changed 7 years ago by
comment:2 Changed 7 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:3 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:4 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:5 Changed 6 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:6 Changed 6 years ago by
I figured out what this is - it's a cache busting issue with javascript or something like that in the browser. We figured out how to deal with this with jsmol, probably something similar should work here - as simple as the usual "?+random digits" trick, perhaps. May need to happen in the notebook code, though.
comment:7 in reply to: ↑ 1 Changed 6 years ago by
Possibly related:
var("y") plot(vector([1,3,4]),viewer='canvas3d')just brings up a Jmol thing, and plotting a
line
with this viewer brings up a black box.
Unrelated, this is actually the same as #17025.
comment:8 Changed 6 years ago by
I've finally reported this "upstream" at https://github.com/sagemath/sagenb/issues/255
comment:9 Changed 6 years ago by
This has a fix upstream that needs review at https://github.com/sagemath/sagenb/pull/284 . I really can't believe this was never fixed.
comment:10 Changed 6 years ago by
- Cc vbraun ppurka novoselt added
This is 100% ready to go, just needs a review upstream!
comment:11 Changed 6 years ago by
- Milestone changed from sage-6.4 to sage-pending
- Report Upstream changed from N/A to Fixed upstream, but not in a stable release.
- Status changed from new to needs_review
This is now merged, next sagenb update will have it - in #10057.
comment:12 Changed 6 years ago by
- Milestone changed from sage-pending to sage-duplicate/invalid/wontfix
- Reviewers set to Jeroen Demeyer
- Status changed from needs_review to positive_review
Fixed by #10057.
comment:13 Changed 6 years ago by
- Resolution set to fixed
- Status changed from positive_review to closed
Possibly related:
just brings up a Jmol thing, and plotting a
line
with this viewer brings up a black box.