View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009162 | MMW v4 | Framework: Scripts/Extensions | public | 2012-02-21 21:57 | 2012-04-26 23:35 |
| Reporter | zvezdan | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.0.5 | Fixed in Version | 4.0.5 | ||
| Summary | 0009162: Nodes with Script.RegisterEvent OnFillTracks don't display covers in Art Browser with Details, also problem with Column Browser | ||||
| Description | Covers are not displayed in the Art Browser with Details mode when users click on some custom node which has OnFillTracks event registered using something like this: Script.RegisterEvent oNewNode, "OnFillTracks", "FillCustomLeaf" However, everything is fine if the same node has the old method for registering events like this: oNewNode.OnFillTracksFunct = "FillCustomLeaf" Unfortunately, using that old method is not an option for my script (Magic Nodes) because of the another bug which doesn't allow using of mixed old and new registering methods. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?p=325338#p325338 http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=64747 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1480 | ||||
|
|
There is also a problem with the Column Browser which does not respond when the selected node is registered using the "new" method, i.e. Script.RegisterEvent oNewNode, "OnFillTracks", "FillCustomLeaf". However, it works fine if the node has registered event using oNewNode.OnFillTracksFunct = "FillCustomLeaf". There are other scripts affected beside of Magic Nodes (all that use custom nodes registered with Script.RegisterEvent), which is reported here: http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=64747 |
|
|
Steps to reproduce the problem 1: - install Magic Nodes; - turn on the Art Browser with Details; - expand Magic Nodes; - expand the first predefined "Album Artist [A-Z], Album (by Year)" node; - select Unknown node -> you would see covers in the art browser just fine; - select any other node on the same level (A B C...) -> you would not see any cover. Note: Unknown node is using oNewNode.OnFillTracksFunct = "FillCustomLeaf", other nodes are using Script.RegisterEvent oNewNode, "OnFillTracks", "FillCustomLeaf". Steps to (not) reproduce the problem 2a): - select Entire Library node and restart MM, just to be sure that everything is reset to default and that initiall node is not some Magic node; - turn on the Column Browser; - expand Magic Nodes; - expand the first predefined "Album Artist [A-Z], Album (by Year)" node; - select Unknown node; - click on some item from the first (Genre) column of Column Browser -> everything is fine; - select any other node on the same level (A B C...); - click on some item from the first column -> everything is fine; - you could repeat the last two steps as many times and everything would be fine, just be sure that you click on only one column. Steps to reproduce the problem 2b): - select Entire Library node and restart MM, just to be sure that everything is reset to default and that initiall node is not some Magic node; - turn on the Column Browser; - expand Magic Nodes; - expand the first predefined "Album Artist [A-Z], Album (by Year)" node; - select any sub-node ("A", "B", ...) except the Unknown node; - click on some item from the first column (Genre) -> everything is fine; - click on some item from the second column (Artist) -> everything is fine; - select some another node from the same level except Unknown node; - click on any column of the Column Browser -> it would be deselected and not responding. Conclusion: the problem 2 is manifesting only after you click on 2 or 3 columns for the same node. This happens with any nodes, not only those that are children of the same parent. You could e.g. expand "A" node, select the first sub-node, click on 2 or 3 columns of the Column Browser and after that whichever node you select from the parent level you would get unresponsive Column Browser. The Unknown node has not that problem: - select any node, e.g. "A" node, or even some another Unknown node; - click on 2 or 3 columns of the Column Browser; - select any Unknown node; - click on the Column Browser -> it would work fine. |
|
|
Fixed in 1480 |
|
|
Verified 1484 |
