Opened 11 years ago

Closed 11 years ago

#6268 closed defect (wontfix)

Tree: _onItemDelete

Reported by: navin@… Owned by: bill
Priority: low Milestone: 1.3
Component: Dijit Version: 1.1b1
Keywords: Cc:
Blocked By: Blocking:

Description

I know according to the comments that this event handler is not technically necessary, but I might have found a case where it is. As a workaround, I connected it from the outside, so I could solve my problem. But my issue is that I had two trees/models/stores where I was moving items between, and ran into an issue, where an item was moved from once and back, it couldn't be moved once more because of an InvalidItemException?. I think was happening was a stale orphaned node was coming back with an invalid item that had been deleted before in that store. When I connected the _onItemDelete method, things worked fine.

Change History (4)

comment:1 in reply to:  description Changed 11 years ago by guest

Replying to guest:

I know according to the comments that this event handler is not technically necessary, but I might have found a case where it is. As a workaround, I connected it from the outside, so I could solve my problem. But my issue is that I had two trees/models/stores where I was moving items between, and ran into an issue, where an item was moved from once and back, it couldn't be moved once more because of an InvalidItemException?. I think was happening was a stale orphaned node was coming back with an invalid item that had been deleted before in that store. When I connected the _onItemDelete method, things worked fine.

Please CC to navin@…

comment:2 Changed 11 years ago by bill

Component: GeneralDijit
Owner: changed from anonymous to bill
Reporter: changed from guest to navin@…
Summary: dijit.Tree _onItemDeleteTree: _onItemDelete

Please attach test case to this (and every) bug, using the "attach file" button.

comment:3 Changed 11 years ago by bill

Milestone: 1.3

comment:4 Changed 11 years ago by bill

Resolution: wontfix
Status: newclosed

Closing since no test case.

You should really be monitoring deletes on the data store itself; I don't see a reason to get notification from the tree.

Note: See TracTickets for help on using tickets.