View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000703 | ardour | bugs | public | 2004-08-28 09:21 | 2020-04-19 20:12 |
| Reporter | marek | Assigned To | cth103 | ||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Summary | 0000703: right button press + drag | ||||
| Description | Currently rightdrag does the same thing as rightclick, i.e. invokes a context menu. The problem is - if you rightdrag outside a region, location marker, punch/loop range and then release the context menobjectregion the context menu was invoked upon. Two ways to deal with this: [more unified, less functionality] rightdrag does the same thing as leftdrag i.e. moves the object except it invokes the context menu when released. This way the context menu always stays related to the object. [less unified, more functionality] The idea: *leftdrag moves object(s) *rightdrag copies object(s), doesn't invoke menu This way, two new operations become available: * ctrl+leftdrag * ctrl+rightdrag another benefit of the "selection follows - button press" model(i.e. that the selection always happens on button press and the actual operation on button release). :) Location markers: rightdrag should copy location markers. Marker line appears just like with left drag. No context menu invoked. Loop/punch ranges: rightdrag moves the entire range. No context menu invoked. Note: in both proposals, there should be a pixel threshold between rightclick and rightdrag, to avoid unintended move/copy. | ||||
| Tags | No tags attached. | ||||
|
|
Uh, the first sentence should be: Currently rightdrag does the same thing as rightclick, i.e. invokes a context menu. The problem is - if you rightdrag outside a region, location marker or punch/loop range and then release, the context menu becomes unrelated to the object the context menu was invoked upon. |
|
|
Third option, most restrictive one - disallow mouse movement if right mouse button is pressed. |
|
|
this is really a GTK issue. we can't prevent mouse movement, and popup menus show up where mouse pointer is, not in a location that we control. |
|
|
Bug is a GTK issue, not an ardour one. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-08-28 09:21 | marek | New Issue | |
| 2004-08-28 09:23 | marek | Note Added: 0001452 | |
| 2004-08-29 09:22 | marek | Note Added: 0001453 | |
| 2005-04-02 18:51 | paul | Note Added: 0002160 | |
| 2009-10-20 00:16 | cth103 | cost | => 0.00 |
| 2009-10-20 00:16 | cth103 | Note Added: 0006753 | |
| 2009-10-20 00:16 | cth103 | Status | new => resolved |
| 2009-10-20 00:16 | cth103 | Resolution | open => won't fix |
| 2009-10-20 00:16 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:12 | system | Note Added: 0021437 | |
| 2020-04-19 20:12 | system | Status | resolved => closed |
