View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006504 | MMW v4 | Main Panel/Toolbars/Menus | public | 2010-09-28 03:19 | 2015-02-05 15:13 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0.7 | ||||
| Summary | 0006504: Persistent tree nodes | ||||
| Description | In MM4, top-level tree nodes should persist (visually) so that they can be selected even when other tree nodes are expanded (which would normally force all top level nodes off the screen). See: http://www.jirihajek.net/MMwiki/index.php/MM_4.0_UI#Main_Panel | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Tested build 1316 and there are two issues with the current implementation: a) The only tree nodes that are persistent are Device and Disc nodes. If the tree is expanded, all other nodes (e.g. Now Playing, Playlists, UPnP Servers, My Computer, Net Radio, Web nodes) are forced off the screen. Factors to consider: - Users will be doing a lot of d&d between collections initially e.g. from Video to TV, until this can be better automated - Tabs are nicely implemented, and therefore there exists an alternate means of dragging files between collections - Having too many persistent nodes may take up too much space in the tree Possible approaches: i) Don't use the Accordian implementation at all ii) Implement it for some or all root nodes as is currently the case (preferred by Rusty for 4.0) iii) Make it configurable for which nodes it is enabled. This is probably the best solution, but only post 4.0. This could be implemented in the View configuration dialog. Note: Top level nodes should remain displayed at the Top/Bottom portion of the tree--depending on whether the node in question is higher/lower than the nodes currently being viewed. Option ii is probably the best approach for 4.0, though we may want to try implementing for more nodes (high) or pursuing option iii (high) time-permitting. b) Drag and drop onto a persistent tree node doesn't work--it currently drags onto the node that appears 'under' the persistent node. This means that the feature fails to satisfy one of the intended usecases (d&d to a device). This should be resolved with priority = 'Urgent' |
|
|
Note that the 'Downloads' node should appear as a persistent tree node if tracks are being downloaded (specified as part of 0006608) Fixed in build 1321. |
|
|
Item b implemented in 1351 |
|
|
Reducing priority to high. |
|
|
Petr, I tested b) in build 1363 and the operation works however, it's not easily usable because when dropping a file onto the device, the tree starts scrolling. I would expect that the tree shouldn't move when the user is trying to drop a file onto the device. In fact, I wouldn't particularly care if the transparency of the tree (behind the persistent node) is removed, if that makes things easier for you. Re-set to urgent to resolve this particular issue. |
|
|
Fixed auto scroll issue in 1364 |
