View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016317 | MMW 5 | Main Panel: Toolbars & Menus | public | 2020-01-29 15:16 | 2022-09-14 14:33 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | Fixed in Version | 5.0 | ||
| Summary | 0016317: Tabs: Open in new tab (from tree) | ||||
| Description | If the user right-clicks on an item in the tree, the first entry in the context menu should be 'Open in new tab'. The current workflow is: 1 Click the new tab button 2 Navigate to the required node (the problem with this is that most users would typically navigate to the node in question before adding a new node) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2224 | ||||
| related to | 0019050 | feedback | rusty | Track Browser: Add CTRL+Click and Scroll Wheel/Middle Mouse Button to open in new tab |
| related to | 0015664 | new | Ludek | Tree: Right click on tree node should not open the node |
| related to | 0016960 | closed | drakinite | Add CTRL+Click and Scroll Wheel Click to open in new tab to Media Tree |
|
|
This functionality is already available by Ctrl+click on node. Adding 'Open in new tab' to context menu for each node would unnecessary pollute the context menu for nodes, i.e. the action should not be so prominent IMHO. Your opinion? |
|
|
I think that 'Open in new tab' would be a useful addition. As for the length of the pop-up menu, it doesn't seem too bad. Should we want to shorten it, I'd rather sacrifice some tools (Auto-tag from filename), which are probably better called either in the mainview pop-up or even better the main menu. |
|
|
Ok, added in 2224 |
|
|
The functionality works, however, this can only be fully verified after 0015664 is fixed (since with that issue open, 'open in new tab' causes 2 duplicate tabs to appear). |
|
|
Reverted in 2225, because 0015664 is not an easy fix and would cause various regressions at this 5.0 pre-release state. |
