Skip to content
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

[8 hours] Fix Activation/Deactivation Logic #3

Open
3 tasks
dnseminara opened this issue Oct 4, 2016 · 0 comments
Open
3 tasks

[8 hours] Fix Activation/Deactivation Logic #3

dnseminara opened this issue Oct 4, 2016 · 0 comments
Assignees

Comments

@dnseminara
Copy link
Contributor

Current implementation is borked - both in the Data Tab and the Active Tab as it doesn't use the same self.toggleActive() functionality as most of the remaining layers. The root of the problem lies within the additional third tier/dropdown. Currently, MARCO only supports layers and sublayers - not sub-sublayers.

screen shot 2016-10-04 at 10 42 45 am

  • An activated port, should turn on the green check for its parent (date ranges) AND its grandparent (gear type) in the Data Tab
  • Date Ranges and Gear Types should only be active if their child is activated. For instance, if a port is activated when one date range, only that date range should be activated.
  • Activated CAS layers should be removable in the Active Tab
@pollardld pollardld self-assigned this Oct 4, 2016
@rhodges rhodges assigned rhodges and unassigned pollardld Oct 24, 2017
@rhodges rhodges changed the title Fix Activation/Deactivation Logic [8 hours] Fix Activation/Deactivation Logic Nov 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants