I figured this out by adding
console print statements to the functions that were added for page callback and
noticed they were continuing to loop. There are only a handful of reasons for a
loop to not terminate and it was pretty easy once the loop was clearly terminal
as defined. So I back traced the loop variable just reading the code and
figured out that it wasn't actually in scope. In the app while looking at the
nodes widget, telling the console to print x showed it was changing, which
meant it wasn't in any scope and was acting at the root level and thus the
reason for the collision.
No comments:
Post a Comment