View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003830 | ardour | bugs | public | 2011-03-06 16:54 | 2020-04-19 20:15 |
| Reporter | danboid | Assigned To | paul | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 3.0-beta2 | ||||
| Summary | 0003830: scrollwheel editor confusion | ||||
| Description | Under A2, using the scrollwheel in the main editor window only scrolled the view of the tracks up and down but now in A3 if your pointer is over a tracks fader the scrollwheel adjusts it. I just found myself with a wonky mix and I realised it got messed up by scrolling the view whilst my pointer was hovering within the same horizontal space which the editor faders occupy hence multiple levels got accidentally adjusted whilst I was scrolling up and down the tracks. Not sure what the best solution is if both bindings for the scrollwheel are to stay if we want to avoid this happening? | ||||
| Tags | No tags attached. | ||||
|
|
One solution would be that the scrollwheel could potentially do different things in different areas of the editor. If it is located above the 'control strip' area of the tracks then it would adjust the fader of the track below but if it is located above the 'region' area of the editor it scrolls tracks up and down. This issue has reminded me of a very similar issue that should maybe be posted separately and thats how hard it is to adjust the velocity of notes using the scrollwheel. Its nigh-on impossible to keep your pointer in the correct location for long enough to set the velocity correctly before you slip off and end up scrolling the editor tracks up/down instead, hence I normally use CTRL+UP/DOWN or CTRL+RMB and type it in. |
|
|
Yes, I noticed this as well. I think that matching A2 by desensitising the track view faders to scroll-wheel events is the best thing to do. I've attached a patch that reverts this change of behaviour, though I'll confess that I don't really understand what the call to Keyboard::some_magic_widget_has_focus() that the patch removes is supposed to be doing... |
|
2011-03-07 10:55
|
desensitise-track-view-fader-scroll-a3.patch (411 bytes)
Index: gtk2_ardour/time_axis_view.cc
===================================================================
--- gtk2_ardour/time_axis_view.cc (revision 9085)
+++ gtk2_ardour/time_axis_view.cc (working copy)
@@ -294,9 +294,6 @@
bool
TimeAxisView::controls_ebox_scroll (GdkEventScroll* ev)
{
- if (Keyboard::some_magic_widget_has_focus()) {
- return false;
- }
switch (ev->direction) {
case GDK_SCROLL_UP:
|
|
|
The sliders in automation tracks also suffer from the same problem. |
|
|
fixed in svn @ rev 10903 for both gain faders and parameter controllers. scroll event is now handled by the time axis view scroll handler. the magic focus stuff was just a mistake. the fader grabs "magic focus" when the mouse pointer enters it (and drops it when it leaves). checking for it being set in the scroll handler was pointless. |
|
|
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 |
|---|---|---|---|
| 2011-03-06 16:54 | danboid | New Issue | |
| 2011-03-06 21:10 | danboid | Note Added: 0010302 | |
| 2011-03-07 00:52 | cth103 | cost | => 0.00 |
| 2011-03-07 00:52 | cth103 | Target Version | => 3.0-beta1 |
| 2011-03-07 10:55 | colinf | Note Added: 0010303 | |
| 2011-03-07 10:55 | colinf | File Added: desensitise-track-view-fader-scroll-a3.patch | |
| 2011-10-05 14:10 | colinf | Note Added: 0011656 | |
| 2011-11-15 14:58 | cth103 | Status | new => confirmed |
| 2011-11-15 14:58 | cth103 | Target Version | 3.0-beta1 => 3.0-beta2 |
| 2011-12-05 18:18 | paul | Note Added: 0012304 | |
| 2011-12-05 18:18 | paul | Status | confirmed => resolved |
| 2011-12-05 18:18 | paul | Resolution | open => fixed |
| 2011-12-05 18:18 | paul | Assigned To | => paul |
| 2020-04-19 20:15 | system | Note Added: 0022441 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
