View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011489 | MMW v4 | Framework: Scripts/Extensions | public | 2013-11-19 08:18 | 2013-11-19 13:25 |
| Reporter | zvezdan | Assigned To | |||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0011489: ISDBApplicationEvents::OnNodeFillChildren and OnNodeDragDrop events needed | ||||
| Description | Since you have some problems adding event handlers to the nodes in the Playlists branch as I reported before (http://www.ventismedia.com/mantis/view.php?id=6729), maybe it would be easier for you to implement such events to the Application object instead. Those should work with all nodes, but I need them mostly because of Playlists nodes. Actually, maybe such solution would be even better because I don't need to register event handlers starting from the main Playlists node (even if that is possible). Instead, my script could just wait in the suggested event handler for user expanding of some node and check if that node/playlist is generated by my script (as I am already doing with Magic Nodes with OnTrackListFilling to dynamically fill filelist for the selected playlist). As you could see, the similar situation we already have when filling tracks, i.e. we have two events: ISDBTreeNodeEvents::OnFillTracks and ISDBApplicationEvents::OnTrackListFilling, which both could be used in similar manner. The suggested OnNodeFillChildren event should be risen before the program starts reading the Playlists table to generate nodes, so the script could eventually add or remove some sub-playlist to the Playlists table before that, according to some internal condition. Alternatively, OnNodeFillChildren could have one output boolean argument telling the program that the script handling this event is actually filling the tree with sub-nodes, so the program should skip that. The name OnNodeFillChildren is because of the consistency with the similar Tree node event, but maybe OnNodeExpand would be better. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
