View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000266 | MMW v4 | Main Panel/Toolbars/Menus | public | 2003-04-10 12:53 | 2006-07-17 18:22 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000266: Tree: /Library/Locations/Network node shouldn't appear unless Tracks are contained within | ||||
| Description | At present, the subnodes in /Library/Locations node only appear when the 'Location' in question has track(s)--except that the 'Network' node always appears, even when there are no tracks contained within! This should be changed--the network node should only appear if there are tracks that are on the network that are already part of the library. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Since MM operates over a SQL database, getting this information means an additional query. I don't think it's worth it, I don't see the current implementation problematic. |
|
|
Not sure I understand the issue. If there are no tracks in the DB with a network-based location, then why bother showing this node? The logic is identical to not showing a Genre of 'Calypso' if there's no Calypso music in the library! |
|
|
This can be fixed by executing a SQL query when Locations node is expanded and showing the node only if same network tracks exist in DB. Also, when a track is added to Library and this node doesn't exist, it should be created. Probably __NotifyDBDirExists() in AppManage.pas should be modified for this purpose. |
|
|
done |
