#1221 closed defect (fixed)
TreeWithNodes.setChildren fires afterAddChild
| Reported by: | ornus | Owned by: | ilia |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Widgets | Version: | 0.3 |
| Keywords: | tree | Cc: | |
| Blocked By: | Blocking: |
Description
When nodes are created lazily afterAddChild shouldn't fire. This breaks data model, since node created lazily exists in the tree data source. There's no way to distinguish new nodes added to the tree from nodes create lazily.
It's more appropriate to use a separate event afterLazyChildCreate or something similar to that.
Change History (4)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
Added special flag to indicate that a node was created lazily, not really added.
comment:3 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
afterAddChild represents a new widget being added. setChildren creates (non-recursively) widgets from given array.