events weird behavior

[ilia]

See test_Tree_9. It should destroy tree with all implicitly created widgets (selector, controller), but actually it doesn't.

The reason is that one of them recieves the treeDestroy message (event.topic) and kills itself, while another one (registered right after 1nd one) does not recieve anything.

[bill]

Heh, that's a good one. I assume it's because the code to call the 2nd one is stored inside the first one. (That's not how it works conceptually, but it's how it works internally.)

I'm not sure if we should think of this as a design flaw or what, but one way to workaround the problem should be, instead of the 1st object destroying itself instantly, set a timer for 0ms to destroy itself. like resizeSoon(). Maybe that would work. (hypothetically speaking)

[ilia]

The next statement right after tree destruction can be "make new tree and new controller with same name".

The suggested workaround will not handle this..

[bill]

Well, on second thought maybe my theory doesn't make much sense anyway. But what's supposed to happen if a function deletes itself (while it is running) anyway?

[alex]

no idea what's going on after nearly half an hour of debugging. Punting to 0.3.1

[Dustin Machi]

I'm not sure exactly why this one got assigned to me, nor do I currently have any idea how to fix this.

[alex]

punt.

[bill]

Fixed by Fredrik in [4461]

[(none)]

Milestone 0.4 deleted