Clearer event dispatch

[imJames]

When you use portals, events are hard to manage. I mean, some events will be fired twice or in an order that is not easy to guess. I don't really understand what the events cascading order is.

And when you have portals into portal things get worse.

I find myself writing quite a lot of code to solve that.

For example what I do is the put a lable outside the form (on the left) and set a text value into it when the event is fired (the text value represents the input of the method that will update the view).

If the same event is fired another time, I check the value of the label to determine if I should actualize the view of not.


I put this request in "feature request" because this is not a bug.

I don't have any good solution to give you but I wanted to let you know the difficulties I'm experimenting.

[IT2Be]

Don't use portals and certainly when things are more complex. Instead use table view or list view. Much more flexible and controllable...

[imJames]

Did I say portal? I wanted to talk about tabpanels

Inside a tabpanel I put forms which sometimes contains another tabpanel to show a list for example.

[Harry Catharell]

When you use portals, events are hard to manage. I mean, some events will be fired twice or in an order that is not easy to guess. I don't really understand what the events cascading order is.

And when you have portals into portal things get worse.

I find myself writing quite a lot of code to solve that.

Despite the fact that portals have been mistakenly quoted instead of tabs, there is a good point here regarding event firing order which I fall foul of a lot with things like tabs within tabs.

Is there a resource anywhere which has a definitive order of precedence in which events are fired and, just as importantly, when events don't fire when you think that they should

Cheers
Harry