ardour/livetrax
13
0
Fork 0
Code

fix inconsistency in smart mode where it shows a trim cursor in the top half of the region edge, but a click is actually going to start a range. It is arguable that we _should_ allow trimming in the top half, but that is complicated. This change is small and makes it consistent for now

Browse Source
This commit is contained in:
Ben Loftis 2014-07-07 14:46:05 -05:00
parent abe203de65
commit 116a0ad327
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gtk2_ardour/editor_canvas.cc
View File

@ -1290,10 +1290,12 @@ Editor::choose_canvas_cursor_on_entry (GdkEventCrossing* /*event*/, ItemType typ
cursor = _cursors->cross_hair;
break;
case LeftFrameHandle:
cursor = which_trim_cursor (true);
if ( effective_mouse_mode() == MouseObject ) // (smart mode): if the user is in the top half, override the trim cursor, since they are in the range zone
cursor = which_trim_cursor (true); //alternatively, one could argue that we _should_ allow trims here, and disallow range selection
break;
case RightFrameHandle:
cursor = which_trim_cursor (false);
if ( effective_mouse_mode() == MouseObject ) //see above
cursor = which_trim_cursor (false);
break;
case StartCrossFadeItem:
cursor = _cursors->fade_in;