Skip to content
This repository has been archived by the owner on Feb 20, 2019. It is now read-only.

Implementing onActivate in a base class totally screws up eventing. #43

Open
philworthington opened this issue Nov 18, 2014 · 1 comment
Open

Implementing onActivate in a base class totally screws up eventing. #43

philworthington opened this issue Nov 18, 2014 · 1 comment

Comments

@philworthington
Copy link

Because the View has "this._root.bind()" in onActivate, that means that every subclass of View must call super.onActivate() in their onActivate. This is pretty confusing and super difficult to debug.
@xirzec
Copy link
Contributor

xirzec commented Nov 18, 2014

Agreed! Good catch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xirzec @philworthington