make edit clock do something useful again; do sensible guess work on how to define edit op range

git-svn-id: svn://localhost/ardour2/branches/2.0-ongoing@2615 d708f5d6-7413-0410-9779-e7cbd77b26cf
This commit is contained in:
Paul Davis 2007-11-09 22:16:55 +00:00
parent d79ff102e8
commit 85dbd75bb0
8 changed files with 62 additions and 17 deletions

View file

@ -1353,7 +1353,7 @@ class Editor : public PublicEditor
void editor_mixer_button_toggled ();
AudioClock edit_cursor_clock;
AudioClock edit_point_clock;
AudioClock zoom_range_clock;
Gtk::Button zoom_in_button;
Gtk::Button zoom_out_button;
@ -1417,7 +1417,7 @@ class Editor : public PublicEditor
void zoom_adjustment_changed();
void edit_cursor_clock_changed();
void edit_point_clock_changed();
void setup_toolbar ();
@ -1926,6 +1926,10 @@ class Editor : public PublicEditor
Glib::RefPtr<Gtk::RadioAction> edit_point_action (Editing::EditPoint);
std::vector<std::string> edit_point_strings;
void selected_marker_moved (ARDOUR::Location*);
sigc::connection edit_point_clock_connection_a;
sigc::connection edit_point_clock_connection_b;
bool get_edit_op_range (nframes64_t& start, nframes64_t& end) const;
RegionSelection get_regions_at (nframes64_t where, const TrackSelection& ts) const;