You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crux of these CAS issues sort've percolate from having an additional, third tier of functionality. This ticket is more of an overarching notification, rather than an actual implementation of a suggestive fix.
Some starting points are here:
showSublayers() either needs to be added to sub-sublayers (ports) or account for that use case everytime that appears
Activation of port layers produces weird results with the activeLayer logic and is part of the reason that deactivation of these layers don't work. If a single CAS port has been activated, you'll see that you can't delete them. During the next go around, add two ports and put a debugger within toggleActive ~794. You'll see that activeLayer doesn't behave the same way for both CAS port layers. This may be helpful for ticket [8 hours] Fix Activation/Deactivation Logic #3
//models.js:794 - in self.toggleActive()if(layer!==activeLayer&&typeofactiveLayer!=='undefined'){// are these CAS/VTR layers?
The text was updated successfully, but these errors were encountered:
The crux of these CAS issues sort've percolate from having an additional, third tier of functionality. This ticket is more of an overarching notification, rather than an actual implementation of a suggestive fix.
Some starting points are here:
showSublayers() either needs to be added to sub-sublayers (ports) or account for that use case everytime that appears
This fires every time a mouse click happens on the body - but currently, there's no subLayer of a sub-sublayer and produces an error.
Activation of port layers produces weird results with the activeLayer logic and is part of the reason that deactivation of these layers don't work. If a single CAS port has been activated, you'll see that you can't delete them. During the next go around, add two ports and put a debugger within toggleActive ~794. You'll see that activeLayer doesn't behave the same way for both CAS port layers. This may be helpful for ticket [8 hours] Fix Activation/Deactivation Logic #3
The text was updated successfully, but these errors were encountered: