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

CSC263 cannot be made active after pressing 236 (with 207) #47

Closed
Ian-Stewart-Binks opened this issue Feb 18, 2014 · 4 comments
Closed

Comments

@Ian-Stewart-Binks
Copy link
Contributor

But 207 works. Note, it's an AND node. will look into this tomorrow.

@Ian-Stewart-Binks
Copy link
Contributor Author

General problem with index[0] and nodes.

@Ian-Stewart-Binks
Copy link
Contributor Author

Rather, Bools.

@david-yz-liu
Copy link
Contributor

Okay so what's the problem? I just tried it and it looks fine to me.

@Ian-Stewart-Binks
Copy link
Contributor Author

Have 236 be the last node you click before you would click 263, Problem
persists with 324, but not 410. I can't figure it out.

On Thu, Feb 20, 2014 at 12:27 PM, David Liu notifications@github.comwrote:

Okay so what's the problem? I just tried it and it looks fine to me.

Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-35646517
.

david-yz-liu pushed a commit that referenced this issue Feb 20, 2014
The problem for Issue #47 was the poor ordering of the recursive
isActive() calls made, which caused our program to check CSC263 before
bool1 was turned on. I fixed this by only making recursive calls to
children when the node's "active" status is changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants