| Age | Commit message (Collapse) | Author |
|---|
|
|
|
required
|
|
link-region-and-track-selection since they are now exclusive, and rename select-all-regions to select-all-objects to match the implementation
|
|
separate action to select-all-tracks and select-all-regions. also, preserve region selection during a split, iff we are working on a region selection: only add the newly created regions, dont change anything else in the selection; leave that in control of the user
|
|
the playhead location. numpad now allows you to access marks higher than 9. to locate to a marker, use the numpad decimal to start and end the operation - for example press .19. to locate to marker 19. also added alternate bindings for redo, delete, and several other alternates that will be needed in subsequent commits. tab is not working, using either Tab or nabla in the binding.in file
|
|
"stuck" at max and min zoom levels
|
|
|
|
Fix up merge conflicts in
gtk2_ardour/editor_mouse.cc
gtk2_ardour/editor_ops.cc
Also fix up compile errors.
|
|
Manually resolved conflicts in import.cc and session.cc
|
|
|
|
|
|
with the guts of Editor::ensure_track_is_visible(), then remove the latter.
Also change all users of ensure_track_is_visible() to use _ensure_time_axis_view_is_visible()
|
|
|
|
|
|
|
|
events to the Editor
|
|
|
|
useful, too)
|
|
disable all action sensitivity.
This is needed to be able to lock the application fully on OS X, where the global menu bar would still allow interaction
even when a modal dialog is displayed.
|
|
Remove Canvas::Layout, use Canvas::Container for the same purpose, move child-rendering into Item::render_children() so that it
could theoretically be used by any derived type.
|
|
|
|
|
|
management.
Debugging output left in place to help address the reports that will come in as people test this more
|
|
debugging/analysis continues)
|
|
event coordinates made it look as if the event happened there)
|
|
|
|
|
|
|
|
Some bugs that exist in master are still present.
|
|
|
|
consistent scroll behaviour (whatever that behaviour is)
|
|
its size; remove debug message
|
|
motion events. The coordinate passed in was in canvas space and the method expected trackview space
To handle any further issues like this, I generalized and added an optional argument specifying that the canvas=>trackview transform is required, thus
centralizing where this done.
|
|
they are always on top.
I mistakenly removed this during the onecanvas changes.
|
|
ScrollGroup for Canvas::{window,canvas}_to_{canvas,window}()
|
|
|
|
part one - lots of minor fixes to be done
|
|
The idea now is that a scroll group item can be added to the canvas which will causes its children to scroll in either or both
directions (horizontal or vertical). There are few complications: the position() of the ScrollGroup is ambiguous depending
on whether you want it with scroll taken into account or not, so Item::canvas_position() was added, which defaults to
the same value as Item::position() but is overridden by ScrollGroup to return the position independent of scrolling. This
method is used when translating between item/canvas/window coordinate systems.
Note that the basic idea is that we MOVE the scroll group when a scroll happens. This mirrors what happens in the GnomeCanvas,
where Nick Mainsbridge came up with a great idea that allowed unification of the time bar and track canvases.
|
|
sources, especially when created via import
|
|
|
|
|
|
|
|
Add a value for Ripple to EditMode enum.
Add Ripple edit mode to edit mode dropdown, by adding it to the
Editor::build_edit_mode_menu() helper function, and remove the old code that
added items to the (now unused) Editor::edit_mode_strings.
Add the regions that should be affected by the drag to RegionDrag::_views so
that the drag carries them along automatically.
Use a copy of the RegionList in Playlist::core_ripple(), since bad things
happen when iterating over regions and they get moved around in the list.
Handle rippling in removal of regions from playlist.
When dragging in ripple mode, exclude all regions that lie before the
original start position of the selected regions being dragged from
rippling: this is what Mixbus does.
Make editor dragging respect snap-to settings, by using the existing
compute_x_delta() function, which did almost the right thing. Move setting
of _last_frame_position out of that function so all ripple-dragged regions
can move.
Ripple when dragging from region list: even though Mixbus doesn't do this, it
seems like a good idea.
Prevent multi-track selection being dragged across tracks, by making
RegionMotionDrag::y_movement_allowed() virtual, and overriding it in
RegionRippleDrag to forbid dragging of selections containing regions on more
than one track to dofferent tracks in ripple mode.
Remember which TimeAxisView a ripple-mode drag that's allowed cross-track
drags started from, so that the effect of rippling regions after any region
that's dragged off that track can be undone.
|
|
c/o Thomas Brand
|
|
This gives us an event/drag-n-drop/click target for things "at the bottom"
|
|
Editor::track_canvas_viewport_size_allocated()
|
|
|
|
|
|
|
|
of visible tracks". function to follow shortly, this is the control widget part
|
