Open lyndskirk16 opened 3 months ago
We're on it. Give us a second to figure out what's going on. I assume it's something to do with the fact that we recently implemented changing color of the objects directly in the 3D scene. This move may have broken things done from the object list.
Bueno!
On Tue, Jun 25, 2024 at 3:07 AM Michael Chirillo @.***> wrote:
We're on it. Give us a second to figure out what's going on. I assume it's something to do with the fact that we recently implemented changing color of the objects directly in the 3D scene. This move may have broken things done from the object list.
— Reply to this email directly, view it on GitHub https://github.com/SynapseWeb/PyReconstruct/issues/31#issuecomment-2188250281, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJNMGGVBR4M2VB2CIAJXBYLZJEQMXAVCNFSM6AAAAABJ2TE7XWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYGI2TAMRYGE . You are receiving this because you authored the thread.Message ID: @.***>
-- Lyndsey M. Kirk, Ph.D. Research Associate Center for Learning and Memory University of Texas, Austin
Describe the bug
When I change the opacity of an object using the object list (right click > 3D > edit 3D settings), and try to regenerate the object in the 3D scene (either by shift double clicking in the object list OR by selecting and reloading the object in the 3D scene, the new object opacity is not conveyed through the 3D object even though it appears to be saved. If I close the 3D scene and then generate the object it will now have the correct opacity.
Commit or version
6bca556
Desktop environment:
Windows 11
Python version
3.9.5