summaryrefslogtreecommitdiff
path: root/gtk2_ardour/editor_mouse.cc
diff options
context:
space:
mode:
authorBen Loftis <ben@harrisonconsoles.com>2016-12-19 12:22:39 -0600
committerBen Loftis <ben@harrisonconsoles.com>2016-12-19 13:14:44 -0600
commit628c99d5555b30992d41e8b5b5ffef44ad7f31d7 (patch)
tree86336ef01b624ef0e228bef44b3dd13251a1c79c /gtk2_ardour/editor_mouse.cc
parent267dd5edd9b3f6296778c7f108b437033bcf2b39 (diff)
Follow Edits => Follow Range
* "Follow Edits" button had several behaviors that confused users. * "Follow Range" only has 2 behaviors: ** Click anywhere in Range mode (or Smart mode) to locate the playhead. ** When you select a Range, "Play" will play the selected range.
Diffstat (limited to 'gtk2_ardour/editor_mouse.cc')
-rw-r--r--gtk2_ardour/editor_mouse.cc4
1 files changed, 4 insertions, 0 deletions
diff --git a/gtk2_ardour/editor_mouse.cc b/gtk2_ardour/editor_mouse.cc
index 578595ff2a..e34c38c43c 100644
--- a/gtk2_ardour/editor_mouse.cc
+++ b/gtk2_ardour/editor_mouse.cc
@@ -2551,6 +2551,10 @@ Editor::update_join_object_range_location (double y)
if (entered_regionview) {
+ //ToDo: there is currently a bug here(?)
+ //when we are inside a region fade handle, it acts as though we are in range mode because it is in the top half of the region
+ //can it be fixed here?
+
ArdourCanvas::Duple const item_space = entered_regionview->get_canvas_group()->canvas_to_item (ArdourCanvas::Duple (0, y));
double const c = item_space.y / entered_regionview->height();