Drawing two objects on the same page causes one to be made invisible (as of v5.1.0)
See original GitHub issueI have a case where I draw two histograms on the same page in quick succession and when I upgraded JSROOT to version 5.1.0 (from 5.0.3), both histograms are ‘plotted’ (i.e. they show up in the Chrome Developer Tools inspection) but one is visible="visible"
and the other is visibility="hidden"
.
If it is important, the plots were simple TH1 plots, generated in ROOT beforehand.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Turn Your AutoCAD Objects Invisible (Lynn Allen ... - YouTube
For years, we've used layers to control the visibility of objects in AutoCAD — but that approach can be very tedious.
Read more >AutoCAD Tutorial | Object Properties | CADTutor
In AutoCAD the display of one object in relation to another is determined by the objects place in the drawing database. Objects drawn...
Read more >Transparency flattening (Acrobat Pro) - Adobe Support
If your document or artwork contains transparency, to be output it usually needs to undergo a process called flattening.
Read more >Face culling - LearnOpenGL
Face culling. Advanced-OpenGL/Face-culling. Try mentally visualizing a 3D cube and count the maximum number of faces you'll be able to see from any ......
Read more >Common Mistakes - OpenGL Wiki - Khronos Group
The compiler-generated copy constructor is wrong; it copies the OpenGL object name, not the OpenGL object itself. This leaves two C++ objects ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fine
I’m satisfied that this issue has been addressed with the changes discussed. Shall we close @linev?